Platform & Developer Experience
Infrastructure & Cloud Platform Engineer
The substrate everything else runs on. The closest thing to a classical engineering role in this family.
What the job actually is
You build and run the compute, network and storage layer that product teams deploy onto — clusters, provisioning, networking, identity, multi-tenancy and the cost of all of it. Unlike SRE this is predominantly build work rather than operate work, and unlike archetype 4 your customer is the system rather than the developer.
Titles this hides behind
Prepare like this
- Know Kubernetes past the manifest. Scheduler behaviour, admission control, what actually happens on a node under memory pressure, and why your pod is pending. Interviewers probe the layer below the one candidates studied.
- Be fluent in one cloud and conversant in a second. All three sit at roughly 50% of postings, so the credible position is depth plus translation, not claimed parity across three.
- Bring a migration story. Something moved, with the rollback plan you prepared and whether you used it.
- Learn the cost dimension — only 5% of postings name FinOps, but it comes up in nearly every senior conversation because it is how platform teams justify themselves.
- Go matters here at 35%, more than anywhere else in either family.
Be ready for
- "Design multi-tenant isolation for untrusted workloads." Namespaces are the wrong first answer. They want to hear about the kernel boundary.
- "Your Terraform apply would delete a production database. How did your process let that happen?" Plan review, state management, and blast-radius control.
- "Cut cloud spend 30%. Where do you look first?"
Compensation
A day that is actually representative
| Time | What you are actually doing |
|---|---|
| 09:00 | A cluster upgrade plan with a rollback that has been tested. |
| 11:00 | Terraform review where the plan contains a destroy nobody noticed. |
| 13:30 | Multi-tenancy design for an untrusted workload. |
| 15:00 | Cost — a right-sizing pass driven by data rather than by guessing. |
| 16:30 | On-call handover. |
Real cases worth being able to discuss
SSRF to instance metadata to an over-permissioned role.
Use it to say: “It is why I treat IAM as the primary blast-radius control in cloud infrastructure.”
Single changes propagating globally within minutes.
Use it to say: “My takeaway is staged rollout with a halt condition — global simultaneous deployment is a design choice, and usually the wrong one.”
A three-week plan
Week 1 — build
Days 1–5: Stand up a cluster from code, then destroy and rebuild it identically.
Week 2 — isolation
Days 1–3: Multi-tenant isolation with a test that attempts cross-tenant access and asserts refusal.
Days 4–5: Delete the guard and confirm the test goes red.
Week 3 — rehearse
Days 1–3: The isolation and Terraform-destroy answers, out loud.
Days 4–5: A migration story with the rollback you prepared.
The book for this field
Infrastructure & Reliability
Reliability and error budgets, capacity arithmetic, networks, storage and the restore you have not tested, the physical layer, a debugging method that transfers, running production, and an honest look at Kubernetes. Plus a Middleware section — web and application servers, messaging (IBM MQ, Kafka) and managed file transfer, from basics to licensing and cost.
Also read for this role
Microsoft 365 & Copilot in the Enterprise
How a Microsoft 365 estate is actually built, licensed and governed — tenant, identity, workloads, devices, Purview and Defender, every licence tier with current prices, and then Copilot and Copilot Studio from the request path to the evidence on whether they deliver.
All 12 chapters in Microsoft 365 & Copilot in the Enterprise →
Cross-cutting
Skills every archetype tests
These are shared across every field on this site — the same question asked in different vocabulary — so preparation here compounds rather than being spent once. The book above is specific to your field.
Practice the 35 Platform questions → · Back to Platform & Developer Experience →