Background
I had been working at my first software job for 3.5 years and in that time I moved from junior to mid. It was obvious that if...
For further actions, you may consider blocking this person and/or reporting abuse
Thanks for writing this article; I really enjoyed reading it. While I appreciate the insights, I’m not sure I would want to work at AWS. I generally prefer smaller companies where I can have a bigger impact, even if that comes with more stress. I’ve always heard about the challenging interview processes at companies like Google, Facebook, and Netflix, but I didn’t realize AWS had a similar approach—although it makes sense. It’s surprising that they offer interviewing workshops to help candidates prepare. The amount of time required for their interview process might also be a deterrent for me, but I’m glad to hear you had a positive experience overall!
I love that you're thinking about your own path and what you want out of a job. Knowing that is so vital for a healthy career
It is interesting reading this. Having worked at AWS/Amazon, there is some good stuff in here, but there is a bit more I would add.
Don't make stories up. A good interviewer will ask questions and find out when/if you are full of crap. This may sound bad, but you have to be honest. Now, you can spin a story any which way, but make sure you actually worked on what you say you worked on.
Earns Trust. If you are caught lying or thought to be lying you will get axed. I have seen a full interview board turn down someone because they were caught lying. Be honest.
The technical aspect is only a facet of the interview, for technical roles. Be prepared for all types of questions. A lot of people know that everyone is just grinding leet code to prep. This means that interviewers are getting more creative in their questions. Asking open ended problems that can be solved a number of ways.
And, if you get a question about the 15/16 leadership principals, just run.
Absolutely to all three of these.
Haha, while I agree that the latter two don't fit with the first 14 principles, I think they are attempting to address real problems Amazon was facing. I hope there's a good resolution there.
Thanks for such a detailed and well informing article. You really gave very good information on what it takes to get into a FAANG company. I personally wish to get into a FAANG company and I will use this as a roadmap. Thanks for that
Glad this could help! Good luck on your journey!
😮
Wait a minute, I recognize you from Twitter! Hello again!
Hello, didn't expected that coming 😲
Keep shining, buddy. ✨
Hope Amazon retains you for long!
Thanks! They keep offering me positions after I chose to leave, but it's more important that I'm home with my baby right now.
I look forward to when I can say yes to coming back though
So true about step #4. Trees got me off guard the last time I tried at a FAANG
Right!? It's so interesting how integral they are to some faang work. I don't know of many places which would prefer to work with a tree over other data structures.
Worth reading and Thank you!
Please keep posting such articles.
Will do! I'm open to ideas if there's anything specific you'd like to hear about
How about a roadmap even more detailed ? :)
Hey, nice post! I thought I recognized that avatar from Slack and I was right.
Oh hey! How crazy to bump into you here!
Thank you so much for sharing your experience! Btw nice collection of dice you have there. ♥️
♥️ it's such a a great desk toy. I was running a ttrpg where the players where an analogy for the subconscious and repressed thought at the time
Worth reading can you share some tips to crack job as fresher?
Sure! Actually there's another comment on this post which summarizes some good extra tips: dev.to/eric_vanwieren_813ca70462/c...
Also, look up Neetcode on YouTube if you haven't already. Seeing them break down problems is incredibly helpful.
Neetcode you say? I haven't checked that out. Thanks for sharing.
Amazing proyect, nice work!!
Preparation is key! Balancing coding challenges, leadership principles, and design patterns made a huge difference in my AWS interview. The hard work paid off!
thanks for sharing
great tips man
I do want to emphasize that this is something that they explicitly said I could do in that AWS provided class, might want to check with your recruiter if the rules change 😅
Very helpful article, thanks.
Although I work in a very small operation and love it, I would like to experience life at one of the big ones, even if only for a short time.
I think it's worth it to try and make the shift for a while. I learned a lot there that I couldn't have anywhere else (although I guess that's the case with a lot of jobs 😆)
I will say, if it was me, I'd wait till I was ready to move on from my current role before looking for something at a faang company. For a number of reasons, but the biggest being that job satisfaction is fairly difficult to find. It's awesome you like your current role!
Hi Winston, thanks for sharing the article! I really enjoyed reading it.
So practical, thanks for sharing with us!
Informative article.
Very inspiring article, man.
Great read. Thanks for sharing those resources! I will check them out.