DevOps and SRE interviews emphasize reliability, automation, and calm execution during failure. Expect discussions of CI/CD pipelines, container orchestration, infrastructure as code, and observability stacks. Scenario questions often describe outages—bad deploy, certificate expiry, cascading retries—and ask how you detect, mitigate, and prevent recurrence. Coding may include scripting, parsing logs, or writing small automation tools rather than leetcode-style algorithms. Interviewers probe blameless postmortem culture, error budgets, and when to stop feature work for toil reduction. Security and compliance appear through secrets management, least privilege IAM, and audit trails. Candidates who only know kubectl cheatsheets without understanding SLOs or capacity planning struggle. Practice tying every tool choice to risk reduction and measurable service health. Expect questions on FinOps tagging, rightsizing, and when managed services beat self-hosted complexity. Discuss progressive delivery: canaries, automatic rollbacks, and metric-based promotion. Interviewers probe whether you treat infrastructure changes with the same review rigor as application code. Mention participation in security incident drills and patching cadence. SRE culture fit often matters as much as tool familiarity.
Recruiter distinguishes SRE from platform DevOps focus and on-call expectations. Phone screen: walk through a CI pipeline you built—stages, test gates, artifact signing, and rollback triggers; follow-up on a time deploy caused an incident. Onsite round one: incident simulation—latency spike after a config change in Kubernetes; candidate narrates dashboards, hypotheses, mitigation, and comms template for stakeholders. Round two: design a multi-account AWS landing zone with Terraform modules, state locking, and drift detection. Round three: practical—write a script to parse nginx logs for top error URLs in the last hour and discuss scaling the approach. Round four: behavioral on reducing toil via automation and pushing back on unrealistic availability promises. Panel debrief weighs operational judgment, automation craft, and collaboration with development teams.
Junior DevOps roles focus on runbooks, guided changes, and learning monitoring tools. Mid-level owns services in production with on-call rotation and meaningful automation. Senior SRE influences architecture, error budgets, and incident command. Staff platform engineers set org standards for IaC and deployment safety. Inflated Kubernetes buzzwords without incident stories fail quickly at senior bars. Structured practice with written rubrics helps you compare sessions week over week and spot recurring gaps before recruiters schedule onsite loops. Treat each mock as a packet exercise: summarize strengths, risks, and follow-up study topics immediately afterward. Structured practice with written rubrics helps you compare sessions week over week and spot recurring gaps before recruiters schedule onsite loops. Treat each mock as a packet exercise: summarize strengths, risks, and follow-up study topics immediately afterward. Structured practice with written rubrics helps you compare sessions week over week and spot recurring gaps before recruiters schedule onsite loops. Treat each mock as a packet exercise: summarize strengths, risks, and follow-up study topics immediately afterward.
Practice outage scenarios before real pager duty
Learn CI/CD patterns that pass senior SRE review
Build confidence explaining rollback and feature flag strategies
Understand Kubernetes pitfalls through guided failures
Develop postmortem writing skills with rubric feedback
Prepare for scripting rounds with realistic log problems
Align narratives with reliability culture expectations
Reduce blind spots in IAM and secrets management
Walk through debugging elevated 5xx after a blue-green deploy
Design CI for monorepo with affected tests and canary deploy
Explain how you would implement zero-downtime database migration support
Choose monitoring signals for a payment API SLO of 99.9 percent
Write automation to enforce label standards on Kubernetes namespaces
Run local k8s and break things intentionally—probes, limits, and DNS
Study Google SRE book chapters on SLOs and postmortems
Build a sample Terraform stack with remote state and modules
Practice incident timelines aloud with explicit customer impact
Drill Linux debugging: ss, journalctl, strace basics
Describe secrets rotation without downtime for a stateful app
How do you prevent retry storms during partial outages?
Tell me about automating away repetitive manual work at scale
Prepare STAR stories for Sev incidents you led or supported
Review CIS benchmarks or well-architected framework pillars at high level
Time-box pipeline whiteboard to include rollback and audit trail
