Infrastructure and cloud engineer interviews (platform, DevOps, cloud data, cloud security, data platform and MLOps) test judgment, not vocabulary. You get scenarios, you narrate your reasoning, and you win by describing decisions you actually made when something broke.

If you keep stalling at the same stage of these loops, it is rarely a knowledge gap. You are answering like a textbook, and the panel wants an operator. This guide covers what every one of these loops shares, then where the six roles split.

What do all of these engineering interviews have in common?

Every loop rewards the same five habits. Learn them once and they carry across all six roles.

  • Scenarios beat definitions. Panels have mostly dropped "what is CI/CD" trivia. They ask "walk me through the last time X broke." Nearly every question is a disguised "tell me about a time."
  • Ownership language. "We fixed it" sounds like you watched. "I found the root cause by checking X, then decided to do Y" sounds like you acted. Mix "I" and "we" honestly.
  • Incident stories end in a systemic change. A new alert, a new test, a new runbook. Candidates who skip the postmortem habit look like they will repeat the outage.
  • Failure modes before you are asked. In any design round, say what breaks first, what happens at 2am, and how you would notice.
  • Cost and tradeoffs, stated plainly. "It depends" is not an answer. Name the tool, name what you rejected, and say why.

One more shared rule: narrate out loud. Interviewers grade the reasoning trail. Silence during a scenario reads worse than an imperfect answer spoken clearly.

Short version: bring lived incidents, name your tradeoffs, and talk through your thinking.

How do platform, DevOps, cloud data, cloud security, data platform and MLOps interviews differ?

The core question each panel asks is different, and that decides which answers land. Use this table to find your loop, then read that role's section below.

RoleCore question the panel is askingHeaviest topicsWhere candidates lose the room
Platform EngineerCan you build something other engineers will actually want to use?Golden paths, self-service tooling, Kubernetes abstractions, developer experience metricsAnswering every question like it is about uptime, never about adoption
Data Platform EngineerCan you own the shared data infrastructure other teams build on?Pipeline design, multi-tenant access, orchestration, cost, disaster recoveryPrepping only one lane of a hybrid data, platform and SRE loop
DevOps EngineerCan you reason about a broken pipeline under time pressure?CI/CD failure modes, Terraform state, Kubernetes debugging, secretsTextbook answers, and freezing in the hands-on lab
Cloud Data EngineerCan you build and debug pipelines that run at real scale?SQL at scale, pipeline architecture, failure scenarios, cloud-specific services, costCorrect SQL that runs badly, and abstract design with no failure modes
Cloud Security EngineerIs least privilege your instinct, and can you explain risk to non-security people?IAM, architecture review, incident response, compliance translationOver-prepping tools and certifications, under-prepping judgment
MLOps EngineerDoes the model keep performing correctly in production, and can you prove it?Training pipelines, serving, drift monitoring, versioning, rollbackPrepping like a pure data scientist or a pure DevOps hire, not the seam between

Plain version: platform asks about adoption, DevOps about delivery, cloud security about judgment, cloud data about scale, data platform about shared ownership, and MLOps about what happens after launch.

What do platform engineer interviews ask?

Platform engineer interviews test whether you can design internal developer platforms that reduce cognitive load for other engineers. Your users are internal developers, so the interview borrows from product management.

Here is the mistake strong SREs make. They answer everything as uptime. Platform engineering is uptime and velocity, and the panel is probing the second half. Without developer experience in your answers, you look like a DevOps engineer with a fancier title.

The contrast with neighboring interviews is simple. An SRE gets "walk me through an incident." A platform engineer gets "walk me through a self-service tool you built and how you got teams to adopt it."

Expect these topics:

  • Kubernetes abstraction design. "How would you let application teams deploy without touching Kubernetes YAML?" Think Backstage, Crossplane or custom operators, not raw manifests.
  • Infrastructure as code at organizational scale. Not "what is Terraform" but how you structure modules across many teams without everyone copy-pasting the same broken pattern.
  • CI/CD as a shared service. How you version and roll back a shared pipeline template without breaking every team at once.
  • Cost guardrails. How you give teams autonomy while preventing runaway cloud spend.

