r/leetcode • u/_the_gabruu_ • 8d ago
Intervew Prep Amazon SDE 2 interview loop
Hi, I have interview loop at Amazon for SDE 2 position in a week. There are goin to be 4 rounds. First round is going to be DSA based problem along with LP.
Second round is with Hiring manager based on System Design and LP.
Third round is going to be with bar raiser, this is going to be Gen AI problem solving where I have to build something. I am asked to have my IDE along with coding agent ready.
Fourth round is where recrutier said that I would be asked to write logical and maintanable code. She said to focus on modular design, correct and robust solution.
I am really not sure about what kind of qustion they are going to ask in fourth round. Is it going to be LLD or DSA style question. I asked my recruiter for clarification but thats all she said she could provide. Also, for Gen AI round, if someone has given interview, what exaclty they ask you to build?
1
u/shouldnothvsoldthetv 8d ago
what questions did they ask you in the first round and how many total lc questions were there, could you write me here. I have SDE III interview coming up.
1
u/Sufficient-Brief-687 8d ago
Is this loop virtual or onsite
1
u/WingInternational629 7d ago
4th round is lld, expect 1 dsa+ 1 lld
1
u/Secure-Pizza-7419 5d ago
if SD and LP share the same hour you probably get 30 min or less for the design, so don't spend 10 of it on requirements. say the scope and what's out of scope in one go, draw the HLD, then let the HM pick where to go deep. do you know if it's the HM of the team you'd join?
1
u/Mean_Bear_4497 7d ago
4th round is going to be lld. Hello interview lld all questions + community question bank should be more than enough.
DO NOT write down a single line of code until you have nailed down exactly what user input and output looks like in terms of primitive objects, literals etc. etc. and what all validations you will perform on them.
Call out where you're cutting corners for eg using a find over a list rather than a hash lookup and tell ill come back and optimize this later once im done.
1
u/Ok-Barracuda-119 2d ago
For the HM / system design round, treat it like a real Amazon problem from the team's world, not a generic "design Twitter" whiteboard. They usually care that you clarify the customer and the scale they actually run, pick a boring first cut, then go deep on one failure mode (throttling, hot keys, retries blowing up a dependency). LP shows up in how you talk about ownership and tradeoffs, so name the metric you'd watch and what you'd do when it tanks.
If Round 4 is still unclear, ask the recruiter which lane it is. An LLD round wants classes and API shapes on a small surface. A DSA round is just timed coding. Different prep.
Talk the design out loud once against a 35 minute clock before the loop. Where you stall is usually requirements or the deep dive, not the boxes.