Employee Engagement Survey Questions: 25 Questions That Actually Surface Problems

The internet is full of "100 Employee Engagement Survey Questions!" articles. They're written for HR departments that need to justify a 45-minute annual survey and a three-month analysis cycle.

You don't need 100 questions. You need the right 25, organized by what they actually tell you about your team.

Each question below includes what it measures, what a concerning answer looks like, and what to do about it. Use them in rotation across your monthly pulse surveys, 3-5 at a time. By month six you'll have covered every dimension that matters.

How Scoring Works

Every question in this article uses the same 0-10 scale. This keeps things consistent with eNPS and means your team only ever learns one scoring system.

0 = Strongly disagree / Never / Not at all 10 = Strongly agree / Always / Completely

For team averages, here's what the ranges mean:

Team Average	Signal
8.0-10.0	Strong. This area is working. Protect it.
5.0-7.9	Neutral zone. Not broken, but worth monitoring. Small issues may be building.
0-4.9	Problem area. Something is wrong here. Act on it this month.

These thresholds apply to every scored question below.

The Anchor: Your eNPS Question

This goes on every single survey. Every month. No exceptions.

"On a scale of 0-10, how likely are you to recommend this company as a place to work?"

This is the eNPS question. It gives you a single score that tracks your team's overall sentiment over time. Responses split into Advocates (9-10), Neutrals (7-8), and Critics (0-6).

Why this question specifically: It's a proxy for everything. People who would recommend your company are generally engaged, trust leadership, see a future for themselves, and feel valued. People who wouldn't are telling you at least one of those things is broken.

Red flag: More than 25% of respondents scoring 0-6. At a 40-person company, that's 10 people with something genuinely wrong.

What to do: Look at the open-text responses from the same survey. The eNPS score tells you the severity. The comments tell you the cause.

Category 1: Flight Risk (Will People Leave?)

These questions catch early warning signs of turnover. Research from Work Institute (2024 Retention Report) shows that 75% of voluntary turnover is preventable, but only if you catch the signals early.

Question 1

"I can see myself working here 12 months from now." (0-10)

The most direct flight risk indicator you can ask. People know before they start looking. This question catches them in the "thinking about it" phase, which is weeks to months before "actively interviewing."

Team average 8-10: They're staying for now. Keep doing what you're doing.
Team average 5-7: Some ambivalence in the team. Something specific is creating doubt. Worth investigating in open-text responses.
Team average below 5: Active retention risk. This is your #1 priority. People are either already looking or will be soon.

Question 2

"I feel valued for my contributions here." (0-10)

People don't leave companies. They leave situations where they feel invisible. This question catches the recognition gap that founders often miss because they're focused on the business, not on explicitly acknowledging individual work.

Red flag: Scores below 5 correlating with your highest performers. That combination means your best people feel taken for granted.
What to do: Start recognizing specific contributions publicly. Not vague "great job team" messages. Name the person, name the work, name why it mattered.

Question 3

"My compensation is fair for the work I do." (0-10)

Comp is a hygiene factor. It doesn't make people engaged when it's good, but it actively disengages them when it's bad. A persistent team average below 5 on this question means you're losing people to companies that pay market rate.

Warning: Don't ask this question if you can't do anything about it. Asking about compensation and then visibly not addressing it erodes trust faster than not asking.
Better approach: Ask this question quarterly, not monthly. And have a plan for what happens when scores are low.

Category 2: Manager Trust (Is Leadership Working?)

In companies with 25-100 employees, "management" often means the founder plus 3-5 team leads who were promoted because they were good at their jobs, not because they were good at managing people.

Gallup's research consistently shows that the manager accounts for 70% of the variance in team engagement scores. For a founder, the uncomfortable version of this finding is: if your team leads aren't good managers, your engagement score is capped regardless of everything else you do.

Question 4

"I feel comfortable raising concerns with my direct manager." (0-10)

The trust question. If people can't be honest with their manager, they definitely can't be honest with you.

Team average below 5: Your manager either punishes honesty (actively bad) or ignores it (passively bad). Both produce the same result: silence.
What to do: Have a frank conversation with any manager whose team averages below 5 on this question. Not punitive. Developmental. "Your team doesn't feel safe raising concerns with you. Let's figure out why."

Question 5

"My manager gives me useful feedback on my work." (0-10)

"Useful" is the operative word. Plenty of managers give feedback. Most of it is either too vague ("nice work"), too late ("remember that thing three months ago?"), or too focused on what went wrong rather than how to do it differently.

Red flag: High scores on "My manager is supportive" combined with low scores on "My manager gives useful feedback." That's a manager who's nice but not helping anyone grow.

Question 6

"When I raise an issue, something actually changes." (0-10)

This measures follow-through. It's one thing to feel heard. It's another to see your feedback result in action. Companies where employees score this question low have a "suggestion box" culture: feedback is collected, acknowledged, and ignored.

