Skip to main content
Technology & Artificial Intelligence

Why data engineers struggle with stakeholder communication

Low extraversion and high technical focus make stakeholder communication a consistent friction point for data engineers. Here's the personality-aware fix.

Data engineers citing stakeholder expectation mismatch as top frustration

~48%

dbt Community Survey 2024

Top reason data engineers don't get promoted to staff

Insufficient cross-functional influence

Staff Engineer interviews, Will Larson

The Personality Root

Data engineers typically score low on extraversion — the trait that drives spontaneous communication, relationship maintenance, and proactive status updates. This is fine for solo pipeline work and becomes a liability when stakeholders discover outages through broken dashboards rather than an engineer's heads-up. The result: trust erosion not because the system failed, but because nobody communicated.

The Fix

The goal is not more social energy — it's building communication into the system. Weekly automated pipeline health emails, a data changelog, and a clear escalation path cost almost no social energy and produce outsized trust.

Root cause

Why this happens

Communication problems in data engineering are structurally tied to low extraversion — making a personality-rooted explanation accurate and differentiated.

In practice

Do and don't

Do

  • Send a weekly 3-sentence pipeline status update to data consumers
  • Maintain a data changelog — one sentence per breaking schema change
  • Define an SLA and communicate it before a pipeline goes live
  • Build a shared Slack channel for data quality incidents with a bot

Don't

  • Wait for stakeholders to ask why their dashboard looks wrong
  • Assume analysts track schema changes through dbt docs
  • Set expectations after the first failure
  • Manually notify stakeholders during each incident
Practice

Exercises to work through this

Visibility update (2 minutes, weekly)

2 minutes
  1. 1.Write one thing you finished this week in one sentence.
  2. 2.Name who it helped or what it unblocked.
  3. 3.Share it in your team channel, a standup, or a 1:1 — no preamble.

Outcome

Decision-makers know your output without you having to oversell.

One genuine initiation (2 minutes)

2 minutes
  1. 1.Identify one person whose work you respect.
  2. 2.Write one specific thing that impressed you about their work.
  3. 3.Send that one thing as a short message — no ask, no agenda.

Outcome

Build a real network without transactional energy.

Questions

Common questions

Q

How quickly can I fix a career problem like imposter syndrome or visibility?

Most people notice a shift within 2–4 weeks of a consistent daily practice. The problem isn't information — it's repetition. Reading about confidence doesn't build it. Running the drill before every relevant situation does.

Q

What if I try these tools and they don't help?

Run the drill for 10 consecutive days before evaluating. Most tools fail because they're tried once in a high-stakes moment — the opposite of how they're designed. They're built for low-stakes practice first, real-situation use second.

Q

Is this career coaching?

No. This is self-directed skill training using personality science. For major career decisions, job loss, or clinical anxiety, work with a qualified coach or therapist. These tools are for building specific, measurable work behaviours.

Explore more

Related pages

PersonalityHQ · Assessment

Know your profile before you decide.

Understand your communication profile