The DevOps interview process, round by round

There is no verified universal round count or completion time for DevOps hiring. Ask for the stage list, duration, language choices, take-home expectations and any later approval or team-matching steps.

The five types below organize practice. Employers can combine them or omit some. Amazon's official hiring pages describe its own process; they do not establish the process at another company.

Prepare a short account of your responsibilities and one recent technical decision. Explain which systems you operated directly and which you encountered as a user.

Ask whether this stage is a recruiter discussion, a technical screen or an assessment. Use the answer to prepare the right depth of detail.

Practise a failure in an unfamiliar system. Ask for symptoms and recent changes, propose a check and explain the decision each possible result would support.

Describe a safe mitigation when users are affected. Avoid listing commands without saying what evidence they would produce.

Clarify the service objective, workload and failure assumptions. Estimate capacity, propose a design and revisit the numbers as the design changes. Google's published NALSD method is useful preparation; its existence does not confirm a NALSD round in every Google SRE loop.

Be ready to revise your proposal when a new constraint makes it unsuitable. Explain the trade-off you are accepting.

A role may assess scripting, application code, algorithms or an infrastructure exercise. Ask which language and tools are permitted, including documentation and AI assistance.

Practise errors, large inputs and partial completion. Explain whether a retry can duplicate an action and show how you would test that behavior.

Prepare examples of decisions, disagreements and work that did not go to plan. Separate your actions from the team's work and state what you learned. Never invent an outage to fill a story template.

Amazon publishes Leadership Principles and describes their role in hiring. Other employers use different frameworks; ask what your interview will cover instead of assuming an equal weighting across companies.

For an illustrative four-week plan, use the first week to diagnose gaps, the next two for the weakest confirmed round types and the final week for mocks and corrections. Change the allocation after feedback.

With one week, confirm the format immediately. Rehearse a relevant diagnosis, one design with arithmetic, a coding exercise and a few accurate experience stories. Do not abandon a confirmed round because a generic preparation guide ranks it lower.