1. 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
  2. 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
  3. 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
  4. 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
  5. 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