!process amazon offer

[brittle karma]

timeline?

[hollow wren]

OA - Oct 28
Recruiter reach out — moving forward - Jan 28
Interview confirmation - March 7
Final Loop - March 12
Offer - March 18

[stark canyon]

how’d the rounds go? all perfect?

[sonic rampart]

damn this one took a long time

congratulations! can you share how did it go and what was asked

[hollow wren]

I think so, however i feel like one of them was a not inclined as i fumbled a little on the follow ups for the LP answers focused on metrics, i dont think they were convinced/had doubts maybe

[hollow wren]

yea, it was a long wait

[stark canyon]

i see, OOD was good?

[hollow wren]

Round 1
20 mins LP, emphasis on delivering under deadlines (have metrics ready). Tech: Word Search II, discussed trade-offs/algorithms in depth. Went smoothly.

Round 2 (LLD) (might have been not inclined :/)
Discussed one project deeply, many follow-ups on impact, metrics (had to defend my reasoning clearly). Then, designed a Multimap-like data structure from scratch, listed methods exhaustively, and coded up insert.

Round 3 (Bar Raiser – 50/50 split)
Behavioral: scenarios about going beyond role, troubleshooting, learning outside comfort zone. Technical: started simple with provided APIs, solved quickly, then incremental complexity involving heaps, sorting, and BFS with controlled depth.

[hollow wren]

It was alright at best imo

[robust cairn]

congrats!!

grad date?

[hollow wren]

Thankyou! Dec 2023

[robust cairn]

so is your start date within a month?

also did they tell u your team? like are u in aws?

[hollow wren]

Yeah, its april 21

[hollow wren]

Not yet

[rare oak]

Can you give more details about the bar raiser? Im trying to get an idea of what to expect

[nova jacinth]

Me too

Bar raiser is just lp?

[robust cairn]

location?

[hollow wren]

It was with a director level engineer, the round was split into two 30min sections (behavioural+technical)

Behavioral asked about a scenario where I went beyond my usual responsibilities, then dove into deep-dive questions around troubleshooting and learning something outside my comfort area. Technical part started easy with a small problem and 2 provided API helper methods—I solved quickly. Follow-ups progressively increased complexity: first adding a new requirement and implementing it; then another layer of complexity involving heaps/sorting, and BFS with controlled depth.

Biggest tip:
Prepare detailed, airtight responses proactively addressing possible follow-ups. Bar raiser explicitly said my answers were very detailed and comprehensive, so he had no further questions after my initial responses and mentioned that my answers already covered other questions he was planning on asking.

[hollow wren]

Its amazon legal

[hollow wren]

nyc

[toxic jacinth]

are ur interviewers at Seattle?

or like West Coast?

[hollow wren]

yeah, all of them were seattle based

[toxic jacinth]

okay thanks

[rare oak]

Thanks for your response. How would you practice for the bar raiser?

[nova jacinth]

I dont think i ever had bar raiser round. Everyone was senior engineer at most, not director. Does anyone knkw if one of the interviews was actually a bar raiser round?

[hollow wren]

Tbh nothing different, just make sure to keep your LP answers well structured and answer follow ups clearly

[hollow wren]

Well in that case its kind of difficult to say which one was bar raiser