The interviewer asks: "How do you explain the value of a Backstage software catalog to a team that is skeptical about adopting it?" Which answer addresses skepticism most effectively?
Option B is strongest: it identifies the three sources of skepticism before addressing them — which shows the engineer has had these conversations before — and addresses each with a specific mechanism rather than a general benefit. The wiki-vs-catalog contrast ('what someone wrote three months ago' vs. 'actual build status') is concrete. The maintenance objection rebuttal explains exactly how updates happen (catalog-info.yaml in the service repo, updated in the same PR). The ROI argument is quantified (67% completeness = 33% of services with no findable owner) and translated into a cost (minutes per incident, hours per onboarding), then restated as the business case ('reduce Slack interruptions'). Developer portal vocabulary:Software catalog — a registry of all software components (services, APIs, pipelines) with their metadata, owners, and health status. Catalog completeness — the percentage of known services with registered, up-to-date catalog entries. catalog-info.yaml — the metadata file stored in a service's repository that registers it with Backstage. Self-serve lookup — finding information without asking another person. Options C and D are accurate but lack the pre-framing of skepticism sources and the specific ROI translation.
2 / 5
The interviewer asks: "How do you report on the current state of your developer portal to leadership?" Which answer uses the most professional metrics framing?
Option B is strongest: it names three specific metrics with real numbers, explains what each number means in business terms (not just the percentage), quantifies the risk of the gap (100 services with incomplete entries = high incident response time), connects golden path adoption to the specific gaps it prevents (security scanning, SLO configuration, observability), provides a before/after comparison for the productivity metric, and articulates the reporting principle explicitly ('activity vs. impact'). The 'what I avoid' section — page view counts — names the common anti-pattern and explains why it fails, which is the insight that separates a mature portal engineer from one who is new to the role. Developer portal metrics vocabulary:Catalog completeness — the percentage of known services with fully populated catalog entries. Golden path adoption rate — the percentage of new services created using approved scaffolding templates. Time-to-first-deployment — the elapsed time from a new engineer's start date to their first successful production deployment. Vanity metric — a metric that looks positive but does not correlate with business outcomes (e.g., page views). Options C and D are accurate but lack the business outcome translation for each metric and the anti-pattern explanation.
3 / 5
The interviewer asks: "Your Tech Radar shows React has moved from Trial to Assess. How do you explain that movement to an engineering team?" Which answer uses Tech Radar vocabulary most precisely?
Option B is strongest: it opens with the critical insight that the ring movement is counterintuitive (Trial is closer to adoption than Assess), provides the precise meaning of all four rings in operational terms, explains the specific message for the affected technology (React), distinguishes 'do not start new work' from 'rip out existing implementations' — which is the most common misunderstanding — and provides the exact team communication message. The 'process signal, not a production emergency' framing is the key conclusion that prevents engineers from over-reacting. Tech Radar vocabulary:Tech Radar — a technology assessment framework (originated by ThoughtWorks) that categorises technologies into Adopt, Trial, Assess, and Hold rings. Adopt — a recommendation to use a technology as the default choice. Trial — a recommendation to actively use a technology in real projects to gather evidence. Assess — a recommendation to monitor a technology without committing to new projects. Hold — a recommendation to freeze new usage of a technology. Options C and D are accurate but lack the counterintuitive ring order explanation and the 'process signal vs. production emergency' framing.
4 / 5
The interviewer asks: "How do you drive adoption of golden path templates among engineering teams?" Which answer demonstrates the most effective adoption strategy?
Option B is strongest: it opens by naming the common mistake (documentation instead of adoption strategy), identifies the actual reason for non-adoption (friction in the template), provides three named adoption levers with specific mechanisms, introduces the definition test for a golden path ('one command to a working service with no post-template homework'), explains how to use the catalog as an adoption driver (gap list per team), and provides the comparison that makes the value concrete (10 minutes vs. 2-5 days). The 'product problem, not documentation problem' framing is the key insight that distinguishes a senior portal engineer from one who writes README files. Developer experience vocabulary:Golden path — the recommended, pre-configured path for creating new services that incorporates all organisational standards. Scaffolding — code and configuration generated automatically from a template. DORA metrics — four key DevOps metrics: deployment frequency, lead time for changes, change failure rate, and time to restore service. Adoption friction — any step or obstacle that reduces the likelihood of a tool being used. Options C and D are accurate but lack the friction diagnosis and the gap-visibility adoption mechanism.
5 / 5
The interviewer asks: "How do you build the business case for investing in a developer portal to senior management?" Which answer is most persuasive?
Option B is strongest: it names four specific cost categories (not generic 'productivity'), provides actual numbers in each category (18 minutes → 2 minutes for incident ownership; 50 incidents/month; 800 minutes saved), shows the calculation method for each cost so management can verify it, and closes with the break-even framing that converts the investment into a financial decision rather than a technology aspiration. The 23-minute context-switching cost (based on the widely cited Gloria Mark research) adds credibility to the interruption cost calculation. The break-even summary ('investment to save N hours per quarter; break-even in M weeks') is the exact format management uses to approve tool investments. Developer portal ROI vocabulary:Time-to-first-deployment — time from onboarding start to first successful production deployment; a key onboarding efficiency metric. Mean time to ownership identification — the average time to find the owner of a service during an incident. Context-switching cost — the productivity loss from interruptions; estimated at 23 minutes of recovery time per interruption. Break-even point — the time period at which savings equal the initial investment. Options C and D are accurate but lack the specific numbers and the break-even framing.