Amazon Cloud & Platform Engineer interviews, as candidates describe them, combine Leadership Principles stories with hands-on networking, Linux and AWS questions. Here is what four candidates report and how to prepare.
$118K
Avg. Base Comp
$160K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Four candidates who interviewed for Amazon's Cloud & Platform Engineer role describe a similar mix: Leadership Principles stories paired with practical networking, Linux and AWS fundamentals. None of them describes a coding-heavy loop. The technical questions were practical and focused on explaining how things work.
Networking came up in every account that detailed technical content. One candidate was asked how DNS works. Another was asked to narrate everything that happens when a branch-office laptop plugged into a switch downloads patches from a central server. A third was asked about TCP versus UDP and what happens when you visit www.amazon.com. Linux questions were basic, such as listing processes, and AWS questions were general.
Behavioral questions were specific. Candidates were asked about carrying a difficult project to completion, automating a customer's process, and how they had applied a leadership principle in their own work. One was expected to answer in STAR format. One candidate was also asked about Hadoop without hands-on experience, and another got an unexpected question on free versus evaporative cooling. Expect an occasional off-profile question and stay calm when it happens.
The reported formats differ. One loop was three back-to-back 45-minute interviews after a screen. Another was five rounds with senior network engineers, a manager and HR. Another was four 45-minute interviews after an online assessment and HR call. A referred internal candidate had a tech lead round and an HR round. Outcomes were mixed, so prepare for both the behavioral and technical sides.
Synthesized from 8 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Amazon process.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Amazon
Given two sorted lists, write a function to merge them into one sorted list.
| Question | |
|---|---|
| Get Top N Frequent Words | |
| Prime to N | |
| Recurring Character | |
| Permutation Palindrome | |
| Weekly Aggregation | |
| Find the First Non-Repeating Character in a String | |
| Friendship Timeline | |
| Payment Data Pipeline | |
| Impute Median | |
| Normalize Grades | |
| Real-Time Transaction Streaming | |
| Nearest Common Ancestor | |
| String Mapping | |
| Cyclic Detection | |
| Flatten JSON | |
| Valid Anagram | |
| Finding The Mode | |
| Longest Increasing Subsequence | |
| Term Frequency | |
| Radix Addition | |
| Target Indices | |
| Hurdles In Data Projects | |
| How Many Friends | |
| Find the Missing Element | |
| Word Frequency | |
| Priority Queue Using Linked List | |
| Centralized Event Ingestion | |
| Move Zeros Back | |
| Real-Time Hashtag Partitioning |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report different openings. One mentions an initial screening, and another an online assessment followed by an HR call and a hiring manager interview. A referred internal candidate went straight to a tech lead round. Have your Leadership Principles stories ready early.
Candidates report practical questions rather than algorithm puzzles. Topics included how DNS works, TCP versus UDP, listing Linux processes, general AWS questions, and walking through a full network flow from laptop to patch server. Expect to explain from first principles.
Behavioral questions appear in every reported loop. Candidates describe being asked about seeing a difficult project through, automating a customer process, and applying a leadership principle in real work. At least one candidate was expected to use STAR structure, so prepare concise stories.
Reported loop shapes vary: three 45-minute interviews with different AWS teams, four 45-minute interviews, or five rounds including senior network engineers, a manager and HR. Format may depend on team and hiring path, so confirm with your recruiter.
Candidates report mixed outcomes: one accepted an offer within days, one declined an offer, and two were rejected. One reports feedback a few days after the loop, and another got no feedback. Timelines varied, including a long gap before one loop.
