Platform Engineer
What the work looks like, the stacks behind the title, what each level means and the training that helps, then how interviews run and how to prepare for each step.
What a platform engineer actually does
An engineer who builds the internal platform that developers use to build, deploy and run their services on their own.
A platform engineer builds an internal developer platform: the tools, templates and services that let development teams create, deploy and run their applications on their own.
Platform teams treat the platform as a product. They talk to developers, build golden paths and self-service tools, often with Backstage, Kubernetes, Argo CD and Crossplane, and they make reliability and security the default.
More and more teams also work with AI coding tools such as Claude Code, Cursor or GitHub Copilot, and expect engineers to use them with judgment.
- Building a new template or golden path
- Interviews with developers on their pain points
- Improving a Kubernetes or GitOps setup
- Adding a policy or a security default
- Code reviews, documentation and platform support
The same title, very different stacks
Most platform engineering searches are defined first by the part of the platform the team owns, then by the ground every platform engineer shares.
What each level means in practice
Titles vary from one company to the next. What changes from one level to the next is the scope you own and the decisions you take.
- Works on the platform with a senior engineer
- Learns the tools, the clusters and the users
- Writes tested code with review
- Builds parts of the platform on their own
- Supports developers and fixes platform issues
- Works directly with development teams
- Designs platform components for many teams
- Takes choices on tools, adoption and defaults
- Mentors other engineers and leads code reviews
- Sets the platform strategy across teams
- Leads choices on architecture and standards
- Writes the design documents others build on
The paths into the role, and what really counts
Companies look first at platforms you have built and that developers adopted. Education and certifications help most early in a career, or to change field.
- Engineering school or master's in computer scienceThe most common path in France, and often expected by large companies.
- University degree in computer scienceThe most common path in the US, at bachelor's or master's level.
- DevOps or SRE firstMany platform engineers start in DevOps or SRE roles before building a platform.
- Backend engineering firstBackend engineers who care about developer experience also move into the role.
Our view: for this role, a platform developers chose to use, with numbers on adoption, often says more than any certificate.
A conversation with a senior tech recruiter
Your first interview is with one of our senior tech recruiters, who knows the role, the stacks and the levels in this guide. The conversation covers your own work through real examples, and the technical exercises come later, with the company. Before the call, we send you the six themes we will cover so you can prepare your examples.
- What you owned yourselfThe platform components, templates or tools you were responsible for, and your own part in the team's work.
- Your environment and its constraintsNumber of teams, existing tools, security rules or budget: what shaped your technical choices.
- The decisions you madeWhich tools, which defaults and how much self-service, the options you compared and the reasons for your choice.
- The impact of your workWhat changed thanks to your work, with numbers when you have them: adoption, time to deploy, tickets saved or incidents.
- How you work with other teamsYour work with developers, security, SREs and leadership, and how you settle a disagreement.
- What you want nextThe kind of platform, scale and scope you are looking for in your next role.
- Platforms developers adopted
- Developer experience
- Reliability and security by default
The same ground for every candidate. For a given role, every candidate answers the same final questions, built with the hiring manager around what the role really needs.
Ready for the next steps. After our call, we tell you how the company runs its interviews, who you will meet at each step and what each step is meant to assess.
What the company will assess, step by step
Each company runs its own process, and we walk you through its steps before you start. Platform engineering processes often combine the steps below, and the depth expected at each step grows with your level.
- A hands-on exerciseInfrastructure code, a Kubernetes setup or a small tool to write, live or as a take‑home.
- A platform designAn internal developer platform to design for many teams, from templates to deployment and observability.
- A deep dive on your past workOne platform component you built, discussed in depth: the users, your choices and the adoption.
- Meeting the manager and the teamHow you work, how you take decisions with others and what the team expects in your first months.
- ConfirmedYou solve the exercise cleanly, explain each choice in simple words and think about the developers who use it.
- SeniorYou lead the design, weigh flexibility and standards, and point out risks and limits before you are asked.
- Staff and PrincipalYou run most of the interview as a peer, think about the platform as a product and connect it to the needs of several teams.
How to prepare as a platform engineer
Practical advice for each step of a platform engineering process, from the way you introduce yourself to the questions you ask at the end of each interview.
Start with the platform components you worked on, their scale and your part in them. Mention your stack in one sentence, then close with what you want next.
For each one, prepare the context, the constraints, your decision, the options you set aside, the result and what you would change today. Say "we" for the team and "I" for your own part.
Interviewers often ask how you know developers need a feature. Prepare how you collected feedback and measured adoption.
In a platform design, start with what developers need to do on their own, then choose the tools and the defaults.
Prepare one example of a policy or a default you added, and how teams accepted it.
Rules on AI coding assistants differ from one company to the next, and sometimes from one step to the next. Ask before each step, and when they are allowed, explain what you ask the tool and how you check its output.
- Walk us through a platform component you built, and who used it.
- How do you measure the success of an internal platform?
- How would you design golden paths for new services?
- A team refuses to use the platform. What do you do?
- How many teams use the platform today?
- How does the team collect feedback from developers?
- Which tools are part of the platform?
- How do platform, SRE and security teams share the work?
- How is adoption of the platform measured?
- How does the team use AI coding tools day to day?
Where platform engineers come from, and where they go
The roles people most often hold before this one, and the ones they most often move to.