A hands-on platform interview covering pipeline design, infrastructure as code and how you behave in the first minutes of an incident.
1. Walk me through what happens, step by step, between a developer merging to main and that change serving production traffic in your most recent setup.
~3 minChecks whether the candidate owns the full delivery path rather than a single tool.
2. A deployment goes out at 16:40 and error rates on one service triple within four minutes. Talk me through your first fifteen minutes.
~3 minAssesses incident instinct: stabilise first, diagnose second.
3. How do you structure Terraform across multiple environments and teams so state stays safe and changes stay reviewable?
~3 minLooks for real infrastructure-as-code experience beyond a single root module.
4. Your Kubernetes cluster costs 40% more than budget but latency SLOs are comfortably met. What do you investigate and what trade-offs do you present?
~3 minTests cost-versus-reliability judgement and stakeholder framing.
5. Tell me about a time reliability work you argued for was deprioritised. What did you do?
~3 minBehavioural signal on influence without authority.
Warm-up & context · 4 min
Interviewer intro, your background, how the session runs.
Core questions · 21 min
Role-specific questions with live follow-ups based on your answers.
Deep dive · 7 min
One topic explored to the edge of your experience.
Your questions & wrap · 4 min
Close the loop and hand over to feedback generation.
Design a multi-region delivery and rollback strategy, then defend the operational cost of your choices.
A friendly first-round call: fundamentals of pipelines, containers and Linux, plus how you learn on the job.
API design, testing strategy and performance debugging, grounded in code you have actually shipped.