136 questions across 20 topics - answered to the depth an interviewer actually expects.
Role tracks: Platform Engineer (junior β staff) Β· DevEx Β· Platform Architect Β· Kubernetes Platform Β· Platform Security Β· Platform SRE Β· AWS Β· Azure Β· GCP Β· FinOps Β· Platform Lead
Every answer gives you a short answer you can say out loud, the detail and trade-offs behind it, a runnable example, and the follow-ups to expect.
Pick your role Β· Browse topics Β· All questions Β· Knowledge graph Β· How answers are structured Β· Contributing
π Explore the knowledge graph β - all 136 questions as a live map of the concepts they share.
β Star the project if it helps you land the role.
Platform engineering interviews are not infrastructure interviews with a new title. They probe a specific set of judgements: whether you can design an interface other engineers will voluntarily use, where you put a guardrail versus a golden path, how you version a contract forty teams depend on, and how you know whether any of it worked.
This guide is organised around those judgements. It assumes you already know what a Pod is, and spends its pages on the decisions above that line - tenancy boundaries, control-plane design, escapable abstractions, rollout policy, cost attribution, and the operating model of a team whose customers are other engineers.
New to the field, or moving in from DevOps or SRE? Start with Platform Engineering Fundamentals, then Developer Experience. The vocabulary in those two topics is assumed by everything else.
Eleven tracks, each a reading order rather than a pile of links. Start at the left and work right.
Interview in a fortnight? Start with Platform Engineering Interviews - it covers the loop structure, the platform design round, how to present work you have done, and what to ask back, cross-linked to the rest of the guide.
Grouped by theme, with question counts and difficulty mix. Click a topic to open its index, which opens with what interviewers probe there.
136 questions across 20 topics - π’ 11 Beginner Β· π‘ 56 Intermediate Β· π΄ 69 Advanced
| Topic | Questions | π’ | π‘ | π΄ | What it covers |
|---|---|---|---|---|---|
| Platform Engineering Fundamentals | 8 | 3 | 3 | 2 | what a platform actually is, why self-service is the defining property, and where platform⦠|
| Developer Experience | 7 | 1 | 5 | 1 | cognitive load, service catalogues, portals, scorecards, onboarding time, and the metrics that⦠|
| Topic | Questions | π’ | π‘ | π΄ | What it covers |
|---|---|---|---|---|---|
| Platform Architecture | 8 | 1 | 3 | 4 | control plane versus data plane, the developer-facing API, escapable abstractions, interface⦠|
| Multi-Tenancy and Isolation | 6 | 0 | 2 | 4 | tenancy models, namespace versus cluster boundaries, noisy neighbours, quotas, network⦠|
| Topic | Questions | π’ | π‘ | π΄ | What it covers |
|---|---|---|---|---|---|
| Kubernetes Platform | 8 | 1 | 2 | 5 | cluster topology, node pools and scheduling, fleet upgrades, admission control as a platform⦠|
| Control Planes and Abstractions | 6 | 0 | 1 | 5 | Crossplane, custom resources as platform contracts, workload specifications, Terraform at scale,β¦ |
| Topic | Questions | π’ | π‘ | π΄ | What it covers |
|---|---|---|---|---|---|
| GitOps and Continuous Delivery | 8 | 1 | 4 | 3 | Argo CD and Flux, repository structure at scale, environment promotion, secrets, drift⦠|
| Progressive Delivery and Feature Flags | 8 | 0 | 2 | 6 | flags as a platform capability, flag debt and its SLAs, rollout curves with abort criteria,β¦ |
| Environments and Ephemeral Infrastructure | 6 | 0 | 4 | 2 | preview environments per pull request, data seeding without leaking production, environment⦠|
| Topic | Questions | π’ | π‘ | π΄ | What it covers |
|---|---|---|---|---|---|
| Platform Security | 8 | 0 | 2 | 6 | workload identity without long-lived keys, secretless pipelines, secrets management,β¦ |
| Policy as Code and Governance | 6 | 0 | 4 | 2 | OPA and Kyverno, rolling out policy without breaking teams, compliance frameworks mapped to⦠|
| Topic | Questions | π’ | π‘ | π΄ | What it covers |
|---|---|---|---|---|---|
| AWS Platform Engineering | 7 | 0 | 3 | 4 | multi-account organisation design, account vending, EKS pod identity, runtime selection,β¦ |
| Azure Platform Engineering | 6 | 0 | 3 | 3 | management groups and landing zones, Azure Policy guardrails, AKS workload identity, runtime⦠|
| GCP Platform Engineering | 6 | 0 | 3 | 3 | the folder and project hierarchy, organisation policies, Workload Identity Federation, GKE⦠|
| Multi-Cloud and Hybrid Platforms | 5 | 0 | 2 | 3 | genuine drivers versus slogans, the cost of portable abstractions, cross-provider primitive⦠|
| Topic | Questions | π’ | π‘ | π΄ | What it covers |
|---|---|---|---|---|---|
| Platform Reliability | 7 | 0 | 2 | 5 | SLOs for a platform rather than an app, error budget policy, platform on-call, incidents where⦠|
| Platform Observability | 6 | 0 | 3 | 3 | OpenTelemetry collectors as shared infrastructure, cardinality and cost control, zero-effort⦠|
| Topic | Questions | π’ | π‘ | π΄ | What it covers |
|---|---|---|---|---|---|
| Platform FinOps | 6 | 1 | 2 | 3 | cost attribution for shared infrastructure, showback versus chargeback, unit economics,β¦ |
| Platform Team and Operating Model | 7 | 1 | 3 | 3 | Team Topologies, staffing, adoption metrics, migration without a mandate, deprecation, the RFC⦠|
| Topic | Questions | π’ | π‘ | π΄ | What it covers |
|---|---|---|---|---|---|
| Platform Engineering Interviews | 7 | 2 | 3 | 2 | the loop structure, the platform design round, presenting your own platform work,β¦ |
Every question in the repository, collapsed by topic - open only the ones you are studying.
15 questions
Platform Engineering Fundamentals Β· 8 questions Β· π’ 3 π‘ 3 π΄ 2
Open the Platform Engineering Fundamentals index β
| No. | Question | Difficulty |
|---|---|---|
| 1 | What is platform engineering? | π’ Beginner |
| 2 | What is an internal developer platform? | π’ Beginner |
| 3 | How is platform engineering different from DevOps and SRE? | π’ Beginner |
| 4 | What is a golden path and how does it differ from a mandate? | π‘ Intermediate |
| 5 | What is the thinnest viable platform? | π‘ Intermediate |
| 6 | How do you decide whether your organisation needs a platform team? | π‘ Intermediate |
| 7 | What does it mean to run a platform as a product? | π΄ Advanced |
| 8 | What are the most common ways platform initiatives fail? | π΄ Advanced |
Developer Experience Β· 7 questions Β· π’ 1 π‘ 5 π΄ 1
Open the Developer Experience index β
| No. | Question | Difficulty |
|---|---|---|
| 9 | What is developer experience and how do you measure it? | π‘ Intermediate |
| 10 | What is cognitive load and why does it drive platform design? | π‘ Intermediate |
| 11 | What is a service catalogue and why does a platform need one? | π‘ Intermediate |
| 12 | What is Backstage and when is it the wrong choice? | π‘ Intermediate |
| 13 | How do you reduce the time it takes a new engineer to ship to production? | π‘ Intermediate |
| 14 | How do you design service scorecards that teams do not resent? | π΄ Advanced |
| 15 | How do you run documentation as a platform capability? | π’ Beginner |
14 questions
Platform Architecture Β· 8 questions Β· π’ 1 π‘ 3 π΄ 4
Open the Platform Architecture index β
| No. | Question | Difficulty |
|---|---|---|
| 16 | What is the difference between a control plane and a data plane in a platform? | π‘ Intermediate |
| 17 | How do you design the developer-facing API of a platform? | π΄ Advanced |
| 18 | How do you keep a platform abstraction escapable? | π΄ Advanced |
| 19 | How do you version a platform interface and migrate consumers? | π΄ Advanced |
| 20 | When should a platform capability be a service, a library, or a template? | π‘ Intermediate |
| 21 | How do you write an architecture decision record for a platform choice? | π’ Beginner |
| 22 | How do you choose a datastore for a platform service? | π‘ Intermediate |
| 23 | How do you decide whether to build or buy a platform capability? | π΄ Advanced |
Multi-Tenancy and Isolation Β· 6 questions Β· π’ 0 π‘ 2 π΄ 4
Open the Multi-Tenancy and Isolation index β
| No. | Question | Difficulty |
|---|---|---|
| 24 | What tenancy models can a platform offer? | π‘ Intermediate |
| 25 | When do you give a tenant its own cluster instead of a namespace? | π΄ Advanced |
| 26 | How do you stop one tenant degrading another? | π΄ Advanced |
| 27 | How do you isolate tenants at the network layer? | π‘ Intermediate |
| 28 | How do you isolate tenant identity and data? | π΄ Advanced |
| 29 | How do you design tenant onboarding and offboarding? | π΄ Advanced |
14 questions
Kubernetes Platform Β· 8 questions Β· π’ 1 π‘ 2 π΄ 5
Open the Kubernetes Platform index β
| No. | Question | Difficulty |
|---|---|---|
| 30 | Why does Kubernetes end up as the substrate for most platforms? | π’ Beginner |
| 31 | How do you design cluster topology for a platform? | π΄ Advanced |
| 32 | How do you design node pools and scheduling for mixed workloads? | π‘ Intermediate |
| 33 | How do you upgrade a fleet of clusters without breaking tenants? | π΄ Advanced |
| 34 | What is admission control and how do you use it as a platform lever? | π‘ Intermediate |
| 35 | When should you write a Kubernetes operator? | π΄ Advanced |
| 36 | How do you run a service mesh as a platform capability? | π΄ Advanced |
| 37 | How do you keep platform components consistent across many clusters? | π΄ Advanced |
Control Planes and Abstractions Β· 6 questions Β· π’ 0 π‘ 1 π΄ 5
Open the Control Planes and Abstractions index β
| No. | Question | Difficulty |
|---|---|---|
| 38 | What is Crossplane and how does it differ from Terraform? | π΄ Advanced |
| 39 | How do you model a platform API with Kubernetes custom resources? | π΄ Advanced |
| 40 | What problem does a workload specification like Score solve? | π‘ Intermediate |
| 41 | How do you manage Terraform at platform scale? | π΄ Advanced |
| 42 | How do you handle resource deletion safely in a control plane? | π΄ Advanced |
| 43 | How do you provide self-service infrastructure without handing out cloud credentials? | π΄ Advanced |
22 questions
GitOps and Continuous Delivery Β· 8 questions Β· π’ 1 π‘ 4 π΄ 3
Open the GitOps and Continuous Delivery index β
| No. | Question | Difficulty |
|---|---|---|
| 44 | What is GitOps and what does it actually guarantee? | π’ Beginner |
| 45 | How do Argo CD and Flux differ, and how do you choose? | π‘ Intermediate |
| 46 | How do you structure repositories for GitOps at scale? | π΄ Advanced |
| 47 | How do you promote a change from staging to production in GitOps? | π΄ Advanced |
| 48 | How do you handle secrets in a GitOps workflow? | π‘ Intermediate |
| 49 | What is configuration drift and how does a platform detect it? | π‘ Intermediate |
| 50 | How do you keep templated manifests reviewable? | π‘ Intermediate |
| 51 | How do you give teams self-service pipelines without maintaining 200 of them? | π΄ Advanced |
Progressive Delivery and Feature Flags Β· 8 questions Β· π’ 0 π‘ 2 π΄ 6
Open the Progressive Delivery and Feature Flags index β
| No. | Question | Difficulty |
|---|---|---|
| 52 | How do you run feature flags as a platform capability? | π΄ Advanced |
| 53 | How do you manage feature flag debt? | π΄ Advanced |
| 54 | How do you design a progressive rollout and its abort criteria? | π΄ Advanced |
| 55 | How do you design a kill switch you can trust? | π΄ Advanced |
| 56 | When do you use a feature flag instead of a canary deployment? | π‘ Intermediate |
| 57 | How do you keep percentage rollouts consistent across services? | π΄ Advanced |
| 58 | What can a feature flag not roll back? | π΄ Advanced |
| 59 | How do you test code that sits behind feature flags? | π‘ Intermediate |
Environments and Ephemeral Infrastructure Β· 6 questions Β· π’ 0 π‘ 4 π΄ 2
Open the Environments and Ephemeral Infrastructure index β
| No. | Question | Difficulty |
|---|---|---|
| 60 | What is an ephemeral environment and when is it worth it? | π‘ Intermediate |
| 61 | How do you build preview environments for every pull request? | π΄ Advanced |
| 62 | How do you seed realistic test data without copying production? | π΄ Advanced |
| 63 | What does environment parity actually require? | π‘ Intermediate |
| 64 | How do you stop ephemeral environments becoming a cost problem? | π‘ Intermediate |
| 65 | How do you give developers a fast inner development loop? | π‘ Intermediate |
14 questions
Platform Security Β· 8 questions Β· π’ 0 π‘ 2 π΄ 6
Open the Platform Security index β
| No. | Question | Difficulty |
|---|---|---|
| 66 | How does a platform provide workload identity without long-lived credentials? | π΄ Advanced |
| 67 | How do you run a secretless CI/CD pipeline? | π΄ Advanced |
| 68 | How do you manage secrets as a platform capability? | π‘ Intermediate |
| 69 | How do you secure the software supply chain for everything the platform builds? | π΄ Advanced |
| 70 | How do you keep base images patched across every team? | π‘ Intermediate |
| 71 | How do you respond to a critical CVE that affects every service on the platform? | π΄ Advanced |
| 72 | How do you design break-glass access to production? | π΄ Advanced |
| 73 | How do you threat model a platform? | π΄ Advanced |
Policy as Code and Governance Β· 6 questions Β· π’ 0 π‘ 4 π΄ 2
Open the Policy as Code and Governance index β
| No. | Question | Difficulty |
|---|---|---|
| 74 | What is policy as code and where does it belong in a platform? | π‘ Intermediate |
| 75 | How do Gatekeeper and Kyverno differ, and how do you choose? | π‘ Intermediate |
| 76 | How do you roll out a new policy without breaking every team? | π΄ Advanced |
| 77 | How do you turn a compliance framework into automated platform controls? | π΄ Advanced |
| 78 | How do you handle policy exceptions without eroding the guardrails? | π‘ Intermediate |
| 79 | What audit trail does a platform owe its auditors? | π‘ Intermediate |
24 questions
AWS Platform Engineering Β· 7 questions Β· π’ 0 π‘ 3 π΄ 4
Open the AWS Platform Engineering index β
| No. | Question | Difficulty |
|---|---|---|
| 80 | How do you structure a multi-account AWS platform? | π΄ Advanced |
| 81 | What is account vending and how do you automate it? | π΄ Advanced |
| 82 | How do you give pods on EKS access to AWS resources safely? | π‘ Intermediate |
| 83 | How do you choose between ECS, EKS, Lambda, and App Runner for a platform runtime? | π‘ Intermediate |
| 84 | How do you manage EKS node capacity with Karpenter? | π΄ Advanced |
| 85 | How do you build a paved road for AWS infrastructure self-service? | π΄ Advanced |
| 86 | How do you allocate AWS cost back to teams? | π‘ Intermediate |
Azure Platform Engineering Β· 6 questions Β· π’ 0 π‘ 3 π΄ 3
Open the Azure Platform Engineering index β
| No. | Question | Difficulty |
|---|---|---|
| 87 | How do you structure an Azure platform with management groups and landing zones? | π΄ Advanced |
| 88 | How do you use Azure Policy as a platform guardrail? | π‘ Intermediate |
| 89 | How do workload identities work on AKS? | π‘ Intermediate |
| 90 | How do you choose between AKS, Container Apps, App Service, and Functions? | π‘ Intermediate |
| 91 | How do you use Bicep for platform modules and subscription vending? | π΄ Advanced |
| 92 | How do you design private networking for Azure PaaS services? | π΄ Advanced |
GCP Platform Engineering Β· 6 questions Β· π’ 0 π‘ 3 π΄ 3
Open the GCP Platform Engineering index β
| No. | Question | Difficulty |
|---|---|---|
| 93 | How do you structure a GCP platform with folders, projects, and organisation policies? | π΄ Advanced |
| 94 | How does Workload Identity Federation remove service account keys? | π‘ Intermediate |
| 95 | How do you choose between GKE, GKE Autopilot, and Cloud Run? | π‘ Intermediate |
| 96 | How do you design Shared VPC for a multi-team GCP platform? | π΄ Advanced |
| 97 | How do you use Config Connector and Config Sync as a GCP control plane? | π΄ Advanced |
| 98 | How do you automate project vending on GCP? | π‘ Intermediate |
Multi-Cloud and Hybrid Platforms Β· 5 questions Β· π’ 0 π‘ 2 π΄ 3
Open the Multi-Cloud and Hybrid Platforms index β
| No. | Question | Difficulty |
|---|---|---|
| 99 | When is multi-cloud a real requirement rather than a slogan? | π‘ Intermediate |
| 100 | What does a genuinely portable platform abstraction cost you? | π΄ Advanced |
| 101 | How do you map equivalent primitives across AWS, Azure, and GCP? | π‘ Intermediate |
| 102 | How do you design a hybrid platform spanning on-premises and cloud? | π΄ Advanced |
| 103 | How does data gravity constrain platform design? | π΄ Advanced |
13 questions
Platform Reliability Β· 7 questions Β· π’ 0 π‘ 2 π΄ 5
Open the Platform Reliability index β
| No. | Question | Difficulty |
|---|---|---|
| 104 | How do you define SLOs for a platform rather than an application? | π΄ Advanced |
| 105 | What does an error budget policy look like for a platform team? | π΄ Advanced |
| 106 | How do you run on-call for a platform team? | π‘ Intermediate |
| 107 | How do you run an incident when the platform itself is the incident? | π΄ Advanced |
| 108 | How do you make a platform degrade gracefully instead of failing closed? | π΄ Advanced |
| 109 | How do you plan disaster recovery for the platform itself? | π΄ Advanced |
| 110 | How do you use chaos engineering to test platform guarantees? | π‘ Intermediate |
Platform Observability Β· 6 questions Β· π’ 0 π‘ 3 π΄ 3
Open the Platform Observability index β
| No. | Question | Difficulty |
|---|---|---|
| 111 | How do you provide observability as a platform capability? | π‘ Intermediate |
| 112 | How do you run an OpenTelemetry collector as a platform service? | π΄ Advanced |
| 113 | How do you control metric cardinality and observability cost? | π΄ Advanced |
| 114 | What telemetry should every service get without writing code? | π‘ Intermediate |
| 115 | How do you make traces useful across team boundaries? | π΄ Advanced |
| 116 | How do you give teams visibility into platform state that affects them? | π‘ Intermediate |
13 questions
Platform FinOps Β· 6 questions Β· π’ 1 π‘ 2 π΄ 3
Open the Platform FinOps index β
| No. | Question | Difficulty |
|---|---|---|
| 117 | What is FinOps and what part of it does a platform team own? | π’ Beginner |
| 118 | How do you attribute shared platform cost to teams? | π΄ Advanced |
| 119 | What is the difference between showback and chargeback, and which works? | π‘ Intermediate |
| 120 | How do you build unit economics for a platform? | π΄ Advanced |
| 121 | How do you use commitments and spot capacity on behalf of every team? | π΄ Advanced |
| 122 | How do you find and remove idle platform cost? | π‘ Intermediate |
Platform Team and Operating Model Β· 7 questions Β· π’ 1 π‘ 3 π΄ 3
Open the Platform Team and Operating Model index β
| No. | Question | Difficulty |
|---|---|---|
| 123 | What does Team Topologies say about platform teams? | π’ Beginner |
| 124 | How do you size and staff a platform team? | π‘ Intermediate |
| 125 | How do you measure platform adoption and success? | π‘ Intermediate |
| 126 | How do you migrate teams onto the platform without a mandate? | π΄ Advanced |
| 127 | How do you deprecate a platform capability? | π΄ Advanced |
| 128 | How do you run an RFC process for platform decisions? | π‘ Intermediate |
| 129 | How do you build a platform roadmap and say no? | π΄ Advanced |
7 questions
Platform Engineering Interviews Β· 7 questions Β· π’ 2 π‘ 3 π΄ 2
Open the Platform Engineering Interviews index β
| No. | Question | Difficulty |
|---|---|---|
| 130 | What does a platform engineering interview loop look like? | π’ Beginner |
| 131 | How do you answer a platform design interview question? | π΄ Advanced |
| 132 | How do you present platform work you have done? | π‘ Intermediate |
| 133 | How do you answer 'how would you build a platform from scratch'? | π΄ Advanced |
| 134 | How do you handle a troubleshooting round? | π‘ Intermediate |
| 135 | What behavioural questions do platform interviews ask, and why? | π‘ Intermediate |
| 136 | What should you ask your interviewer about their platform? | π’ Beginner |
Every answer follows the same four beats, so you can read one section deep or all four:
| Section | What it gives you |
|---|---|
| Short answer | Two or three sentences you could say out loud. Start here. |
| Detail | The substance - mechanisms, trade-offs, and the vocabulary that signals experience. |
| Example | Real manifests, policies, commands, or diagrams you can run and adapt. |
| Interview tips | The follow-up questions, the common traps, and the points that separate a strong answer from a memorised one. |
Difficulty is marked π’ Beginner Β· π‘ Intermediate Β· π΄ Advanced. The distribution skews senior, because the field does: most platform roles are filled at senior and above, and the interesting questions are about judgement rather than recall.
Three ways to work through it:
- Preparing for a specific role - take the track from Pick your role, and read each topic README's "What interviewers probe here" before its questions.
- Broad revision - read the short answers across a topic, then go deep only where you hesitate.
- Obsidian / note vault - every file carries YAML frontmatter (
title,id,category,difficulty,tags), so the whole repository can be dropped into a vault and browsed by tag.
Platform engineering questions do not sit in neat boxes: tenancy decides your isolation boundary, which decides your policy model, which decides what your golden path can promise. The knowledge graph makes those dependencies visible - every question is a node, and two questions are linked when they genuinely argue about the same concept.
The links are derived, not hand-maintained. Each answer is scanned for the ~70 concepts this field turns on (control plane, golden path, policy as code, blast radius, error budget, chargeback, β¦), and a pair is linked when the concepts they share are rare across the vault. Rarity weighting is what stops "kubernetes" linking everything to everything; length normalisation stops the longest answers becoming hubs.
python3 scripts/build_knowledge_graph.py --output docs/index.html # the deployed page
python3 scripts/build_knowledge_graph.py --stats # edge counts, hubs, orphans
python3 scripts/build_knowledge_graph.py --json docs/graph.json # the raw graph
python3 scripts/inject_wikilinks.py # write the same edges into the question filesThree renderings ship with the builder and are selectable with --prototype:
| Prototype | What it is for |
|---|---|
constellation |
(deployed) Force-directed map of the whole vault, clustered by theme. Click a question to light up its neighbourhood. |
atlas |
The capability map: groups and topics laid out in reading order, with concept links drawn on demand. |
pathway |
Difficulty lanes that generate a study route - the questions to read before the hard one makes sense. |
The page is a single self-contained HTML file with no dependencies, deployed to GitHub Pages by knowledge-graph.yml on every push to main.
inject_wikilinks.py writes the same edges into each question's ## Related Questions block, between <!-- RELATED:START --> and <!-- RELATED:END --> markers, as both [[wikilinks]] (for Obsidian-style vaults) and relative links (for GitHub). It is idempotent, and --check fails CI when a block has drifted from the graph.
.
βββ platform-engineering-fundamentals/ # topic-slug/
β βββ README.md # generated topic index
β βββ what-is-platform-engineering.md # question-slug.md
βββ ...
βββ scripts/
β βββ lib_content.py # shared frontmatter/vault parsing
β βββ generate_indexes.py # regenerates all indexes from question files
β βββ validate_content.py # CI validation of the whole vault
β βββ build_knowledge_graph.py # derives the concept graph, renders the HTML site
β βββ inject_wikilinks.py # writes graph edges into `## Related Questions` blocks
β βββ topic_meta.json # topic registry: order, group, description, study notes
βββ docs/
β βββ index.html # generated knowledge graph, deployed to GitHub Pages
βββ .github/workflows/
βββ validate-and-format.yml # runs validation + Prettier on every PR
βββ knowledge-graph.yml # rebuilds and deploys the graph on push to main
Directories and filenames carry no numeric prefixes - they are pure slugs. Ordering comes from two places instead:
- Topic order - the
orderfield inscripts/topic_meta.json, which is also the registry of which directories count as topics. - Question order - the
idfield in each question's frontmatter, unique across the repository.
Renaming or reordering is therefore a metadata edit, not a mass file rename.
Every question file starts with frontmatter:
---
title: "What is a golden path and how does it differ from a mandate?"
id: 4
category: "Platform Engineering Fundamentals"
difficulty: "Intermediate"
tags:
- platform-engineering
- platform-engineering-fundamentals
- interview-questions
---The indexes are generated, not hand-written. The question files are the single source of truth; topic READMEs and the tables above are rendered from their frontmatter. After adding or editing a question:
python3 scripts/generate_indexes.py # rewrite all indexes
python3 scripts/inject_wikilinks.py # refresh the related-questions blocks
python3 scripts/build_knowledge_graph.py --output docs/index.html # rebuild the graph page
python3 scripts/validate_content.py # verify frontmatter, naming, links, index freshnessBoth are stdlib-only Python 3.11+ - no dependencies to install. CI runs the same commands and fails the pull request on drift.
New questions, better answers, and corrections are all welcome. CONTRIBUTING.md covers the file format, naming rules, and the local checks to run before opening a pull request.
Not sure where to start? Open an issue - there are templates for a new question, a correction to an existing answer, a new topic, and broken links or tooling.
Two documents set the ground rules: the Code of Conduct - including the rules on interviewer privacy, NDAs, and plagiarism - and the Security Policy, which covers how to report a committed credential, a workflow vulnerability, or a dangerously over-permissive example policy privately.
Three sibling repositories, same structure, same tooling - pick the one that matches the role you are interviewing for:
- Ultimate DevOps Guide - DevOps, SRE, DevSecOps, and cloud engineering. Start there for container, CI/CD, Linux, and networking fundamentals; this guide assumes them.
- Ultimate AI Engineering Guide - LLM fundamentals, prompt engineering, RAG, agents and MCP, fine-tuning, evaluation, and LLMOps. The counterpart for AI platform and AI engineering loops, where this guide covers the infrastructure the models run on.
- Ultimate Platform Engineering Guide (you are here) - the platform layer between the two: golden paths, control planes, tenancy, and the operating model of a team whose customers are other engineers.
The vocabulary this guide uses is not invented here. It leans on the work of the platform engineering community:
- Team Topologies by Matthew Skelton and Manuel Pais - platform teams as enabling teams, cognitive load as the design constraint, and the thinnest viable platform.
- CNCF Platforms Working Group - the platform maturity model and the capability-plane vocabulary.
- Google SRE - SLOs, error budgets, and the toil framing that platform reliability builds on.
- OpenFeature, OpenTelemetry, Crossplane, Backstage, and Argo CD - the open standards and projects most of these answers reference.
- DORA - the delivery metrics used throughout to argue about outcomes rather than output.
Released under the MIT License.