Design an internal developer platform
PremiumCloud infrastructureMedium
- Platform engineering
- Golden paths
- Service catalog
Quick answer
This cloud infrastructure interview question asks you to design an internal developer platform. Aim for a design that runs reliably and securely in the cloud at a sensible cost, then explain the services, regions, deployment and trade-offs. Interviewers want to see how you balance reliability, security and cost.
The problem
Design an internal developer platform (IDP) with a developer portal: an engineer creates a service from a template and gets a repository, pipeline, environments, monitoring and an owner record in minutes, with no tickets. The hard parts are one paved path that fits 150 teams, safe self-service on shared clusters, and a catalog that stays true.
What must an internal developer platform do?
- Service scaffolding: Create a service from a golden-path template (Go API, Node web app, worker) that sets up the repository, CI pipeline, deploy config, dashboards, alerts and catalog entry.
- Service catalog: Show every service with its owner team, on-call, dependencies, docs and links, kept fresh from a metadata file in each repository.
How well must it do it?
- Fast start: A new service is running in staging within 30 minutes of creation.
- Tenant isolation: Teams can change only their own namespaces and resources; production changes are audited.
What scale should you design for?
Use these numbers in your estimates.
The scale numbers unlock with this questionUnlock
Key concepts
- Platform engineering
- Golden paths
- Service catalog
- GitOps
- Preview environments
- Self service infrastructure
How you’ll practise
- Requirements
- Environments and topology
- Deployment pipeline
- Reliability and disaster recovery
- Observability and cost
- Wrap-up
Lala, personalized to you, gives a hint when you ask and reviews your design when you are ready.
What do interviewers look for?
In any cloud infrastructure design round.
- Clarifies availability, security and cost targets
- Chooses managed services with reasons
- Plans regions, zones and failover
- Covers identity, secrets and network boundaries
- Explains deployment, rollback and observability
- Keeps an eye on cost as usage grows
Questions people ask about this interview question
- Which design type is this question?
- It is a cloud infrastructure question. You design an internal developer platform and explain your choices the way you would in an interview.
- Is this question asked at entry level?
- It is marked Medium. Entry-level engineers can practise it, but it expects you to reason about requirements and trade-offs, not only list components.
- What should I cover first?
- Start with the workloads, the availability target and the security and cost limits. Agree on scope with the interviewer before you design anything.
- Can I practise it for free?
- It is a premium question. Sign up and unlock it once for 10 credits; it then stays unlocked. When you finish, Lala, your personalized AI mentor, can review your design for 30 credits.
Related questions
- Design an application health check systemCloud infrastructure · EasyPremium
- Design a distributed software release orchestration platformCloud infrastructure · HardPremium
- Design a multi-cloud disaster recovery orchestration platformCloud infrastructure · HardPremium
- Design a global infrastructure change approval & risk assessment platformCloud infrastructure · HardPremium
Updated · Written by the SevyDevy team