Amazon Software Development Engineer Intern Interview Experience
Amazon · Intern · Software Engineer
The weird part is you do not have to run the code, but that almost makes it harder because they really want the optimal answer right away. My interview problem was straight-up lowest common ancestor in a BST.
Interview process
I interviewed in March 2025 for the Seattle SDE intern role. My whole process was just an online assessment and then one interview, with no recruiter screen or extra technical rounds in between. That last interview packed everything into one session, about 25 to 30 minutes of coding and 15 minutes of behavioral questions. It felt really streamlined because they put all the evaluation into that one final conversation.
Interview rounds · 2
- 1
Online assessment
Data Structures & AlgorithmsTechnicalThe OA was just two coding questions, one more like a normal BFS/tree traversal problem and one optimization problem about packaging and how to best process it.
- Q1. Use BFS to traverse through a tree and find different nodes.
- Q2. Solve an optimization problem about packaging and how to best process the packaging.
- 2
Final / onsite round
Data Structures & AlgorithmsBehavioralTechnicalThe only interview round combined everything into one session, with about 25 to 30 minutes for coding and around 15 minutes for leadership principles, and I did not have to run my code.
Q1. Find the lowest common ancestor in a BST given nodes P and Q.
How they answeredI treated it like a tougher LeetCode problem and went for the optimal solution right away. I used DFS and compared the left and right side values to see whether they matched P or Q, then used that to identify the ancestor. They did not really add twists after that, so once I got to the optimal answer, that was enough.
- Q2. If you're designing an application and the user is not happy with a feature, or engagement is dropping, how would you handle that?
- Q3. What do you do if somebody in a higher position than you on your team is wrong?
Tips from the candidate
I would prep for this like they want the optimal answer fast, not just something that works. You do not have to run the code, so it helps to practice talking through your logic really clearly on the spot. The coding felt more graph focused than other places I interviewed, and my actual question was lowest common ancestor in a BST. For the OA, I saw one BFS/tree traversal problem and one packaging optimization problem. I would also be ready for leadership principles, especially customer obsession and have backbone.
Company culture
It felt like they really value you being independent and not asking for help excessively. That was the main vibe I got from going through it.