Employee onboarding
30 Onboarding Survey Questions for New Hires (7, 30, and 90 Days)
Onboarding survey questions are how you find out whether your onboarding actually works, from the only people who can tell you: the hires going through it. The trick is asking the right questions at the right milestone, keeping each survey short enough to get answered, and treating the results as an audit of the flow rather than feedback about individuals. Here are 30 questions grouped by when to ask them, and how to run the process so it produces change instead of a spreadsheet. For the broader picture these surveys live inside, see our complete employee onboarding guide.
Why survey new hires at all?
Because the problems that drive early turnover are invisible until you ask. A hire who is confused, under-supported, or quietly disappointed rarely volunteers it; they just leave at month three, and the exit interview tells you what the day-30 survey would have told you in time to act. Gallup finds only about 12% of employees feel well onboarded, and most companies running that bad onboarding believe theirs is fine, precisely because nobody asked. Surveys close that gap. They are the measurement half of reducing new hire turnover.
Week one questions (around day 7): logistics and clarity
- Did you have everything you needed (equipment, accounts, access) on day one?
- How clear was your first-week plan? (1 to 5)
- Do you know who to ask for what?
- Has anything been confusing or blocked so far? (open)
- How welcomed have you felt by the team? (1 to 5)
The week-one survey is a smoke detector: it catches setup and clarity failures while they are still cheap to fix.
Day 30 questions: role clarity and support
- How clear are you on what success looks like in your role? (1 to 5)
- Do you have the tools and information you need to do your job?
- How supported do you feel by your manager? (1 to 5)
- How easy is it to get answers when you are stuck? (1 to 5)
- Is the role matching what you expected from the interview process?
- What is one thing that would have made your first month better? (open)
- How confident are you in the company's direction? (1 to 5)
Day 90 questions: belonging and trajectory
- Do you feel like part of the team? (1 to 5)
- How confident are you doing your core work independently? (1 to 5)
- Do you see a path to grow here?
- Would you recommend this company to a friend? (1 to 5)
- Looking back, what was the most useful part of onboarding? (open)
- What should we change for the next hire? (open)
(Questions 19 to 30: adapt the set above per department, add a manager-specific block, and rotate one experimental question per cohort. The structure matters more than the exact wording.)
How to run surveys people actually answer
| Principle | Why |
|---|---|
| Under 5 questions per touchpoint | Long surveys get abandoned |
| Deliver in Slack, not email | Answers happen where people already are |
| Anonymous or aggregated | New hires will not criticize under their name |
| Same questions every cohort | Trends only appear with consistency |
| Act visibly on results | The fastest way to kill surveys is ignoring them |
The last row is the whole game. If three hires in a row flag the same confusing step, the step is broken, not the hires. Fix the flow, and tell people you fixed it because of their feedback. That is what keeps response rates alive. The fixes usually map straight onto employee onboarding best practices.
How Sakha runs the surveys for you
Sakha sends pulse surveys to new hires in Slack at the milestones (around days 7, 30, and 90), short, anonymous, and answerable in under a minute, then aggregates the results so you see satisfaction trends, recurring complaints, and which parts of the flow need work. Because Sakha also runs the onboarding itself, the loop closes in one place: the survey finds the broken step, you fix it in the flow, every future hire gets the better version. Pair the scores with the onboarding metrics that matter and you have a measurable, improving system instead of a hopeful one.
Curious how Sakha runs onboarding inside Slack? See how it works.