Amazon Software Engineer Interview Guide for New Grads 2027

The Amazon SDE interview for new grads still runs through an Online Assessment, a virtual loop, and a Bar Raiser, and knowing that shape early changes how you prep. Amazon cut around 30,000 corporate jobs across late 2025 and early 2026, and if that's the headline you've been reading, you'd assume the door slammed shut. It didn't. AWS CEO Matt Garman said in April 2026 that Amazon is on track to bring in over 11,000 interns and early-career SDEs globally, and a spokesperson confirmed that number is in line with previous years (Business Insider). So the layoffs and the hiring are happening at the same time, in different parts of the company.

This guide comes from a mix of firsthand hiring experience and pattern recognition at scale. After nearly 20 years of interviewing engineers, mentoring candidates, and watching thousands of people earn offers at companies like Amazon through Simplify, you start to see what consistently matters. I also dug through recent new-grad interview write-ups to validate those patterns, so the advice here reflects both what candidates are reporting and what I've seen work over time.

The short version: the format hasn't changed much, but the silences are long, the logistics are messy, and a few specific habits separate the people who got offers from the people who got rejected on questions they called "relatively simple" in hindsight.

What does Amazon's Online Assessment actually test?

The OA has three sections, and people who only grind LeetCode get surprised by two of them.

The coding section is one or two problems, usually one easy plus one medium or two mediums. In a 2024 US new-grad OA it was 80 minutes for two questions. In a 2025 India SDE-1 OA it was 75 minutes, and one candidate finished both mediums in 45 to 50. Topics that keep showing up: sliding window, binary search, graphs, dynamic programming, heaps, two pointers. The whole block runs about 2 to 3.5 hours and the link usually expires in 7 days, so don't sit on it.

Then there's the Work Simulation, which is 5 or 6 email-based modules where you respond to coworkers, debug, and prioritize under ambiguity. It can take 90 to 120 minutes. The Work Style Assessment is situational multiple choice where you pick the most and least appropriate response, around 10 minutes. These map to Amazon's Leadership Principles. Answer them like someone who bias-for-actions and takes ownership, not like someone hedging every call.

How should you practice coding for the loop?

This is the prep gap that bit people. The candidates we've worked with have been asked to write the entire solution, including reading input and printing output, then dry-run it step by step in front of the interviewer. If your whole practice routine is filling in a LeetCode function stub, you've never actually written input parsing or an output loop under pressure, and it shows.

So change how you practice. Write the full program, reading from input, building your structure, and printing the result. Then talk through it line by line with a sample input, tracking variables as you go. Do that out loud, alone, until it feels normal. Real loop questions that came up in 2025 included a monotonic stack problem like Daily Temperatures, a Koko Eating Bananas binary search, and a graph traversal with follow-ups on why you didn't use BFS, whether you could do it without recursion, and how to optimize space. The follow-ups are where they probe whether you understand your own solution.

Why is the Amazon interview timeline so slow?

What nobody warns you about is that the process is slow and uneven, and a long gap is not a rejection.

Full loops ran 3 to 4 months from OA to decision in 2025. We've seen candidates go OA in March, loop invite in May, virtual loop in July. Another applied through University Talent Acquisition, got the OA link 5 working days later, then sat through a month of silence before three interview rounds in a row and an offer. The worst case among the candidates we've worked with: cleared the OA in August, heard nothing for 2.5 months despite multiple follow-ups, got 24 hours' notice for the interview, then waited until mid-December for a rejection.

The other recurring mess is interviewers not showing up. We've consistently seen this play out one of a few ways: an interviewer never joins, one is 10 minutes late because his laptop wasn't charged, and another round gets rescheduled over a technical issue. The move that works is to wait 5 to 10 minutes, then email or call the recruiting team immediately. The candidates who did that got their slot rescheduled, often the same day. Save your recruiter's email before each round so you're not scrambling.

That unpredictable rhythm is exactly where things slip through the cracks. Amazon's timeline is famously uneven, 3 to 4 months from OA to offer with long gaps in between, and the Simplify's Job Tracker keeps your applications and recruiting milestones in one place so you always know where you are in the loop and when to follow up with your recruiter.

How do you prepare for Amazon's behavioral round?

Each loop interviewer is assigned specific Leadership Principles, and there's a Bar Raiser, an outside interviewer whose job is to confirm you'd be better than about half the people already in the role. The behavioral round is scored, not a warmup.

Some of our users who went through this had answers that were redundant across different questions, and they spent too long setting up the situation. The fix is the playbook: write about 8 STAR stories ahead of time, keep each to roughly a minute, and weight the Action part heaviest. Practice them out loud, ideally in a mock, because skipping mocks is exactly what wrecks people's nerves.

The best LP answers we've seen were built on evidence. Asked about a conflict from his own decision, one candidate wanted separate notification configs per operating system while his team wanted one. Instead of arguing, he built a quick proof of concept, showed the single-config script breaking on certain devices, then showed the before and after. The team aligned. That's how you answer "disagree and commit" or "dive deep," with a thing you built and a result, not an opinion you held.

Two more things worth knowing. Light system design or low-level design shows up at SDE-1 sometimes, not always, so spend a little time on basics like a rate limiter or a notification system rather than assuming design is senior-only. And a CS degree isn't required: we've seen a mechanical engineering grad and an applied-math major both make it deep into these loops. Garman himself said authoring a Java snippet matters less now than scoping problems and shipping working software (CRN), so lean into that framing when you talk about your projects.

The last piece is getting in front of the right people before the loop even starts. Amazon's new-grad pipeline favors candidates who show up with a referral or a warm intro from someone already inside, and Simplify Network surfaces your 1st and 2nd-degree connections at Amazon and AWS so you can ask for an introduction from people who know the bar, the team, and the real interview experience. In a process this long and uneven, a warm intro cuts through the noise.

When does Amazon open its new-grad SWE applications?

There isn't one clean window. Student timelines show OA links arriving in March, May, June, and August across recent cycles, so the postings open and close on a rolling basis as cohort caps fill. The practical move is to apply the day a posting goes live rather than waiting for a fall-only window that doesn't really exist. Set alerts and check often.

What total comp can a new-grad Amazon SDE expect?

Entry-level L4 SDE packages have landed in the rough range of $120K to $160K in total comp, which blends base salary, a sign-on bonus, and a four-year stock vest. Treat that as directional, since bands shift by location and cycle. Always confirm the breakdown in your written offer, because the sign-on front-loads the first two years before stock ramps up.

Does the Amazon SDE-1 loop include system design?

It depends on the team and possibly the region. Some 2025 candidates got a basic system design prompt or a low-level design problem in the Bar Raiser round, while a 2024 US new grad got none at all. Don't over-index on it, but spend a few hours on fundamentals like a rate limiter or a notification system so you're not caught flat.

How many STAR stories should I prepare for the Bar Raiser?

Around 8 is the number that holds up across a full loop without forcing you to reuse the same example. Map each story to two or three Leadership Principles so you have flexibility, keep every story to about a minute, and rehearse the Action portion most. The Bar Raiser is specifically looking for depth and ownership, not a tidy summary.

Can you get an Amazon SDE offer without a CS degree?

Yes. Candidates from mechanical engineering and applied math backgrounds have advanced deep into these loops and landed offers, often through University Talent Acquisition rather than a CS career fair. What the loop actually tests is problem scoping, clean coding, and Leadership Principle stories, so a strong project portfolio can carry more weight than the degree printed on your transcript.