Trying to prepare for this but really have no direction, can anyone help? Recruiters said may include questions related to: system design, tech challenges you have led and overcome and technical problem solving. This is pretty vague so wondering if anyone has gone through this and has specific examples and what success looks like. The call is only an hour so trying to imagine what will be covered. ** I should add that I've been managing fairly large teams for the past 7-8 years so I'm not super close to the code anymore.
Well despite having what seemed like a really good conversation sounds like I didn't pass even the first phone screen and of course no clear feedback on why. Just that I'm "encouraged to apply for other positions"... Awesome.
You are doing fine!!!!! Congrats on getting over with the confusion. Thanks for the update back to the community.
Not really doing fine but thanks. All the prep 15 years of mostly successful experience and can't pass phase one...
The response was as follows: "After serious consideration, we have decided to pursue other candidates for this particular role. We encourage you to apply to any postings listed on our job board at www.amazon.jobs." So I take it it's just not aligned with one role vs not aligned with amazon in general?
Hmmmm. That sounds totally useless for a feedback to improve. Good that you aren’t blocked for 6m or 1 yr. Did they ask LP related Qs or more technical or more “role oriented” in the phone interview? May be they asked role oriented all disguised to check LPs????
May we know what we’re the questions like?
Tech Industry
2d
53275
Goog Employees Arrested
Layoffs
2d
41075
Google CFO confirms 'large-scale' layoffs (Apr 17)
Tech Industry
8h
593
So did Satya make Google dance?
Tech Industry
Yesterday
1073
RIP Lacework
Tech Industry
Yesterday
532
Chances of meta clearing E5 with screwing up one coding one round and acing all other
You don’t have to code. You have to understand system design and architecture and be able to know good from bad and work independently or collaboratively on a design. You will not design things for production on the job, but whiteboarding rough ideas like you will do in the interview will not be abnormal. You won’t lead the discussion on the job but if you can’t hang at all you’ll lose confidence. Look at the LPs. Have SBI examples for all of them. When it comes to tech challenges they want to know what YOU did. You had a team member sequestered and removed from on-call, you created and protected a tiger team, you shadowed on call for a month and helped the team decide how to eliminate N root causes. Not what your team or the best engineer on it did. When you’re interfacing with business folk you need to understand what they want to do through the BS of what they’re saying you should do, and be able to solve it in a sane way instead of how they are proposing it. You have to suggest this to your team along with sufficient humility, they may know better, but you shouldn’t bring them ill-informed edicts from businesses stakeholders that leaves them with no agency when they own the systems.
Thanks a lot this is helpful, are the LP scenarios a part of the technical call? It seemed like those where challenged in a secondary "leadership" phone call or perhaps in the onsite.
Always. Be. LPing.