winkle
Back

Interview · Technical

DevOps and site reliability

Covers reliability targets, deployment, incident response, operational tooling, capacity, recovery and cost, answered in words. Suits mid-level to staff DevOps, SRE and platform engineers. Follow-ups ask how the candidate would know it worked and what they would do when it didn't.

Suits: DevOps engineer, Site reliability engineer, Platform engineer, Infrastructure engineer, Cloud engineer

Questions
7 of 18
Length
35 min
Format
Voice or typed
Levels
Mid to Staff
See this interview on a 30-minute call.
AI interviewerScored
Example

  1. Interviewer: Tell me about a time you changed someone's mind at work. How did you go about it?

  2. Candidate: Our team wanted to rebuild the billing page from scratch, and I thought it was the wrong call, so we put together a plan to…

  3. Follow-up

    Interviewer: You said "we". What did you say yourself, and what finally changed their mind?

  4. Scored on

    • Reliability engineering30%
    • Incident response25%
    • Automation and delivery25%
    • Cost and judgement20%

    Score, reasons and recording. Your team decides.

An example exchange. This interview's own questions open when you use it.

What it listens for, and how much each part counts.

Every answer is scored against this guide, with the reasoning written beside the score. You get the recording or the written answers too, and your team makes the call.

  • Reliability engineering30%
    Designs for failure with clear targets, recovery and capacity.
  • Incident response25%
    Stops harm fast, communicates and learns without blame.
  • Automation and delivery25%
    Builds pipelines and tooling that make change safe.
  • Cost and judgement20%
    Balances reliability, cost and team needs sensibly.

Send it alongside

All interviews

  • Coding interview: problem solving

    Engineering · Technical

    Four classic problems, solved in words, that show how a candidate reasons about correctness and cost.

    Listens for

    • Problem understanding
    • Approach and correctness
    • Edge cases
    • Complexity reasoning
    Typed

    4 of 18 questions · 35 min · All levels

  • System design: backend

    Engineering · System design

    One notification service at burst scale, designed stage by stage to test estimates, scaling and failure.

    Listens for

    • Requirements and estimation
    • API and data design
    • Scale and throughput
    • Reliability
    • Trade-off judgement
    Voice or typed

    7 stages · 50 min · Senior to Staff

  • Frontend engineering deep-dive

    Engineering · Technical

    Tests real frontend judgement: performance on weak devices, state, accessibility, rendering and debugging.

    Listens for

    • Performance
    • Architecture and state
    • Accessibility
    • Debugging
    • Trade-offs and communication
    Voice or typed

    5 of 16 questions · 25 min · Mid to Staff