Tell me about a technical spec or requirements document you wrote. How did you decide what level of detail engineers needed?

What the interviewer is looking for

• This question tests requirements & technical specs. Writes clear problem statements and specs with constraints, edge cases and non-functional needs, at the right level of detail for engineers.
• Strong answers: Covers the problem, users, constraints, edge cases and success measures, leaves implementation to engineers, and refined it with their input.
• Likely follow-up: What did engineers ask about that you had not thought of?

Another way it may be asked: Think of a spec you wrote for engineers. What did you put in, what did you leave out, and why?

A structure to follow: Answer, explain, example, limits

1. Step 1

   Answer

   Give your direct answer in the first sentence so the interviewer knows where you are going.

2. Step 2

   Explain

   Say how it works or why you would do it that way, in plain words before jargon.

3. Step 3

   Example

   Anchor it in something you have actually done or seen, with the detail that shows hands-on experience.

4. Step 4

   Limits

   Say when your approach would not be the right one. It shows judgement.

This is guidance on shape, not a script. Use your own real experience and facts; never invent details to fill a gap. See the STAR guide and answer frameworks.

Common slips

• Reciting a definition without showing you have applied it.
• Using terms you cannot explain if asked a level deeper.
• Claiming experience beyond what you can discuss in detail.

How to practise it

Say the answer in 90 seconds, then answer the follow-up as if it were a new question.

Related questions

• If an engineer told you a feature would take three times longer than expected, what questions would you ask them?
• In simple terms, how would you explain what happens behind the scenes when someone taps a button in an app and their data loads?
• Imagine two engineering teams disagree about who should own a shared service. How would you help them reach a decision?
• How do you decide how much of a quarter to spend on technical debt versus new features? Give me a real example.
• Describe a time you worked on a product used by developers, like a platform service or developer tool. How did you learn what they needed?

Browse all questions