winkle
Back

Interview · Technical

Cloud and platform engineer

Covers infrastructure design, deployment pipelines, reliability, on-call, cost and the internal platform that other engineers build on. Suits mid to staff-level cloud, platform and reliability hires. Follow-ups push for real numbers, failure modes and how changes are rolled back.

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

Questions
7 of 17
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

    • Infrastructure design30%
    • Reliability and operations25%
    • Automation and developer experience25%
    • Cost and security 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.

  • Infrastructure design30%
    Designs secure, resilient cloud setups that fit the workload.
  • Reliability and operations25%
    Runs services calmly, measures health and learns from failure.
  • Automation and developer experience25%
    Automates delivery so other engineers ship safely on their own.
  • Cost and security judgement20%
    Keeps spend and access under control without blocking teams.

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