Just got my rejection from Amazon. Recruiter refuses to share feedback details on the on-site but hinted that i did great on the coding and design. Ended the call saying that Amazon has certain leadership principles that it evaluates everyone on. What is that supposed to mean? (My interviews all had 15 minutes of questions on my past experience. Coding was LC medium and I managed to get mostly workable solutions. The only controversial questions I had to answer was have you fought with your manager and do you regret any decision in the past. I said no to both. In my case I have never ever fought with my manager and could not recollect any technical decision that I regretted.) Is that why I get knocked off? For not fighting with my manager?! I answered the questions as truthfully and humbly as possible. Can the good folks at Amazon please shed some light on why someone gets knocked out on leadership principles? TC: 170k
To be honest, I think they are looking for a more sought after explanation as to why hasn't there been any disagreements btwn u n ur mngr. With all due respect it kinda portrays you as gullible.
Well I did say we have had disagreements in techincal design discussions but I was asked explicitly if I ever fought to which I answered no.
Might just be unlucky, can't judge in that case
That is why you make up shit if you can't find such example.
The truth is I have been really lucky to have had some really good managers and I know and have seen how bad some others can be both in my company and outside. I told them exactly that. I also said that we have techincal discussion all the time.
So how do you make stuff up on this? I mentioned disagreements but they kept asking me about fighting! I thought making stuff up was more dangerous than the truth.
May be long answer needed
Why the fuck would you say ânoâ to both? Thatâs stupid in any interview. Those questions are freebiesâyou should know right away âTheyâre looking for a way to gauge how I handle interpersonal challenges.â If you canât see that, yeah, you should be mad...at yourself. You gave up an opportunity. Your post is annoying because Iâm over here kicking my own ass over LeetCode practice while you, a person who can get through the Amazon code questions well, fail on elementary shit like this. Iâm coming for your fucking spot and taking it if you donât get it together.
Well then you can imagine how it is to get knocked out after grinding LC (not saying I am an expert, far far from it), travelling onsite, answering their graph and string questions and then getting rejected for telling the truth! Fwiw, I didn't say a short no, I just explained that I never had a need to fight. I also explained that we have techincal discussions all the time.
Fuck telling the entire truth. Donât lie. Project. Are you just a hermit? Do you not know people yet? The world? Honest Abe got shot in the fucking head. Remember that. Get yours. This isnât a world built on whole truths. Come up with a situation on the fucking spot when you donât have a real answer.
Ur interview didnât go well. LPs hardly make any difference. You might feel that your interviews were good, but ur interviewers felt other way. Also, like any company itâs based on number of votes you get from your interviewers.
Maybe you are right but honestly it did not feel like the coding or design rounds were bad. I needed a hint or two but nothing seemed terrible. The interviewers always walked out with a whiteboard filled with a complete function(s). I have had tougher luck before.
Itâs a thing in Amazon to give good experience to the candidate. If you would have got more yes, they would have given you another team even if your HM didnât wanted to hire you. Also not trying to judge you. At the end of the day interview is just a day thing and depending on how your day went you either get a call or not. Best of luck for your future interviews.
Honestly it's a red flag to say you never regretted any technical decision. We all make huge mistakes, it's part of learning. Saying you've never regretted anything or would have changed things in hindsight either means you're lying to make yourself sound perfect or you actually haven't made any technical decisions.
Well again the answer wasn't a short no, I spoke about bugs I caused and how they got fixed. The one I got drilled most was fight with manager!
What if we haven't yet had the opportunity to make substantial technical decisions at work (which is a reason why we're looking for a job elsewhere)? The technical decisions I've gotten to make so far are fairly straightforward and I don't regret them. As for more open-ended technical decisions, I've mentioned to my manager I'd like exposure to that but it hasn't happened yet.
Not regerting a technical decision means you're are unable to accept you're wrong, or never learned from your mistakes. That's a huge blind spot that will easily fail you an interview. It's most likely you failed because of that rather then "not fighting with your manager".
To be honest, if I'm asked to judge only by the way you come across based on your question then I wouldn't hire you. This is not criticism, please take it as constructive feedback. You don't know why you were rejected, you came up with two possible reasons, then you picked the one that seems the most ridiculous (rejected for not fighting manager), and then you framed your question and the title to emphasize that reason. You're trying to show that your interviewers were stupid. It's passive aggressive. If you did something similar in the interview then that's your answer. Of course I'm speculating. And what do l know anyway? But think about it, and maybe it helps in a future interview. Getting rejected sucks, I know from experience. I feel your pain, and I hope you get a better offer soon. Good luck.
Understood. Not trying to prove anyone stupid, but rather looking to eliminate what seems like my most bothersome root cause. You and folks above are probably right - it's likely something with coding- maybe I missed a corner case or overlooked a bug. Just going by what recruiter said seemed like LP was the root cause, but that could just be a (confusing) attempt at sweet talk. Thanks for the honest feedback though.
I once âimprovedâ a design by deleting a legacy caching logic. I was semi senior so didnât need to justify much. At launch that caused an expected issue. Nothing too serious . Oncall had to spend couple of hours. I didnât regret my call. I regret not talking about my design enough so that I didnât foresee the issue. I would have made the change anyway while mitigating the impact . The guy who was officially a senior engineer disagreed with my decision. So we talked and disagreed and he gave me a bad review. In an interview I would go into the details of what did I learn. He was right and I was wrong. I understood that some years later. You donât have technical regrets? Either you need to recall examples. Or you lack self awareness. Or you never make any consequential calls. None of those options make me want to hire
What if you don't have the opportunity to make consequential calls, even though you have told your manager you would like more responsibility on that front? No one on my team has that opportunity except the team lead and the manager.
Software Engineering Career
Yesterday
543
What MAANGMULA has a higher interview bar?
Tech Industry
Yesterday
2733
Google giving meals. Meanwhile Amazon L8 âdonât take more than one fruitâ
India
Yesterday
215
Duniya me Vishwaguru ka Danka
Fitness
Yesterday
1028
how can i loose 5 pounds with small changes to lifestyle
Working Parents
Yesterday
2797
Is it true many Indian couples are in sexless marriage?
Don't worry. Most of the time BR give not inclined just to show his bar is high.