Empathizing with engineers: How I’d actually do it as a PM
Our reviewers evaluate writing services independently. Learn how we stay transparent, our methodology, and tell us about anything we missed.
People ask: "how technical do I need to be as a PM?" My honest answer: less than you think—if you can empathize with engineers.
Empathy here isn't vibes. It's how you unlock better builds, faster unblocks, and decisions eng can make without you in every thread.
Why engineering empathy multiplies value
When I deeply understand how my eng partners work, I can:
- Sequence high-value work in a way that's buildable
- Remove blockers instead of adding status theater
- Bring customer and business context that makes tradeoffs obvious
- Create meaning (not just tickets)
- Enable engineers to decide safely within clear boundaries
You don't need to read every PR. You need to respect the craft and the constraints.
What empathy looks like day to day
- Learn their definition of done — tests, observability, migration risk, not just "UI looks right"
- Protect focus — batch interruptions; don't turn Slack into a page wire
- Bring the why — users, metrics, constraints—then ask for options
- Estimate with humility — ask what would change the estimate; don't negotiate like procurement
- Credit publicly, critique privately
- Sit in design/architecture conversations long enough to understand risk, not to cosplay as staff eng
You don't have to code
I've seen strong PMs without CS degrees ship hard technical products by:
- Asking precise questions ("what's the failure mode if X?")
- Learning system diagrams at a conceptual level
- Caring about quality, on-call load, and debt
- Never pretending to know what they don't
Fake-technical is worse than non-technical.
Anti-patterns that destroy trust
- Throwing specs over the wall
- Surprising eng with commitments made in sales calls
- Treating estimates as promises you can squeeze
- Only showing up when something's late
- Using "agile" to mean "I can change my mind daily without cost"
Practices I'd start this month
- Shadow an on-call or incident review once
- Ask each eng: what should I stop/start/continue?
- Co-write acceptance criteria for one gnarly story
- Keep a running list of tech debt themes and actually schedule some
- Celebrate craft, not just launch dates
My take
Engineering empathy is a PM force multiplier. Curiosity + respect beats a bootcamp certificate in a language you'll never commit.
Build the collaboration muscle with structured PM practice via the Product Manager Certification. The newsletter keeps these operator habits sharp.
