Describe handling conciseness feedback
Company: Datadog
Role: Software Engineer
Category: Behavioral & Leadership
Difficulty: medium
Interview Round: Technical Screen
Tell me about a time you received feedback that your answers were not concise. What was the context, the exact feedback, and how did you adjust your communication style? Walk through the actions you took, how you measured improvement, and the outcome for your team or stakeholders.
Quick Answer: This question evaluates a candidate's ability to accept and act on conciseness feedback, encompassing communication clarity, adaptability, measurement of improvement, and leadership influence on stakeholder interactions.
Solution
Approach
- Use STAR to frame the story.
- Apply BLUF: start with the answer, then 1–3 key points.
- Include concrete metrics to show improvement.
Sample answer (condensed, software-engineering context)
- Situation: During design reviews for a new telemetry ingestion service, my updates and Slack replies tended to include long background explanations. This caused meetings to run long and decisions to spill into follow-up threads.
- Task: Secure alignment on the design and unblock implementation within the sprint.
- Exact feedback: My tech lead said, “Your answers bury the lede. Start with the recommendation and two supporting points; put the rest in an appendix.” A PM added, “I’m losing the key ask in the details.”
- Actions:
- Adopted BLUF for live and written comms: lead with the recommendation, then 2–3 bullets on rationale and trade-offs.
- Created a response template for Slack/email: 1) Answer, 2) Why (≤3 bullets), 3) Risks/Next step, 4) Link to detail.
- Time-boxed live answers to ~30 seconds, then asked, “Do you want detail on trade-offs, estimates, or risks?”
- Added TL;DR to design docs and kept complexity in appendices.
- Asked a clarifying question before answering to target the scope.
- Practiced trimming: removed filler, collapsed examples, used numbers instead of qualifiers.
- Measurement:
- Design review duration dropped ~35% (avg 45 → 29 minutes across 4 sessions).
- Follow-up clarification messages per decision thread dropped ~60% (≈5 → 2).
- Decision latency decreased from ~2 days to same-day on two key decisions.
- PR review turnaround improved (median 72h → 28h) after concise summaries in PR descriptions.
- Quick pulse survey (1–5 clarity): 3.1 → 4.4 over a month (n=7 teammates).
- Outcome:
- We finalized the ingestion design in one session instead of two, unblocking work and helping us land the milestone one sprint earlier.
- Stakeholders reported higher confidence; fewer re-explanations freed ~8 engineer-days that month.
- As a side benefit, I rewrote on-call runbook intros into one-paragraph BLUFs, contributing to a ~15% reduction in MTTR for two incidents (faster first actions).
Why this works
- BLUF reduces cognitive load and surfaces the decision/ask immediately.
- Structuring details in bullets and appendices preserves completeness without overwhelming the audience.
- Measuring behavior change (time, follow-ups, decisions, reviews) shows impact beyond “felt better.”
Pitfalls and guardrails
- Don’t over-compress: confirm if the audience wants more depth. Ask, “Is this level of detail right?”
- Keep an appendix or doc link so experts can drill down.
- Calibrate to the audience: executives want the decision and risk; engineers may want trade-offs and constraints.
- Rehearse for high-stakes reviews; write the BLUF first, then expand if needed.
Reusable template (for your own story)
- Situation: [Project/meeting context] + [why concision mattered].
- Task: [Decision/approval you needed].
- Feedback (quote): “[…]” from [role].
- Actions: BLUF + response template + time-box live answers + TL;DR in docs + clarify-before-answering.
- Measurement: meeting length, follow-up questions, decision latency, PR turnaround, clarity rating.
- Outcome: [Business/engineering impact], [time saved], [quality/throughput/incident metric].
Interview delivery tip
- Open with a one-sentence BLUF: “I was told my answers buried the lede; I adopted BLUF and a 3-bullet structure, which cut meeting time by ~35% and sped reviews by >2×.” Then walk through STAR briefly and cite 2–3 metrics.