The Company Survey Asks About the Company. This One Asks About the Job.
Organization-level surveys produce organization-level answers — culture, leadership, direction — and then hand them to managers who can change none of it. Job satisfaction sits one level down, where the actionable lives: does the work match the title, does the week contain too much of what nobody was hired for, is the trajectory real, does the pay feel fair. These are questions a manager can act on this quarter, which is why this instrument belongs to the manager-and-HR pair rather than to the board deck.
Run it twice a year, or whenever the job itself changes — new responsibilities, a restructured team, a promotion in place. The trigger that matters most: after the job has quietly drifted from the one the employee accepted.
What the Job Level Actually Measures
- Role clarity. Do you know exactly what is expected of you? A yes/no item — and the percentage of no answers in a team is usually the single most alarming number in the whole survey.
- Task fit. A number question: what share of your week is spent on the work you were actually hired to do? Answers below half point at either a role problem or a staffing one — both worth knowing precisely.
- Growth trajectory. An opinion scale on whether the job is moving somewhere: skills, scope, or level.
- Pay fairness, carefully framed. Never ask for figures — ask for the perception: does your compensation feel fair for the work you do? Fairness perception predicts job-seeking better than any benchmark, and the question stays answerable everywhere.
- Enablement. Does the role come with the tools, access, and information to do it well?
- Manager support, in role context. Not rate-your-manager — narrower and more useful: when you hit a blocker in your actual work, does help arrive?
- One open field: what single change would make this job better? Job-level suggestions are famously concrete: a second monitor, an approval removed, one recurring meeting deleted.
The Read Belongs at Team Level
Results land with the manager and their HR partner as a team picture: clarity gaps, task-fit distributions, the growth scores that quietly explain an unexpectedly good resignation. Individual answers stay out of the manager’s view — the pattern is the instrument’s product, not the person. Where job-level dissatisfaction repeats across teams, it is no longer a manager topic; it graduates to the org-level instruments in the human-resources surveys collection. Role-change moments pair naturally with the performance review cycle, and the response archive keeps each half-year comparable.
Frequently Asked Questions
How is job satisfaction different from engagement?
Engagement measures the relationship with the company — mission, pride, intent to stay. Job satisfaction measures the fit of the work itself. People can love the company and hate the job; the two findings demand opposite interventions.
Will my manager see my individual answers?
No — managers see team-level patterns only. The moment individual answers reach the person being rated, the instrument measures diplomacy instead of fit.
Should we run it for the whole company at once?
Teams can run on their own cycle — after restructures, role changes, or at review time — which is this survey’s natural rhythm. A synchronized company-wide run adds comparability, if the calendar can wait for everyone’s trigger.
Is the pay question safe to ask?
Framed as fairness perception, it is both safe and the most predictive pay-related question available. It never asks for figures, and its answers route to HR’s compensation review rather than into team meetings.