Developer Portals interview questions

Backstage, scaffolding, and service cataloging.

3 questions in Platform & DevEx.

Platform Engineering and Developer ExperienceA 18-minute read on how the topic fits together, before the questions.Platform engineering fundamentals55 short answers on one page, for revising rather than studying.

medium1

mediumConceptDesign

When you build a golden-path template for scaffolding new services, you're pushing every team toward one way of doing things. What do you gain from that, and what do you have to give up?

A golden path buys consistency, faster onboarding, and cheaper platform support at the cost of teams whose problem genuinely doesn't fit the template; the design answer is an escape hatch that costs something small, not a wall.

4 minmid, senior, staff

hard2

hardScenarioDesign

Six months after launching an internal developer portal, weekly active usage has plateaued at around forty percent of engineering. How would you go about figuring out why, and what would you actually do about it?

Stalled adoption is rarely a UI problem; segment usage by team and task rather than the aggregate number, then match the fix to whichever of three causes shows up - a missing daily task, a faster existing habit, or data nobody trusts.

4 minsenior, staff, lead

hardDesignScenario

You've built a service catalog with an owner field on every entry. A year later, half the owners listed are people who left the company. How would you design the catalog so that doesn't happen?

Treat ownership as a derived, continuously verified fact rather than a manually entered field: source it from an existing system of record, expire it on a schedule, and fail builds or pages loudly when it goes unverified.

4 minsenior, staff, lead