How do you answer a golden path question?

A golden path is the officially supported, opinionated way to do a common task, like deploying a new service. Think of the included breakfast at a hotel: guests can eat anywhere in the city, but one good, fast option means most never wander off.

Structure your answer in three layers:

  1. The developer-facing interface. A CLI command, a template repo or a Backstage software template.
  2. Guardrails by default. Security scanning, resource limits, logging and tracing wired up automatically.
  3. An escape hatch. A documented way out for teams with legitimate custom needs.

Panels listen hardest for the third layer. A platform with no escape hatch is one teams route around.

Platform system design prompts look like "design a multi-tenant CI/CD system for 50 teams" or "design a self-service database provisioning system with cost guardrails." They grade multi-tenant isolation, safe versioning of shared components, and observability of the platform itself. Behavioral questions follow the same logic: "describe a time you built something nobody used," and "how do you measure platform success?" Good answers cite developer surveys, time-to-first-deploy, ticket trends and golden path adoption.

What does a data platform engineer interview test?

A data platform engineer interview tests data engineering fundamentals, infrastructure judgment and operational maturity in one loop. This role is posted as "data engineer," "platform engineer" or "infrastructure engineer," but the loop rarely matches the title. You can get a pipeline question, a Kubernetes question and an outage walkthrough in the same sitting.

The lens matters. A data engineer answer optimizes one pipeline. A data platform answer optimizes blast radius, multi-tenancy and failure isolation, because a hundred other engineers will build on your decision.

Most companies run four to six rounds: a SQL and data modeling screen, a coding round (Python, Scala or Java), data infrastructure system design, a platform and DevOps deep dive, an incident scenario, and a behavioral round with stakeholders. Startups lean on hands-on coding and ownership stories. Larger companies lean on system design and cross-team scenarios.

Questions to rehearse:

  • Design a pipeline that ingests five sources with different schemas and SLAs. Cover schema evolution, dead-letter handling and backfill.
  • How do you handle late-arriving or out-of-order data? Watermarking, windowing, idempotent writes.
  • Write SQL for duplicates and the second-most-recent event per user. Practice ROW_NUMBER() and LAG() cold.
  • Batch or streaming? The right answer is usually batch until latency requirements force a change.
  • Design multi-tenant access to a shared data lake so one team's bad query cannot starve another's compute.
  • How do you handle a bad deploy that silently corrupts data instead of crashing loudly?
  • How would you design disaster recovery for a petabyte-scale warehouse? Talk RPO/RTO and replication cost.

For the system design round, use a repeatable frame. Clarify scale and constraints first. Sketch the flow from sources to serving. State storage and format tradeoffs. Raise failure modes before being asked. Cover cost ownership across teams. Close with data quality checks and freshness alerts for silent failures. If you are weighing which data role fits you at all, this breakdown of data engineer vs analytics engineer vs BI developer helps.

What are the most common DevOps engineer interview questions in 2026?

DevOps interviews in 2026 front-load scenarios on CI/CD, Terraform, Kubernetes, observability and security. Hiring managers learned that plenty of candidates can talk about Kubernetes but have never debugged a crash-looping pod at 2am. The bar moved from "do you know the tool" to "have you operated it under stress."

Questions that show up repeatedly:

  • "A deploy just broke production but all tests passed. Walk me through your first ten minutes."
  • "How do you choose between blue-green, canary and rolling deploys for a stateful service?"
  • "Your Terraform apply failed halfway. State no longer matches reality. What do you do?"
  • "When would you not use IaC for a piece of infrastructure?"
  • "A pod is stuck in CrashLoopBackOff. What is your debugging order?"
  • "How do you decide what pages someone versus what stays on a dashboard?"
  • "A developer committed an API key. Walk through your response, start to finish."

