Datadog·Software Engineer·Onsite - Behavioral / Leadership·Senior

Senior

Jul 2026

Summary

Behavioral round at Datadog for a software engineering role. One question the whole session, focused on communication and self-awareness. Pretty introspective stuff for an engineering interview.

Questions Asked (1)

Describe a time you got feedback that your communication was too long-winded. What was the situation, what exactly did someone tell you, and what did you actually do to fix it going forward?

Adaptability & AmbiguityStakeholder Management

Author's notes

This one caught me flat-footed because I hadn't prepped a story specifically about communication feedback.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Choose a specific instance where you received feedback about being long-winded, ideally in a technical or cross-functional setting. Clearly describe the situation, the exact feedback, and the concrete steps you took to improve, emphasizing measurable outcomes and sustained change. Show self-awareness and a growth mindset.

Pro tip: Demonstrate that you not only fixed the immediate issue but also developed a systematic approach to communication, such as using structured formats (e.g., BLUF, STAR) or seeking ongoing feedback, which shows maturity and long-term commitment to improvement.

1. Set the Context

Briefly describe the situation: your role, the project, and the audience (e.g., during a design review or sprint planning). Keep it concise to focus on the feedback and your response.

2. Share the Specific Feedback

Quote or paraphrase exactly what was said, including who said it (e.g., a manager, a peer). Be honest and avoid downplaying the feedback.

3. Explain Your Initial Reaction and Analysis

Describe how you processed the feedback, why you think you were long-winded (e.g., over-explaining due to uncertainty), and how you decided to address it.

4. Detail the Actions You Took

List concrete steps you implemented to improve, such as preparing agendas, using bullet points, practicing concise summaries, or asking for feedback after meetings.

5. Highlight the Results and Ongoing Improvement

Share the positive outcomes (e.g., faster meetings, clearer communication) and how you continue to refine your communication skills.

Key Points to Mention

Specific example of feedback received, including the exact words or paraphrase.
Self-awareness of why you were long-winded (e.g., nervousness, desire to be thorough).
Concrete actions taken to improve, such as structuring responses with the STAR method or using a 'headline first' approach.
Measurable results, like reduced meeting time or positive feedback from stakeholders.
Ongoing commitment to clear communication, such as seeking regular feedback or practicing with peers.
Relevance to software engineering, e.g., writing concise design docs or giving efficient stand-up updates.

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.