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?

What the interviewer is looking for

• This question tests developer experience. Treats developers as customers, gathers their feedback, cares about documentation, versioning and smooth migrations.
• What to bring out: Uses interviews, usage data, support threads and hands-on use, and improves documentation and onboarding as well as features.
• Expect a follow-up like: What was the most surprising thing developers told you?

Another way it may be asked: If your customers are other engineers, how do you find out what is frustrating them? Give an example.

A structure to follow: STAR, with the weight on Action and Result

1. Step 1

   Situation

   One or two sentences: where, when and what was at stake. Pick a real example you were close to.

2. Step 2

   Task

   What you personally were responsible for. Say "I", not only "we", so the developer experience you showed is visible.

3. Step 3

   Action

   The two or three things you did and why you chose them over the alternatives. This should be about half your answer.

4. Step 4

   Result

   What changed, in your own measure of it, and what you would do differently. Only use numbers you can stand behind.

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

• Describing what the team did without saying what you did.
• Choosing an example with no clear outcome, or one you cannot answer detailed questions about.
• Ending on the action and skipping the result and what you learned.

How to practise it

Write two bullet points for each STAR letter, then say the answer aloud in about two minutes.

Related questions

• When a breaking change to a platform is unavoidable, how do you roll it out to the teams who depend on it?
• In simple terms, how would you explain what happens behind the scenes when someone taps a button in an app and their data loads?
• If an engineer told you a feature would take three times longer than expected, what questions would you ask them?
• Imagine two engineering teams disagree about who should own a shared service. How would you help them reach a decision?
• Tell me about a technical spec or requirements document you wrote. How did you decide what level of detail engineers needed?

Browse all questions