Why Annual Engagement Surveys Are Failing Your Engineers
I’ve sat through a lot of annual engagement surveys over 25 years. Questions about benefits satisfaction. Questions about the office, back when there was an office. Questions about company perks, whether the free snacks were the right ones, whether the wellness program felt worthwhile.
None of it was wrong to ask. Some of it genuinely mattered to someone. But sitting there answering it as an engineer, and later as an engineering leader, I remember thinking the same thing every single time: this isn’t the place where anything about my actual work is going to surface.
It took me a while to understand why that gap existed. It’s not that the people designing these surveys didn’t care about engineering teams specifically. It’s that the survey belongs to HR, and HR designs surveys around what HR controls. Benefits, perks, office policy, compensation satisfaction, all of it sits squarely inside HR’s domain. What doesn’t sit there: whether an engineer is blocked, whether priorities are clear, whether the team’s communication has degraded, whether workload has become unsustainable. Those signals belong to engineering leadership, not HR, and a survey built by one team rarely asks the questions that matter most to another.
A survey designed for everyone ends up designed for no one
Generic engagement surveys are built to work across an entire company. Sales, marketing, finance, engineering, all filling out the same form, answering the same dozen questions on the same annual cycle. That uniformity is exactly what makes the tool weak for any one function.
An engineering team’s health doesn’t look like a sales team’s health. A salesperson’s engagement might hinge on quota structure, commission clarity, or pipeline support. An engineer’s might hinge on whether they’re blocked on a dependency, whether the sprint priorities actually reflect what leadership cares about, or whether code review has turned adversarial. These are different worlds with different failure modes, and a single generic survey has to stay broad enough to apply to both, which means it ends up specific to neither.
The result is a tool that measures company-wide sentiment reasonably well and measures engineering team health almost not at all. You get a satisfaction score. You don’t get anything that tells you whether your engineering org is actually functioning.
The questions that were never being asked
Think about what a generic survey actually asks versus what an engineering leader actually needs to know week to week.
The generic version: How satisfied are you with your compensation? How would you rate our benefits package? Do you feel the office environment supports your work?
What’s missing: How blocked are you feeling right now? How clear are your priorities for this week? How sustainable is your current workload? How well is the team communicating? How much are you enjoying the work itself, separate from the benefits attached to it?
Those second five questions aren’t HR questions. They’re engineering leadership questions. They’re about the actual conditions of the work, not the conditions around the work. And because they don’t belong to HR’s traditional domain, they almost never make it onto the survey HR builds, no matter how thoughtfully HR approaches the rest of it.
This isn’t a criticism of HR teams. It’s a structural mismatch. The team that owns the listening mechanism isn’t the team that needs the specific signal, and the team that needs the signal usually isn’t the one designing the questions.
Why this gap matters more than it seems
It would be easy to say the fix is just “add some engineering-specific questions to the annual survey.” That misses the deeper problem.
Even a perfectly worded question about workload or priority clarity, asked once a year, arrives too late to be useful. Engineering conditions change week to week, not year to year. A team that’s blocked and frustrated in March could be in a completely different state by the time the annual survey rolls around in November, and the survey has no way of catching what happened in between.
The mismatch isn’t just about which questions get asked. It’s about who’s asking them, how often, and for what purpose. HR surveys exist to give the company a sense of overall sentiment once a year. Engineering leaders need something closer to continuous, and they need it built around the specific signals that predict whether their team is about to have a good quarter or a bad one.
What engineering teams actually need instead
The right tool for engineering team health isn’t a better annual survey. It’s a separate, purpose-built mechanism that engineering leaders own directly, asking questions engineering leaders actually need answered, on a cadence that matches how quickly engineering conditions change.
That’s the entire premise behind CrewPulse. Five weekly, anonymous questions, built specifically around engineering team health: morale, workload, priority clarity, communication, and whether someone feels blocked. Paired with delivery data from GitHub and Jira, so the health signals sit next to what’s actually happening in the work.
None of those five questions would fit naturally into a company-wide HR survey, and that’s exactly the point. They’re not measuring company sentiment. They’re measuring the specific conditions that determine whether an engineering team ships well and stays intact.
The bottom line
I don’t think the annual engagement survey is a bad idea executed badly. I think it’s the right tool for a different job. It can tell a company something real about benefits satisfaction and general sentiment. It was never going to tell an engineering leader whether their team is blocked, overloaded, or losing alignment, because those aren’t the questions HR was ever positioned to ask.
Engineering teams don’t need a better version of the HR survey. They need their own mechanism, owned by the people who are actually responsible for engineering team health, asking about the things only engineering leaders can act on.
CrewPulse tracks the five signals that actually predict engineering team health, weekly, alongside your delivery data. Start your free trial here.