Search the practice set
275 questions, 991 terms and 600 topics in 30 areas.
60 results for “Platform Engineering”
Platform User Research
Treating engineers as users whose actual behaviour is observed rather than assumed, which is what separates a platform from a set of shared tools.
Monzo's Microservice Estate
Monzo runs a bank on well over a thousand microservices, and the interesting engineering is in the platform and network isolation that makes that number survivable.
Booking.com's Experimentation Platform
Booking.com runs over a thousand concurrent experiments and treats the ability to test any change safely as a platform capability rather than a product feature.
Chaos Engineering
Deliberately injecting failure into a system to discover, before an incident does, which of your resilience assumptions are false.
Platform Contract
The platform's promise to its consumers about interface stability, behaviour and support, treated with the same seriousness as an external API.
Platform Lifecycle Constraint
The operating system's rules about when your process runs, which are not negotiable and invalidate most assumptions carried over from server code.
Platform Team Product Model
Running an internal platform team with product management disciplines — users, roadmap, support, metrics — rather than as an infrastructure function.
Platform as a Product
Running an internal platform with the disciplines of a product — voluntary adoption, user research, documentation and a roadmap — rather than as a mandated standard.
Leadership asks for "five nines" across the platform. Engineering says it is impossible. Design the response.
Reframe the request "Five nines" is almost never what the business actually wants. 26 seconds of downtime per month is a number chosen for its rhetorical weight
You are forming a platform team of four to serve twelve product teams. What do you build first?
Not a platform. One golden path. Four people cannot build an internal developer platform for twelve teams. They can make one journey excellent, and expand from
A business sponsor asks for a real-time data platform because "the competition has one". Reporting is currently a nightly batch that lands at 06:00 and nobody has complained. How do you handle this?
Do not answer the technology question "Real time platform" is a solution, and it has arrived without a problem attached. Answering it directly leads either to a
A design review presents a new event-driven platform. What cost questions do you ask before approving it?
What the interviewer is testing Whether cost is part of your architecture review or an afterthought handled by finance later, and whether you know the specific
A new platform must serve a public partner API, three internal front-ends with different data needs, and high-volume service-to-service traffic. Choose the API styles and defend the choice.
Resist "pick one" These are three different problems with three different consumers. Standardising on one style optimises for architectural tidiness at the expe
A platform of 40 services has logs only, and incidents take hours to diagnose. Design the observability strategy and its rollout order.
Why logs alone fail at this size Logs answer "what happened in this service". They cannot answer "where did this request spend its time across twelve services",
A platform team proposes adopting a service mesh for 40 services. Make the case for and against, then decide.
What it genuinely provides mTLS everywhere, with automated certificate rotation. This is usually the deciding factor. Doing mTLS by hand means short lived certi
A regulated client requires that no traffic between their data centre and your SaaS platform traverses the public internet. Design the connectivity and justify the cost.
Two distinct requirements hiding in one sentence Traffic must not traverse the public internet — a routing requirement. The client must be able to demonstrate i
A single deploy took down your monitoring platform. What happened, and how do you prevent a recurrence?
What almost certainly happened A high cardinality label was added to a metric. Each unique combination of label values is a separate time series, and cost scale
A vendor claims their streaming platform provides exactly-once processing. How do you evaluate the claim?
Ask where the guarantee ends Nearly always at the platform's boundary. Within it, state and offsets commit together, so internal state reflects each input once.
An AI feature launched two months ago now costs more per month than the rest of the platform. What do you investigate?
Get cost per request, decomposed Token cost splits into input and output, and they price differently. Break the bill down by feature, by user, and by input vers
An e-commerce platform stores card numbers to support repeat purchases. How do you reduce PCI scope?
Stop the card number reaching your systems at all The strongest reduction is not storing cards more safely; it is never receiving them. A hosted field or an ifr
Application teams say the platform is unreliable. The platform team's dashboard shows 99.95% on every component. How do you resolve this?
Both are right, and that is the finding The platform measured its components. Consumers experience journeys. The gap between those two views is where trust erod
Delivery leadership says releases are too slow and wants the engineering team to "move faster". Lead time from commit to production is 21 days. How do you investigate, and what do you expect to find?
Do not accept the framing "Move faster" assumes the constraint is how fast code is written. That is almost never where the twenty one days went, and starting an
Design a webhook delivery system for a platform with 10,000 customers. What are the hard parts?
Delivery, and its failure modes Persist the event first, deliver asynchronously. Delivery in the request path couples your latency and availability to every cus
Engineering says the codebase is full of technical debt. The business hears "we want to stop delivering and tidy up". How do you reframe it?
The word is the problem "Technical debt" means nothing to a business audience, and where it means something it sounds like tidying. It also covers three genuine
Finance wants a three-year commitment on cloud spend for the discount. Engineering is nervous. How do you advise?
Commit to the floor, not to the forecast The safe commitment is the portion of usage that will exist regardless of what happens: the steady baseline, evidenced
Leadership asks whether to build an internal developer platform or buy one. Twelve teams, forty services, growing. How do you frame the decision?
Reject the framing as a binary Nobody builds or buys a whole platform. A platform is an assembly: source control, CI, artifact registry, infrastructure provisio
Partner integrations take four months from contract signature to production traffic. Engineering says the work is three days. Where does the time go and how do you cut it?
Map the elapsed time honestly The engineering estimate is correct and irrelevant. The four months are: Legal and contractual review. Security questionnaires and
Platform Engineering
General material on internal platforms as products with users, adoption and lifecycles.
Internal Developer Platform
The assembled surface teams actually touch, and what belongs behind it.
Platform API Deprecation
Removing something dozens of internal teams depend on, on a timeline that holds.
Platform APIs
Treating the platform's own interfaces as contracts with consumers and compatibility rules.
Platform Adoption
Migrating existing teams onto a platform without a mandate, and reading the adoption curve.
Platform Funding
Central cost, showback, chargeback, and justifying a team that ships no customer feature.
Platform SLOs
Committing to reliability for internal consumers who cannot choose another provider.
Platform Team Topologies
Stream-aligned, enabling, complicated-subsystem and platform teams, and their interactions.
Platform Telemetry
Instrumenting the platform itself: usage, friction, and where teams leave the paved road.
Platform Tenancy
Isolating teams sharing a cluster, account or pipeline fleet, and where isolation must be hard.
Abstraction Level Choice
How much to hide, and the leak that turns a helpful abstraction into a trap.
Cluster Architecture
How many clusters, split by what, and the blast radius each split buys.
Container Image Strategy
Base images, layer hygiene, rebuild cadence, and patching a fleet of images.
Developer Environments
Local, remote and ephemeral environments, and the fidelity each can honestly claim.
Guardrails vs Gates
Preventing a class of mistake automatically versus stopping to ask a human.
Inner Loop & Outer Loop
Where an engineer's time actually goes, and which loop a platform investment shortens.
Paved Road & Golden Path
A supported default route that is easier than the alternatives rather than mandatory.
Self-Service Provisioning
Teams getting infrastructure without a ticket, and the guardrails that make that safe.
Service Mesh Operations
What a mesh genuinely solves, its failure modes, and the cost of running one.
Service Templates
Scaffolding new services with observability, CI and security already wired in.
Chaos Engineering
Hypothesis-driven failure injection with a bounded blast radius.
Data Platform Architecture
General material on designing the analytical data estate end to end.
Data Platform Tenancy
Multiple domains on shared storage and compute, with separable access and cost.
Delivery & Release Engineering
General material on getting a change from commit to production safely and often.
ML Platform
Feature stores, training pipelines, registries and deployment.
Platform Teams
Reducing other teams' cognitive load, measured by adoption.
Platform as a Product
Adoption earned rather than mandated, with an owner and a roadmap.
Privacy Engineering
Minimisation, purpose limitation, and erasure that is implementable.
Platform Engineering & Developer Experience
Building the product other engineers build on, and being judged on whether they use it.
Data Platform Architecture
The analytical estate: storage layout, ingestion, transformation and the compute that reads it.
Delivery & Release Engineering
How code becomes a running change in production, and what stops that path being frightening.
Performance & Capacity Engineering
If traffic becomes ten times larger, what breaks first?