Interview questions and model answers
"What is platform engineering, and how is it different from DevOps?"
DevOps is the culture and practices of shared ownership between building and running software. Platform engineering is one way of making that sustainable at scale: a dedicated team builds an internal developer platform — golden paths, self-service infrastructure, CI/CD, runtime, observability and guardrails — so product teams can own their services without each becoming infrastructure experts. It's about reducing cognitive load through self-service, not taking work back into a central ops team.
"How would you start building an internal developer platform?"
Start with users: interview teams and measure where time goes, such as onboarding, creating services, getting infrastructure or debugging deploys. Pick the biggest pain and build the thinnest solution, often a golden-path template for new services with CI, deployment and observability included, plus a catalogue of who owns what. Pilot with one or two teams, measure lead time and onboarding time, iterate, then expand. Treat it as a product with a roadmap, docs and support.
"What's a golden path?"
The supported, opinionated, easiest way to do a common task, like creating a new service with its repository, pipeline, deployment, dashboards and alerts already set up and compliant. Teams aren't forced onto it, but it's the path with the best support, and when the platform improves it, everyone on it benefits.
"What does Backstage give you, and what does it cost?"
A software catalogue with ownership and dependencies, software templates for golden paths, TechDocs for docs as code, search, and plugins that bring Kubernetes, CI, GitOps, on-call and cost data onto each service's page. The cost is that it's a framework: you build, host, upgrade and extend your own app, which needs a small dedicated team, and the catalogue only helps if it's kept accurate, so I'd make other tools depend on it.
"How do you give developers self-service databases safely?"
Encode the guardrails in the interface: a Terraform module or a Crossplane composition that creates the database with encryption, backups, private networking, tags and monitoring already set, exposing only meaningful choices like size and engine version. Developers request it through a pull request or a portal template; policy checks and plans run in CI. They get it in minutes, and it's compliant by construction.
"How do you measure whether a platform is working?"
DORA metrics before and after adoption, time to onboard and to create a new service, adoption of golden paths, number of tickets to the platform team, platform reliability SLOs, and regular developer-experience surveys. High adoption with poor satisfaction is a warning sign that people are tolerating it.
"Teams refuse to adopt your platform. What do you do?"
Find out why, with interviews and by watching them use it: maybe it's missing something they need, harder than their current way, or poorly documented. Fix the biggest gaps, add escape hatches, migrate one team with hands-on help and publicise their results, and make the golden path genuinely the easiest option. Mandates are a last resort, for security or compliance requirements, and even then should come with migration support.