Do other tech companies value your AWS expertises
Being in a non-AWS org at Amazon, I’ve built many services based on quite a selection of AWS offerings, and I’m wondering would it be weird if I am interviewing other tech giants on systems design and I describe my solution based on those AWS offerings? I mean other cloud may have similar products, but there are always some small features that may not have parity. @Google @Facebook
I’d steer away from choosing the actual technology and describe functionality. Like using “distributed message queue” instead of SQS or “distributed cache” instead of Elasticache. Also, what role?
SDE. So for the SQS case, one thing special about it is its at least once, potentially out of order delivery, so like the consumer system would need to handle out of order/duplicate delivery. That’s actually pretty important to cover for SQS but may not be the case for other queue technology.
Who are going to use queues will look at their specs. Kafka also have different levels of guarantee. To me, understand the cloud basic offering doesn't present too much value in the hiring process. Mention something so elementry would make you look junior.
Op, do you know that none is going to give a shit for what did in your project.
Yeah, use the AWS product name and describe why it fit the use case. Many companies use AWS is some capacity so it’s completely fine to discuss it.
Say both - “I would use SQS here or (insert company name)’s equivalent distributed messaging service”
Although, I think this is a minor distinction. Probably not a big deal either way. Just design that shit well and people will pick up on your knowledge
Just something I’ve noticed on interview panels... Amazon folks pretty much handwave major components in their architecture. “Oh we decided to us AWS lambda for this part” etc. It isn’t bad necessarily but often times the knowledge of these systems (or their open source equivalents) is skin deep at the most.
What else should they mention to change your mind?
Is this different from other companies built on top of AWS?
People generally don't seem to care or won't know what you're talking about when you name specific services (Not invented here syndrome). If you do want to talk about using these services, provide a basic description of what those services do. (SWE/Eng)
I was asked at length about my AWS experience when interviewing at Google. In particular Goog wanted me to compare and contrast the cloud offerings.
For a swe role?
Eng leadership
Detailed knowledge of AWS is a large pro, in my opinion.
At the end of my design interview at Doordash, the interviewer asked me to put Aws product names on blocks in the diagram.
What’s your yoe?
8 yoe
How to tag companies?
Only can do it in topic posts. Welcome to Blind.
I have wondered the same thing...