1. Platform Team Topologies advanced

    How should platform work be organised as an organisation grows, and what structure prevents the platform becoming a bottleneck?

    2 min answer team-topologiesplatformenabling-teamsbottleneck
  2. Platform Team Topologies beginner Multiple choice

    Six platform engineers support forty product teams. Each team raises roughly 1.5 requests a week and each request costs about 90 minutes of an engineer's time once the context switch is counted. Roughly how much of the team's capacity is interrupt work and what does that number rule in or out?

    2 min answer platform teaminterruptscapacityteam topologies
  3. Platform Teams intermediate

    A platform team is overwhelmed by requests and product teams complain about waiting. What does the boundary between them need to change?

    2 min answer platform-teamsself-serviceboundaryrequests
  4. Platform Teams intermediate Multiple choice

    A platform team of 9 serving 300 engineers changes model. It stops publishing modules and libraries that teams run themselves and starts operating the runtime: it owns the clusters, the pipelines and the base images, and it holds the pager for them. Within two quarters the share of services on the supported path goes from 60% to 95% and a runtime upgrade that used to take three quarters takes five weeks. What has the organisation given up?

    3 min answer platform-teamsteam-topologieson-callcognitive-load
  5. Platform Teams intermediate

    When should an organisation create a platform team, and what distinguishes one from a service desk?

    2 min answer platformself-servicecognitive-loadbottleneck
  6. Platform Teams advanced

    You run a platform team of twelve serving four hundred engineers. Product teams say the platform is a bottleneck; your team says the requests are unbounded and they cannot do product work. Both are right. What do you change?

    2 min answer platform-teamsself-serviceboundariesprioritisation
  7. Platform Telemetry advanced

    A platform injects standard labels into every metric it scrapes: team, service, environment, pod and commit SHA. Between deploys the metrics backend is healthy. Within minutes of each fleet deploy, query latency triples, ingester memory climbs and dashboards covering the last six hours time out. Samples per second have not changed. Where is the time going?

    3 min answer prometheuscardinalityseries churnlabels
  8. Platform Telemetry intermediate

    A platform team cannot tell which of its capabilities are used, by whom, or whether they are working. What telemetry does a platform need about itself?

    2 min answer druvaplatform-telemetryusageadoption
  9. Platform Telemetry advanced

    On 11 December 2024 OpenAI rolled a new telemetry service across its Kubernetes fleet. Staging was clean; the change reached every cluster in under thirty minutes; all services degraded for roughly four hours. What is the failure chain, and which of its links is the one to design against?

    3 min answer openaikubernetescontrol planedns
  10. Platform Telemetry intermediate

    Review this platform telemetry programme. 14 dashboards, a weekly adoption report by capability, per-capability request counters with caller identity, a quarterly developer survey of 38 questions, and DORA metrics computed per product team and published weekly to leadership. Two of the seven platform engineers spend about a day a week each maintaining it. What would you remove, what would you change, and what would you leave alone?

    3 min answer platform telemetrygoodharts lawdorasurveys
  11. Platform Telemetry intermediate

    What should a platform team measure about its own platform, and what is most often missing?

    1 min answer platform-telemetryadoptionexperienceslos
  12. Platform Tenancy advanced

    A platform serves internal teams with very different scale and criticality. Should they share infrastructure?

    1 min answer platform-tenancyisolationnoisy-neighbourtiering