Interview questions

Interview questions for initiative: 14 questions, probes and a 1–4 scale

On this page
  1. Initiative, defined as something you can observe
  2. Ten behavioral questions, with follow-up probes
  3. Four situational questions
  4. What strong and weak answers sound like
  5. A 1–4 anchored rating scale for initiative
  6. Which roles need it most, and how much to weight it
  7. Common interviewer mistakes with initiative
  8. Questions people ask

Interview questions for initiative should find out whether a candidate acts on things nobody asked them to do, whether those things actually mattered, and whether they had the judgment to bring the right people along. Plenty of candidates can describe being "proactive"; fewer can name a problem they spotted, the specific action they took and what changed because of it. Below are fourteen questions, ten behavioral and four situational, each with follow-up probes, plus sample strong and weak answers, a 1–4 anchored scale and the mistakes that inflate this score.

Initiative is easy to confuse with its neighbors. Interview questions for work ethic cover diligence and follow-through on assigned work; this page is about unassigned work. And generating new ideas is its own skill, covered in interview questions for creativity. Initiative is the step after the idea: doing something about it.

Initiative, defined as something you can observe

Definition: initiative is spotting a problem or opportunity outside your assigned work and acting on it, within sensible limits, without waiting to be told. Four behaviors show it:

  • Noticing. Seeing a gap, recurring problem or opportunity that others were working around.
  • Acting, not only suggesting. Taking a concrete first step, even a small one, rather than just mentioning it.
  • Judging the boundary. Knowing what they could change themselves, what needed permission, and who needed to be told.
  • Picking what matters. Choosing things with real impact, not busywork that happened to be visible.

Ten behavioral questions, with follow-up probes

  1. Tell me about a problem you fixed that everyone else had been working around.
    Probes: How long had it been a problem? Why do you think no one had fixed it?
  2. Describe something you started at work that is still running without you.
    Probes: What did you do to make it last? Who owns it now?
  3. Tell me about a time you went ahead with something before you had formal approval.
    Probes: Why did you think that was acceptable? Who did you tell, and when?
  4. Tell me about an idea you raised that was not adopted.
    Probes: What did you do after the no? Would you raise it again?
  5. Describe a time you learned a skill or tool before your role required it.
    Probes: What made you think it would matter? How did it get used?
  6. Tell me about a time you noticed an opportunity, such as a customer need or a cost saving, that was outside your job description.
    Probes: What was the first concrete thing you did? What happened to your own work while you did it?
  7. Describe a time you took on a piece of work nobody wanted.
    Probes: Why did you take it? What did you ask for in return, if anything?
  8. Tell me about a time you started something and then stopped because it was not worth continuing.
    Probes: How did you decide? What did you tell the people who had been involved?
  9. Tell me about a time you asked for more responsibility.
    Probes: What exactly did you ask for? What did you do with it?
  10. Describe a time you took initiative and it caused a problem.
    Probes: What did you not see coming? What do you check now before acting?

Questions 3, 8 and 10 carry most of the judgment signal. A candidate with strong initiative but poor judgment will tell great stories to questions 1 and 6, then struggle with 10.

Four situational questions

  1. "In your first month, you notice our onboarding checklist is out of date and new starters keep asking the same questions. What do you do?"
    Probes: Who would you talk to first? What would you do if nobody seemed to own it?
  2. "Your manager is on leave for two weeks and a client asks for something you think we should do, but it's slightly outside what you normally handle. How do you respond?"
    Probes: What would you do yourself, and what would you wait on? How would you let the client know?
  3. "You finish your planned work for the week by Wednesday. What do you do with Thursday and Friday?"
    Probes: How would you choose between options? Who would you tell?
  4. "You spot a process in another team that is causing problems for yours. It isn't your process. What do you do?"
    Probes: What would you bring to that team? What if they don't prioritize it?

What strong and weak answers sound like

Illustrative answers to question 1, written to show the contrast.

Weak: "I'm a real self-starter. I'm always looking for ways to improve things, and I don't wait to be told. For example, I'm the one who organizes the team lunches and I set up a shared folder for our documents."

The weak answer offers self-description and two examples that are visible but low impact. There is no problem that was costing anyone anything, and no sense of what changed. It is not a bad sign, only a thin one; ask for something that affected results.

