The interviewer asks: "How do you approach API versioning strategy for a platform used by hundreds of external developers?" Which answer best demonstrates API Platform Engineer expertise?
Option B is strongest because it states a clear choice with reasoning, pairs versioning with an operational practice — the deprecation window — and mentions automated breaking-change detection in CI, which shows production maturity. Option A identifies the right technique but gives no rationale, deprecation plan, or tooling, which is insufficient at platform engineer level. Option C is practical and mentions the developer portal, but it does not address tooling, automation, or how the platform enforces the policy. Option D provides an excellent comparison of all three strategies and the gateway-enforcement insight, but it is structured as a framework lecture rather than a decisive engineering recommendation. API Platform interview best practice: state your choice, justify it for the given scale, and describe the operational practices that support it.
2 / 5
The interviewer asks: "What is the role of an API gateway in a microservices architecture, and what would you centralise there?" Which answer best demonstrates API Platform Engineer expertise?
Option B is strongest because it lists the key gateway responsibilities with precise terms, explains the rationale — keeping services lean and ensuring consistent enforcement — in clear English that non-native speakers can replicate. Option A is accurate but superficial; routing alone misses the enforcement and observability value that platform engineers care about. Option C is good and adds canary routing, which is a valuable platform insight, but the language is less precise than B and omits TLS termination. Option D shows sophisticated thinking about not over-centralising and pairing the gateway with a service mesh, but starting with what not to do can leave the interviewer uncertain about what you would actually build. API Platform interview best practice: list the cross-cutting concerns you centralise and explain why centralisation at the gateway reduces duplication across services.
3 / 5
The interviewer asks: "How would you design a rate limiting strategy that is fair to all developers while protecting backend services?" Which answer best demonstrates API Platform Engineer expertise?
Option B is strongest because it covers the algorithm choice with justification, applies limits at two granularities (burst and daily), and includes the critical developer experience detail — RateLimit headers — that allows clients to self-regulate. This demonstrates end-to-end platform thinking. Option A describes the outcome but not the design; returning a 429 is the minimum, not a strategy. Option C introduces circuit breakers, which is a good complementary concern, but it does not address algorithm choice or how developers will know their remaining quota. Option D is technically excellent — distributed Redis counters and endpoint cost weighting are production-grade features — but the answer is dense and starts with implementation details before establishing the strategy. API Platform interview best practice: always mention the headers you expose to developers; it shows you think about DX, not just enforcement.
4 / 5
The interviewer asks: "What makes a great developer portal, and how do you measure whether developers are succeeding with your APIs?" Which answer best demonstrates API Platform Engineer expertise?
Option B is strongest because it anchors on a single north-star metric — time-to-first-successful-call — then lists the concrete portal features that drive it, and rounds off with a three-stage funnel that shows how to operationalise the measurement. Option A identifies the right ingredients but at a surface level that any developer could say; it does not demonstrate platform engineering thinking. Option C introduces an excellent three-pillar framework and ties each pillar to a metric, which is sophisticated, but it lacks concrete portal features and does not explain how the metrics are actually collected. Option D treats the portal as a product with OKRs, which is the right mindset, and mentions A/B testing, but it focuses on measurement without describing what the portal should contain. API Platform interview best practice: lead with the metric that defines developer success, then derive the features from that metric.
5 / 5
The interviewer asks: "How do you manage the API lifecycle from design through deprecation in a large organisation?" Which answer best demonstrates API Platform Engineer expertise?
Option B is strongest because it names four explicit lifecycle stages, gives a concrete tool example — Spectral — links each stage to an actionable practice, and ends with an adoption-metric-driven deprecation decision. The structure makes it easy for the interviewer to follow. Option A is a paraphrase of the question rather than an answer; it shows awareness of the concept but no implementation knowledge. Option C covers the design and deprecation phases well and mentions usage tracking, but it skips the Build and Publish stages, leaving a gap in the lifecycle story. Option D introduces API governance tooling — Spectral, Prism, and an API registry — which is excellent, and the automated notification workflow is a mature touch, but the answer is tool-heavy and does not structure the lifecycle as clearly as B. API Platform interview best practice: structure your answer around explicit lifecycle stages to show you have an end-to-end mental model, not just point solutions.