1. Platform API Deprecation intermediate

    A platform must deprecate an API or capability that many teams depend on. How is this done without destroying trust or stalling indefinitely?

    2 min answer deprecationplatformmigrationtrust
  2. Platform API Deprecation intermediate

    A platform must remove a widely-used internal API. How should the deprecation be run?

    2 min answer deprecationmigrationtelemetrycommunication
  3. Platform API Deprecation intermediate

    An internal platform must remove a capability that several teams depend on. How should the deprecation be run?

    2 min answer verceldeprecationinternal-apimigration
  4. Platform API Deprecation advanced

    The platform is removing v1 of its config API. Telemetry showed 412 calling services at announcement; after six months of a funded migration 9 remain - 4 have no owner in the catalogue, 3 are monthly batch jobs that touch the API only on the first of the month, and 2 belong to a team that says it will not move this quarter. Removal was promised for the end of the quarter. Sequence the removal so you keep the date and stay reversible at every step.

    3 min answer deprecationbrownoutsunsetreversibility
  5. Platform API Deprecation intermediate

    You need to retire a platform API used by 60 services. Describe the plan.

    2 min answer deprecationmigrationplatform
  6. Platform API Deprecation advanced Multiple choice

    Your gateway samples 1% of platform API requests into traces and that trace data is the only usage record you have. One caller is a monthly batch job that makes 3 calls a month. Roughly what is the chance it appears at all in six months of this data and what does that number rule out?

    3 min answer deprecationsamplingtelemetryprobability
  7. Platform APIs intermediate

    A platform exposes APIs to internal teams. How should these differ from APIs exposed to external customers?

    2 min answer platform-apiinternalversioningcoupling
  8. Platform APIs beginner

    A platform team argues that their internal API needs no versioning because every caller is inside the company and can be found with a code search. What is wrong with that reasoning?

    2 min answer internal apiversioningcouplingdeployment
  9. Platform APIs advanced

    An interviewer gives you this. "Our platform takes a short YAML file per service and a controller reconciles it into real infrastructure. 300 services use it. Product wants to change the default CPU request for the services that never set one. Walk me through how you would ship that."

    3 min answer platform apisdefaultsreconciliationblast radius
  10. Platform APIs intermediate Multiple choice

    Product teams need a Kafka topic and an object-storage bucket per service with quotas and retention that change over time. Should the platform expose a synchronous provisioning call that returns when the resource exists or a declarative resource reconciled by a controller or a pull request into a shared Terraform repository?

    3 min answer platform apideclarativereconciliationprovisioning
  11. Platform APIs intermediate

    The Hugging Face Hub stored large model and dataset files with Git LFS which versions whole files - appending 1 MB to a 5 GB file re-uploads 5 GB. In 2025 the Hub began moving repositories onto Xet storage which splits content into roughly 64 KB content-defined chunks aggregated into roughly 64 MB blocks so only changed chunks travel. The API developers call did not change. What forced the change and what had to stay stable and where would copying it be a mistake?

    3 min answer hugging facededuplicationstorageplatform api
  12. Platform as a Product intermediate

    A platform team builds capabilities that teams do not adopt. What does treating the platform as a product actually require, and how is adoption measured without mandates?

    3 min answer platform-engineeringadoptionproduct-thinkingpaved-road