The typical loop runs four to six rounds: recruiter screen, technical screen (Python, Bash or Go, Linux, git), infrastructure design, a hands-on lab where you debug a broken cluster or pipeline live, a behavioral and incident round, and a hiring manager conversation. The hands-on lab is where most candidates lose the offer, not the whiteboard.

Common offer-killers: definitions instead of decisions, no ownership language, no postmortem habit, underselling scripting skills, and not asking about on-call load. That last one signals you have never carried a pager.

What do cloud data engineer interviews focus on?

Cloud data engineer interviews focus on pipeline architecture, SQL and transformation logic, and troubleshooting production failures. You spend little time on LeetCode-style algorithms and a lot of time explaining why you chose Spark over Flink or how you would debug a pipeline dropping records at 2 AM.

  • SQL at scale. Window functions, CTEs, recursive CTEs, and follow-ups like "what if the left table has 500 million rows and the right has 2 billion?" A correct query that runs inefficiently fails the unstated test.
  • Pipeline design. Ingest user events, compute daily metrics, serve dashboards and ML models. Strong answers name tools (Kafka vs Kinesis, Spark vs Presto, Airflow vs dbt), say what breaks first under load, and explain what you rejected.
  • Troubleshooting. "A pipeline that ran fine for six months suddenly fails." Check logs, verify upstream systems, test a subset of data, look for schema or data quality shifts, review infrastructure changes, and quantify the blast radius.
  • Cloud-specific depth. AWS shops ask about S3 partitioning and Glue vs EMR. GCP shops ask about BigQuery slot reservations and dataset-level IAM. Azure shops ask about Synapse with Data Lake Storage.
  • Cost. Compression (Parquet vs CSV can be a 10x difference), partition pruning, reserved vs on-demand capacity, columnar storage.

Read the target company's engineering blog and learn their data stack. If they run BigQuery, do not show up knowing only Spark.

What do cloud security engineer interviews ask?

Cloud security engineer interviews center on IAM design, live misconfiguration or breach response, and explaining tradeoffs to non-security people. Interviewers stop caring about certifications early and listen for how you think under ambiguity. A panel usually splits the load: one person on IAM, one on architecture and incidents, one on behavioral and stakeholders.

Which IAM questions come up?

IAM is the most tested area because real breaches start with overprivileged roles, stale service accounts and wildcard permissions. Expect:

  • "Design an IAM policy for a microservice that reads one database and writes one queue." Scoped resources, not "AdministratorAccess for now."
  • "How do you handle cross-account access?" Assume-role patterns, service principals or workload identity federation, and why long-lived keys are a liability.
  • "A developer needs S3 access to one bucket for 48 hours." Time-bound, just-in-time, revoked on schedule.
  • "How do you find roles with unused permissions?" Access analyzer tooling, not a manual audit.

Least privilege should show up unprompted in your answer. If the interviewer has to drag it out of you, you lose points.

How do you answer an incident response question?

Say the steps out loud, in order. It signals you have run an incident before.

  1. Confirm the alert is real.
  2. Contain: isolate the instance, revoke the credential, disable the exposed key.
  3. Preserve evidence: snapshot, pull logs, do not just terminate.
  4. Assess blast radius: what else did that credential touch?
  5. Communicate up before you have the full picture.
  6. Fix the root cause, including the policy that allowed the overprivilege.
  7. Write the postmortem and name what changes.

Architecture questions are scenario diagnostics: segmenting a VPC for a multi-tier app, securing secrets with rotation instead of env vars, designing zero-trust without just adding a VPN, or fixing 0.0.0.0/0 on port 22 without breaking access. Compliance questions reward business language: exposure, likelihood, cost of a breach versus cost of delay. Name SOC 2, ISO 27001 or NIST CSF only if you can say what the control protects against. If a "why are you leaving" question rides along in the same loop, this guide on answering without trashing your old boss covers it.

What do MLOps engineer interviews test?

