Tell me about a time you explained a technical decision to a non-technical stakeholder
cs-jun-008
Your answer
Answer as you would in a real interview — explain your thinking, not just the conclusion.
Model answer
Use the STAR method: Situation — describe the context (e.g., had to justify switching from XML config to a database-backed settings system). Task — what you needed to convey and why. Action — how you simplified the explanation: dropped jargon, used an analogy (e.g., 'Think of XML as a paper form you fill in before starting — if you want to change something you have to stop, edit the form, and restart. A database is like a live settings screen you can update while the system is running'). Result — stakeholder approved the change and the team delivered on time. The key is translating technical risk and benefit into business impact.
Follow-up
How do you decide how deep to go technically when writing docs for a mixed audience?