Team average below 5 from more than 30% of respondents: Your feedback loop is broken. This is the #1 reason response rates drop over time.

Question 7

"I trust the leadership team to make good decisions for the company." (0-10)

A different dimension from manager trust. This is about strategic confidence. "Do I believe the people running this company know what they're doing?" Low scores here often come from lack of transparency about business decisions, not from bad decisions themselves.

What to do: Share more context about decisions. Founders often make good calls based on information only they have. Your team doesn't have that context. They just see the output and wonder why.

Category 3: Workload and Burnout (Is the Pace Sustainable?)

Burnout in founder-led companies has a specific pattern. The founder works 60-hour weeks because they're building something they own. They unconsciously set that as the cultural norm. The team matches the pace out of loyalty or perceived expectation, not intrinsic motivation. Within 12-18 months, the best people start declining.

A 2024 Deloitte survey found that 77% of workers have experienced burnout at their current job, and 57% of those said their employer isn't doing enough to address workplace burnout.

Question 8

"My workload has felt manageable this month." (0-10)

Simple. Direct. Monthly tracking of this question catches the slow creep from "busy but manageable" to "drowning but not complaining."

Team average below 5 for two consecutive months: You have a structural capacity problem, not a temporary crunch. Something needs to come off the plate.

Question 9

"I rarely feel pressure to work outside my normal hours." (0-10)

Low scores here mean the pressure is real, whether it's impossible deadlines, everyone else being online at 9pm, or a culture where logging off first feels like a career risk. Some people work late voluntarily because they're in flow. That's different from working late because they feel they have to.

Team average below 5: Your culture has a boundary problem. Address it publicly. "I've noticed people working late consistently. That's not the expectation. Let's talk about what's driving it."

Question 10

"I have the resources and tools I need to do my job well." (0-10)

This catches the silent productivity killers. The slow laptop that wastes 30 minutes a day. The missing software license that forces workarounds. The understaffed team that means everyone covers two roles. People stop mentioning these things after a while because they assume nothing will change.

Team average below 5: Ask a follow-up in the next survey: "What's the #1 tool, resource, or support that would most improve your work?" Then actually provide it.

Question 11

"I can disconnect from work during evenings and weekends without guilt." (0-10)

The guilt question matters more than the behavior question. Someone who works on Sunday because they want to is different from someone who works on Sunday because they'll fall behind if they don't. This question catches the second scenario.

Team average below 5: The team doesn't feel permission to switch off. This often starts at the top. If you're sending Slack messages at 11pm, your team reads that as an expectation regardless of what you say.

Category 4: Growth and Development (Do People See a Future?)

In founder-led companies, career paths are often unclear because the company's own path is unclear. That's fine for people who joined for the adventure. It's less fine for the senior hire you brought in at month 40 who expected some structure.

Question 12

"I see a clear path for my professional growth here over the next 12 months." (0-10)

The retention insurance question. People leave when they can't see what's next. In a 50-person company, "what's next" doesn't have to mean a promotion. It can mean new responsibilities, new skills, or leading a project. But it has to mean something.

Team average below 5, combined with high scores on "I do good work here": You're growing someone else's next hire. They like the work but don't see a future. Fix it or lose them within 6 months.

Question 13

"I've had a meaningful conversation about my career development recently." (0-10)

A 0 means "hasn't happened." A 10 means "yes, it was genuinely useful." The middle range tells you conversations are happening but not landing. If the team average sits below 5, your managers aren't having development conversations. That's a coaching gap, not a survey problem.

Question 14

"I'm learning new skills or growing professionally in my current role." (0-10)

Stagnation is the quiet engagement killer. People don't always leave for more money. They leave because they stopped growing and the days started feeling identical.

What to do when the team average is below 5: Budget $500-1,000 per person per year for professional development. Courses, conferences, books, certifications. The ROI is retention. One prevented departure saves you $15,000-45,000 in replacement costs.

Question 15

"My strengths are used well in my current role." (0-10)

The misalignment detector. Someone might be great at their job but feel like their best skills are being wasted. A designer who spends 80% of their time on admin. An engineer doing QA instead of building. A team average below 5 here means you have the right people in the wrong seats.

Category 5: Culture and Belonging (Is This a Team or Just a Group?)

Culture in a small company isn't about ping-pong tables or unlimited PTO policies. It's about whether people feel like they belong to something that matters, or whether they're just collecting a paycheck at a place that happens to employ them.

Question 16

"I feel like I belong on this team." (0-10)

Direct belonging measurement. In companies with 25-100 people, belonging is hyper-personal. Everyone knows everyone. Being the person who doesn't feel included is more visible and more painful at this scale.

Low scores correlated with tenure under 6 months: Your onboarding isn't building connection. New hires are arriving and staying on the outside.
Low scores correlated with remote employees: Your remote culture needs work. If in-office people feel like they belong and remote people don't, you have a two-tier culture.

Question 17

