Prices shown are a USD base. Your local-market price is calculated at checkout in your own currency, plus any local sales tax.
What is inside
20 chapters, in the order the interviews tend to ask them:
The Amazon interview loop: stages, timing and what each one screens for
The online assessment for software roles: what it measures
Why the behavioural interview decides the outcome
The Leadership Principles: the published list and how to use it honestly
Mapping behavioural questions to principles, with worked answers
The system design interview at Amazon scale
The coding round: data structures, analysis and the review
The Bar Raiser: the gatekeeper role as publicly described
The level ladder: from intern to principal and beyond
Promotion: the written packet and the calibration conversation
Compensation: bands, offers and the total rewards picture
AWS interviews: why the cloud organisation is treated separately
Two pizza teams, ownership and the cost of a service
Working backwards: the document before the code
Single threaded ownership, bias for action and the bias against it
The published reliability material and what it teaches you
The published systems papers: what they say and what they do not
Blue and green deployment, change management and the cost of a release
On call: the operations practice behind the published principles
Pace, returns, rumours and the limits of what is public
How the answers are built
Each chapter opens with the checklist the question is really testing. A few from this pack:
What is publicly documented is the existence of a multi-interview loop, a written debrief and a structured decision, not the exact number of interviews for a given role.
The published format is a timed coding exercise plus, for many roles, a workstyle component, and the specific delivery service has changed more than once.
A behavioural answer is a single sample, so the interviewer's job is to judge whether that instance is representative of how you usually behave.
The list is published verbatim at aboutamazon.com, so quoting it is safe and going beyond it into claims about internal practice is not.
A behavioural question is usually a proxy for one or two principles, so identifying the proxy is most of the preparation work.
The round is a conversation about requirements and trade-offs, and a design that starts from named components has already lost ground.
Questions this pack covers
Walk me through what the recruiter screen call actually covers before any loop is scheduled
How many interviews make up a typical loop for a software role
How long do I get on the online coding assessment, and how should I pace myself
Which programming languages am I allowed to use in the timed environment
Why does the behavioural round carry so much weight in the loop
What makes a behavioural answer specific enough to be believed
How many Leadership Principles are published, and where can I read them
What does customer obsession mean for a backend engineer
Each one is answered in full in the pack, with the reasoning written out rather than a bullet list.