Strong: "Every Monday our recruiters spent about an hour reconciling interview schedules between the calendar and the ATS, and everyone just accepted it. I tried a shared calendar view that pulled from the ATS on my own desk for two weeks, checked it with the ops lead so I wasn't breaking anything, then showed the team. Three of five switched straight away. The Monday hour went down to about fifteen minutes, and the ops lead now maintains it."

The strong answer has a real, recurring cost, a small test before asking anyone to change, a check with the person who owned the system, a measurable result and a handover. That handover matters: it shows the candidate was improving the team's work, not building a personal project.

A 1–4 anchored rating scale for initiative

ScoreAnchor
1 — No evidence Examples are all assigned work. Describes noticing problems but waiting for someone else to act, or cannot name anything they started.
2 — Limited Suggested improvements or acted on small, low-impact things. Or took real action but without regard for who owned the area, creating friction they do not acknowledge.
3 — Solid Spotted a problem with real cost outside their brief, took a concrete first step, involved the right people, and can describe the result.
4 — Strong Everything at 3, plus chose the problem because of its impact, made the change last beyond their own involvement, and can describe a time they chose not to act and why.

Use the same scale across candidates at different levels, but adjust the scope you expect. A graduate who fixed a broken team checklist can earn a 3; a senior hire needs examples that changed how a team or function works. How to interview new graduates has more on getting usable evidence from candidates with short work histories.

Which roles need it most, and how much to weight it

Initiative is valuable almost everywhere, but it is not equally important everywhere, and weighting it the same for every role tends to favor confident self-promoters. Decide the weight before the interviews start:

Role typeWhat to look for
Early-stage companies and brand-new functionsWeight heavily. Look for candidates who built something from nothing and handed it over.
Senior individual contributorsWeight heavily. Look for problems they chose because of impact, not visibility.
People managersLook for initiative they created in others: a team member they encouraged to own a fix.
Regulated, safety-critical or tightly scripted rolesWeight lower. Look for raising problems early through the right channel, rather than changing things unilaterally.

Whatever weight you choose, write it on the scorecard before the first interview. Deciding it afterwards means the weight follows whichever candidate the panel already liked.

Common interviewer mistakes with initiative

  • Rewarding visibility over impact. Organizing social events and volunteering for committees are visible and pleasant. They are initiative only if they addressed a real problem.
  • Treating "I didn't ask permission" as a strength. Sometimes it is the right call; often it is a sign of poor judgment about ownership. Probe who else was affected.
  • Ignoring the cost to assigned work. Ask what happened to their normal work while they pursued the new thing. Initiative that consistently drops the day job is a mixed signal.
  • Penalizing people from structured environments. Someone from a regulated or tightly scripted role may have fewer dramatic examples. Ask about smaller scopes before concluding there is no evidence.
  • Confusing initiative with potential. Initiative is one input to potential, not the whole of it; how to interview for potential covers the rest. Score them separately so a strong initiative story does not inflate both.

If initiative is a core requirement, give it its own line on the scorecard with the anchors above; the scorecard builder will generate one. If it is a secondary requirement, one behavioral question with full probing is usually enough.

Questions people ask

What is the difference between initiative and work ethic?

Work ethic is about reliably doing the work you have been given, with care and follow-through. Initiative is about acting on something nobody asked you to do because you saw it mattered. A candidate can be extremely diligent and never step outside their brief, or full of new ideas and poor at finishing assigned work, so the two are worth scoring separately.

Is acting without permission a sign of strong initiative?

Not by itself. Strong initiative includes judging what you are allowed to change and who needs to know. Acting unilaterally on something with real risk, or that belonged to another team, is a judgment problem, even when the result was good. Ask who they told and when.

How do I assess initiative in candidates from very structured jobs?

Ask about smaller scopes: a checklist they improved, a recurring problem they flagged with a suggested fix, a skill they learned before it was required. Highly structured roles limit how much someone can change, but they rarely eliminate it, and noticing and proposing is still initiative.

Should I weight initiative heavily for every role?

No. It matters most where work is loosely defined, such as early-stage companies, new functions and senior individual contributor roles. In roles where consistency and following a set process are the point, weight it lower and look instead for people who raise problems through the right channel.