"I understand how my work contributes to the company's goals." (0-10)

The line-of-sight question. Engagement drops when people can't see how their daily work connects to something bigger. This is common in growing companies where roles become more specialized and people lose sight of the overall picture.

What to do: Monthly all-hands where you share company goals, how each team contributes, and where the company stands. Takes 30 minutes. Solves the problem for most people.

Question 18

"Information and decisions are shared transparently at this company." (0-10)

The transparency test. Low scores here usually mean decisions get made and announced without context. People don't need to be consulted on everything. But they need to understand why.

Team average below 5: People feel out of the loop. The fix is usually cheap: share the reasoning behind decisions, not just the decisions themselves.

Question 19

"I'm proud to tell people where I work." (0-10)

An emotional version of the eNPS question. This one captures identity. People who score 8-10 here are advocates who recruit their friends, defend the company in public, and stay through rough patches. People below 5 are emotionally checked out.

Question 20

"This company handles disagreements and conflicts fairly." (0-10)

How a company handles conflict tells people more about the culture than any values statement on the wall. Low scores here often point to inconsistent treatment, favoritism, or unresolved interpersonal issues that everyone knows about but nobody addresses.

Team average below 5: There's likely a specific incident or pattern driving this. The open-text question will tell you what it is.

The Essential Open-Text Questions

Numbers give you the trend. Open-text gives you the story. Include at least one of these in every survey.

Question 21

"What's the one thing we could change to make this a better place to work?"

The classic. "One thing" is important. It forces prioritization. Without the constraint, people write vague wish lists. With it, they tell you the thing that bothers them most.

Question 22

"What's something that went well this month that we should keep doing?"

Equally important as the problems. You need to know what's working so you can protect it. Companies that only ask about problems create a culture where surveys feel negative.

Question 23

"Is there anything you'd like leadership to know that you haven't felt comfortable sharing?"

The safety valve. This question occasionally surfaces things you'd never hear in a 1:1. Concerns about a specific manager. A policy that's quietly frustrating everyone. A team dynamic that's gone bad. The anonymous format makes this safe in a way that face-to-face conversations aren't.

Question 24

"If you could change one thing about how your team works together, what would it be?"

Team-level instead of company-level. Catches dynamics that company-wide questions miss. Especially useful in companies where some teams are thriving and others aren't.

Question 25

"What would make you more excited to come to work each day?"

Forward-looking instead of backward-looking. This surfaces aspirations and motivations, not just complaints. The answers often reveal low-cost, high-impact changes: more flexibility, better tools, clearer communication, or recognition that feels genuine.

How to Use These 25 Questions

Don't send all 25 at once. That defeats the purpose of a quick pulse survey. Here's the rotation:

Every month (always include):

The eNPS question (anchor)
One open-text question (rotate between 21-25)

Rotate 2-3 of these per month:

Month 1: Questions 4, 8, 17 (Trust, Workload, Belonging)
Month 2: Questions 1, 12, 18 (Flight Risk, Growth, Transparency)
Month 3: Questions 5, 9, 16 (Manager Feedback, After-Hours Pressure, Belonging)
Month 4: Questions 2, 13, 10 (Feeling Valued, Career Conversations, Resources)
Month 5: Questions 7, 14, 20 (Leadership Trust, Learning, Conflict)
Month 6: Questions 3, 11, 15, 19 (Compensation, Disconnect, Strengths, Pride)

After six months, cycle back to Month 1 and compare scores. The trends across two cycles tell you what's improving, what's declining, and what's stuck.

Want this full rotation calendar as a ready-made template? Join the StaffHero early access list to get the complete question bank with rotation schedule and red-flag thresholds when we launch.

Analyzing Responses Without an HR Team

If you're a founder reading 30-40 open-text responses every month, here's a quick analysis framework:

Read every response once. Don't analyze yet. Just absorb.
On the second pass, tag themes. Workload. Management. Growth. Communication. Compensation. Use whatever categories emerge naturally.
Count the themes. If 8 out of 30 responses mention workload, that's your signal. One mention is noise. Three is a pattern. Eight is a mandate.
Cross-reference with the numbers. Did the workload question (Q8) also average below 5? Confirmation. The qual and quant agree. Act on it.
Identify the outlier. Is there one response that's dramatically different from the rest? Could be noise. Could be someone in a uniquely bad situation worth investigating.

If this analysis takes more than 30 minutes, you're over-thinking it. Or you could use StaffHero, which runs this analysis automatically with AI and delivers a one-page Founder Brief with the top themes, supporting quotes (anonymized), and recommended actions.

Net Promoter®, NPS®, NPS Prism®, and the NPS-related emoticons are registered trademarks of Bain & Company, Inc., NICE Systems, Inc., and Fred Reichheld. Net Promoter Score℠ and Net Promoter System℠ are service marks of Bain & Company, Inc., NICE Systems, Inc., and Fred Reichheld.