Amazon SDE-1 Interview Experience — Hyderabad, 2020 (Offer)
AmazonSDE I·Hyderabad·Interviewed October 2020OfferUpdated July 17, 2026
A candidate with about two years of experience applied to Amazon through the company's careers portal and heard nothing back for roughly a month. A recruiter later came across the profile on a job portal and reached out directly, saying it matched an open SDE-1 role in Hyderabad. The candidate agreed to move forward, and the process unfolded over several weeks.
It started with a timed online assessment covering two coding problems, followed by two back-to-back technical interviews on the same day about a week later, both conducted virtually over Amazon Chime with a shared codeshare link. A hiring manager round followed a few days after that, and a bar raiser round came about ten days after the hiring manager round. A confirmation call arrived about three days after the final round with news that the candidate had been selected.
How the process went
Application & recruiter contact
Applied through Amazon's careers portal and got no response for about a month. A recruiter later noticed the candidate's profile on a job portal and reached out because it matched an open SDE-1 role.
Online Assessment
A 90-minute test with two coding questions. Each round in the process was followed by a short debrief where the candidate had to explain the approach and its time and space complexity.
Two technical interviews
Scheduled back-to-back on the same day, about a week after the online assessment. Both were conducted virtually over Amazon Chime with a shared codeshare link, one hour each.
Hiring Manager round
Scheduled about three days after the technical interviews. Combined background and leadership-principle questions with one coding problem.
Bar Raiser round
The final round, roughly ten days after the hiring manager round. Included more leadership-principle questions plus two coding problems.
Decision
A confirmation call came about three days after the bar raiser round informing the candidate they had been selected.
Online Assessment
Two coding problems under time pressure · 90 minutes
- Given a list of song durations and a target journey length, pick two songs whose combined length finishes the trip with a fixed buffer to spare — a two-sum style problem solved by sorting and using two pointers.
- Find the shortest path between a source and destination in a grid, moving in four directions, solved with BFS.
A short debrief followed the coding portion, where the candidate had to explain the approach and its time and space complexity — a format repeated after every round in the process.
Technical Interview 1
Search and grid traversal problems on a shared codeshare link · 1 hour
- In a sorted string, count how many times a given character occurs, implemented with two binary-search helper functions marking the first and last occurrence.
- On a grid where some cells contain fire, determine whether a person starting at a given cell can reach the edge without passing through fire, solved with BFS.
- Follow-up: the fire spreads to adjacent cells each turn, so the search has to track fire and the person's movement together — a variant of the classic 'rotting oranges' pattern, handled with two queues.
The candidate made a point of covering edge cases and commenting the code before being asked, after the interviewer had flagged missing edge cases on the first question.
Technical Interview 2
Resume walkthrough plus BFS and sliding-window problems · 1 hour
- Walkthrough of AWS experience from the resume, including an explanation of how ECS (Elastic Container Service) works.
- In a binary matrix of 0s and 1s, find the maximum distance from any 0 cell to the nearest 1, solved with BFS (related to the '01 Matrix' problem, but looking for the farthest rather than nearest cell).
- Given an unsorted array and two integers k and t, find two indices i and j where the value difference is at most t and the index difference is at most k; asked to optimize past brute force toward roughly O(n log k) using a maintained sorted window.
The interviewer pointed out that inserting into the maintained sorted window was still an O(n) operation and wasn't fully satisfied with the fix; the candidate didn't close that gap before time ran out but still advanced to the next stage.
Hiring Manager Round
Background discussion and leadership-principle questions, plus one coding problem · 1 hour
- Questions about past college and work projects, technology choices, challenges faced, and reasons for wanting to leave the current company.
- Determine whether a given binary tree is symmetric when folded down the middle — a variant of the classic symmetric-tree check, solved recursively.
Most of the hour went to the background discussion rather than coding; the interviewer had significant industry experience and probed follow-ups closely.
Bar Raiser Round
Leadership-principle questions plus two coding problems · 1 hour
- Leadership-principle questions about handling a tight deadline and about a time the candidate took initiative that helped the team.
- Given a list of sentences, build an index mapping each word to the lines it appears in, solved with a hash map.
- Implement an LRU cache from scratch without built-in data structures, using a doubly linked list and hash map; the interviewer also asked about OOP concepts like polymorphism while the classes were being written.
The candidate didn't finish writing the LRU cache implementation before time ran out, but the interviewer said they were satisfied with the approach shown.
Key takeaways
- Explain the approach and call out edge cases before writing code — several interviewers in this process noted it explicitly as something they were evaluating.
- Expect a short 'explain your complexity' debrief after every coding question, not just at the end of the round — budget time for it.
- Leadership-principle stories carried real weight in the hiring manager and bar raiser rounds; have concrete examples ready rather than improvising on the spot.
- Not fully closing a follow-up (the O(n) insertion gap in the second technical interview) didn't end the process — a clearly explained approach was enough to move forward.
- A steady practice routine over several months, weighted toward medium and hard problems, was what the candidate credited most for feeling interview-ready.
Practice a Amazon interview
Rehearse out loud against the kinds of questions in this story — with an AI interviewer that asks follow-ups.
Practice this interviewSource
The questions and process facts come from the candidate's public write-up, linked below. The retelling above is our own summary.
Candidate's public write-up on LeetCode Discuss