MLOps interviews test whether you can move a model from a notebook to a production system that stays reliable. They assume you can train a model and run infrastructure, then probe the connective tissue. Data science stops at "the model works." DevOps stops at "the service is up." MLOps asks what happens weeks later when the service is up but the predictions have quietly gone bad.

If a question ends at deployment, it is a DevOps question in an MLOps costume. The real ones ask what happens after.

  • Pipelines and data. Design a weekly retraining pipeline with real orchestration (Airflow, Kubeflow Pipelines, Dagster). Handle training-serving skew with a feature store or shared feature layer. Version datasets with DVC or lakeFS. To reproduce a model from months ago, pin three things: code version, data version and the dependency environment.
  • Serving. Batch vs real-time inference (fraud scoring is real-time, monthly churn can be batch). Containerized deployment with TorchServe, Triton, BentoML or a FastAPI wrapper. Shadow deployments run the new model silently beside the old one. Canary deployments send it a small slice of live traffic. Rollback means a registry with version pinned, no retraining required.
  • Monitoring and drift. Data drift is the input distribution changing. Concept drift is the relationship between inputs and correct outputs changing. The fix differs. Monitor prediction distribution, latency, feature distributions and business outcomes, and watch segment-level numbers because the aggregate can hide a failure in one slice.
  • System design. Narrow scope first: traffic, latency, scheduled or triggered retraining. Then data flow, training, serving, registry, monitoring and the feedback loop. Tell it as cause and effect, not a tool list.

Have two incident stories ready: one infrastructure failure and one silent model-quality failure. If yours came from a side project, say so.

How do you prepare for any of these interviews without wasting time?

Study narrow and deep, using your own incident history as the material. Broad, shallow prep is how people end up reciting definitions.

  1. Write up your last few production incidents. Two paragraphs each: root cause, fix, and the process change afterward.
  2. Map every tool in the job description to a real project. "Familiar with" does not survive follow-ups.
  3. Pick one orchestration tool and one warehouse, serving framework or cloud service to go deep on. Know failure modes, scaling limits and cost behavior.
  4. Re-derive your last two architecture decisions. Be ready to say what you would change now.
  5. Rebuild one pipeline or cluster config from memory. If you cannot, you will freeze in a hands-on lab.
  6. Practice narrating out loud. Narrow scope before you name a single tool.
  7. Prepare questions for the panel. Ask how they measure platform satisfaction, or what the on-call load looks like.
  8. Time-box it. For DevOps, three days is plenty. Past that, you are better off applying to more roles.

Coming from SRE or DevOps into platform work? Translate, do not downplay. Reframe incident stories around prevention tooling, learn the vocabulary (golden path, paved road, platform-as-a-product), and prepare one story about driving adoption. "I built X, three teams ignored it, I found out why, and adoption rose after I changed the default" beats "I built X."

How are C2C and contract interviews different?

The technical content is the same. The process around it is not. C2C interviews often fold technical screening and business terms into the same call: availability, start date, bench status, and sometimes rate. Prime vendors move faster than corporate hiring managers and may re-sell your answers to the end client, so hedge less. DevOps candidates may also get a distinct round about their LLC, insurance and availability.

Know your rate and start date before the first call. Read Contract-to-Hire vs C2C so you know what you are walking into. MLOps and cloud security roles in particular often run through corp-to-corp contracts, with vendor screens and statements of work sitting in front of the technical rounds.

How do you get into these interview loops in the first place?

Prep only matters if your application gets read. These roles get buried under applicants fast, and the first wave gets recruiter attention while everyone else waits in a queue. Titles also vary: the same platform job appears as "Platform Engineer," "Infrastructure Engineer" or "Developer Experience Engineer," so coverage matters as much as polish. The tradeoff between sending more and sending first is laid out in application volume vs application speed.

That is the problem GiraffyReach is built for. It detects fresh postings the moment they go live, applies before the crowd, and runs recruiter outreach, including on the C2C side. You do the prep above. It gets you into the rooms where the prep gets used.