#!process Amazon reject

1 messages · Page 1 of 1 (latest)

valid gale
#

timeline please

slender raptor
#

After OA?

fluid helm
#

Timeline:
Jul 12th - Applied
Oct 5th - OA link received (different job ID from what I applied)
Oct 11th - Interview Schedule link received
Oct 21st - Interview scheduled
Nov 5th - Final interview loop
Nov 11th - Rejection Mail

valid gale
#

sorry man.

#

how was your loop?

fluid helm
#

Loop was fine for the most part.

1st round - LP round with many 3-4 follow-up questions for each main question. Answered them in STAR format and the interviewer was satisfied by the reaction to the answers.

2nd round - Mix of LP and low level system design. Asked me to design a pizza shop using LLD. Expected this particular question through research during my preparation so was easy to answer.

3rd round - leetcode style round with 1lp where 1st question was on lists with no emphasis on data structure or algorithms. Did gave approach and was about to code and the interviewer said to move on to next question. He agreed on the approach and then moved onto next question due to less time left in the slot.
2nd question was a string based more leetcodeish than first one. Gave approach and after me and him going back and forth with clarification questions started to code and during dry run passed most test cases and with a small change passed all cases. Interview was also satisfied and ended on good note.

Personally what I feel is that maybe they found a better person than me who was more time optimized. That would be a cause for my rejection if not then I don’t have a clue on the rejection part.

hardy relic
#

I'm sorry. Hope you get another offer soon

#

I had similar experiences, and all my interviewers were indians. Was this the case with you

still ermine
fluid helm
#

The editor which they provide does not contain code run functionality. It is called as whiteboarding where the interviewer gives you inputs and while you clarify your doubts at the start of question specification, you need to ask for various possible inputs and outputs. So I asked the interviewer what should be the outputs when a null input is given or negative or positive or what ever it maybe based on the question. Then using those you check for each input how does the code outputs by checking the code works in each input going through each line.

Basically they check how will are you thinking when a dry run occurs.

#

Sorry for long messages

still ermine
fluid helm
hardy relic
#

Oh, thanks for the info.

fluid helm
#

The tagged lc question from leetcode bot are useful and work on neetcode blind 75 and 150. These would cover most questions.

#

Pizza shop you can find on Google itself as it’s a popular question.

round zenith
#

was this for entry level swe position?

slender raptor
#

When did you write the OA?

fluid helm