Amazon
Software Development Engineer (SDE-1)
Selected Medium
- Interviewed
- August 2026
- Experience
- Fresher (2026 batch)
- Location
- Bengaluru
- Shared by
- Anonymous
Overview
The process had four stages over about three weeks: an online assessment, two technical interviews and a final Bar Raiser round. The recruiter shared the schedule in advance, which made it easy to plan revision. Each technical round was 45 to 60 minutes and the interviewers were friendly but asked a lot of follow-up questions. Thinking aloud and explaining trade-offs mattered more than reaching the perfect solution quickly.
Interview rounds
-
1
Online Assessment
Two coding problems in 90 minutes, plus a short work-style questionnaire. One problem was an array and sliding window question, the other a medium graph traversal problem. Passing all the visible test cases and handling edge cases cleanly was enough to move ahead. -
2
Technical Interview 1 (DSA)
Two problems on a shared editor. The first was about finding the longest substring with at most K distinct characters. The second was to merge overlapping intervals. The interviewer asked for time and space complexity for each and for a better approach after the first working solution. -
3
Technical Interview 2 (Problem solving and design basics)
One tree problem (lowest common ancestor) and a discussion on designing a simple URL shortener: the API, how to generate unique IDs and what to store in the database. The interviewer cared more about reasoning and trade-offs than about a complete design. -
4
Bar Raiser (Behavioural)
Mostly behavioural questions based on Amazon's leadership principles, such as "Tell me about a time you disagreed with a teammate" and "Describe a project you owned end to end". There was one short coding question near the end to check clarity of thought.
Tips and takeaways
Practise explaining your approach out loud before you write any code.
Revise arrays, hash maps, trees and graphs, plus a few medium-level dynamic programming problems.
Prepare two or three real stories from your projects for the Bar Raiser, using the situation, action and result format.
Ask clarifying questions and state your edge cases before coding.
Revise arrays, hash maps, trees and graphs, plus a few medium-level dynamic programming problems.
Prepare two or three real stories from your projects for the Bar Raiser, using the situation, action and result format.
Ask clarifying questions and state your edge cases before coding.
