Amazon
SDE Intern
Not shared Hard
- Interviewed
- August 2025
- Experience
- Student (off campus)
- Location
- Online
- Shared by
- Anonymous
Overview
A student applied through a LinkedIn post in early July 2025 and heard back at the end of the month. The process then ran in stages: a hiring interest form, a Mettl coding challenge, a second online assessment on HackerRank, a recruiter call to schedule, and one virtual interview on Amazon Chime. The final interview was with two senior software engineers and had two live coding problems. The author wrote the post the day after the interview and was still waiting for the result, so the outcome is unknown.
Interview rounds
-
1
Application and Interest Form
Applied on LinkedIn, then received a mail asking for a Hiring Interest Form with role, location, duration and qualification details. A "Next Step" mail followed about a week later, announcing a coding challenge. -
2
Mettl Coding Challenge (1 hour 30 minutes, 9 sections)
One medium-level dynamic programming coding question plus eight MCQ sections covering data structures, algorithms, operating systems, databases, Linux, pseudocode, computer networks and software testing. -
3
HackerRank Online Assessment (1 hour 45 minutes, 4 sections)
A timed coding challenge with two medium to hard questions, plus three untimed sections: Working at Amazon, Your Engineering Work Style, and Your Work Style. All four sections had to be completed. -
4
Virtual Interview on Amazon Chime
Two senior engineers joined, and the candidate introduced themselves and then used a live coding notepad. Problem 1 was a hard-level array problem framed as an Amazon scenario. The candidate explained brute force and why it was not optimal, optimized it, dry-ran it on the interviewers' input, and covered edge cases and follow-ups. Problem 2 was a medium-level graph problem. The candidate struggled at first, the interviewers guided them with questions, and they then coded the solution and handled follow-up optimizations. Interviewers signalled they were satisfied, and HR was to follow up with results.
Tips and takeaways
Do not neglect the untimed work-style sections of the HackerRank assessment, because all four sections must be completed to stay in consideration. For the interview, narrate your thinking: brute force first, why it is not good enough, then the optimal approach with time and space complexity, a dry run and edge cases. When you are stuck, treat the interviewers' guiding questions as hints and answer them. Expect rescheduling, so keep your calendar flexible. Revise OS, DBMS, Linux, networks and software testing basics for the MCQ sections.
