What is a good answer to an interview question about being proactive

One where you can account for the hours. Unasked work always comes out of committed work, and the candidates who are genuinely good at this either cleared it first or can say precisely what slipped. An answer where the initiative appears to have cost nothing invites an interviewer to assume the cost landed on somebody else.

Should I mention that someone told me not to do it

Yes, if it happened, and it often did in some form. Describing how you interpreted the instruction, and admitting if you interpreted it conveniently, is far stronger than a clean story. Hiring managers are deciding how you behave under a no, and a candidate who has never received one has not been tested.

Is taking initiative without permission a red flag

Only when it comes with no awareness of the trade. Doing a rough version first and asking for a week reads as judgment, doing the finished version and presenting it reads as a manager having to react. Show that you know the difference and the same story becomes an asset.

Tell Me About a Time You Took Initiative

Why interviewers ask this

When an interviewer says tell me about a time you took initiative, what they are testing is not whether you are willing to do unasked work. Almost everybody is, at least once, and the stories are interchangeable. What they want to establish is whether your initiative is something a manager would have to spend time containing. Unasked work is a claim on hours that belonged to somebody's plan, and the people who are genuinely valuable at it check the claim first. The people who are exhausting do the thing, do it well, and present it finished. That leaves a manager choosing between adopting something they never scoped and being the person who says no to enthusiasm, and both of those cost more than the work saved.

An answer that sounds fine

Our support team was fielding the same questions about billing over and over, and nobody had time to work out how often, because the ticket categories were too coarse to tell us anything useful. Nobody asked me to look at it. I spent a few evenings pulling six months of ticket text, tagged the top recurring themes by hand, and built a simple dashboard showing volume by theme over time. Billing questions were nearly a third of everything. I brought it to our operations lead, we rewrote three help articles off the back of it, and billing tickets dropped by about twenty percent over the next quarter. It is a good example of me being proactive rather than waiting to be told.

Where it breaks

Nobody asked me to look at it appears in the second sentence and is presented as the virtue of the story. It is also the only fact in the account that carries any risk, and the answer never returns to it. A few evenings is doing quiet work as well, because evenings are the socially acceptable way of saying this cost nothing, and unasked analysis of six months of ticket text does not fit into a few evenings unless something else moved. There is a third thing, subtler than either. The operations lead had presumably not prioritised this, and the story never asks why. Most interview question about initiative answers are built exactly this way, with the absence of permission framed as the achievement, and an interviewer who has managed people hears somebody describing work they would have had to react to rather than work they asked for.

The follow-up

What happened to the thing you did not do while you did this, and did anyone tell you not to?

My own queue slipped, so my average response time went from about four hours to nearly a day for that fortnight, which my team lead did notice. And yes, sort of. She had said a month earlier that ticket categorisation was not a priority this quarter and to leave it. I did not think of what I did as the same thing, because I was not changing the categories, I was analysing the text. Which, looking at it now, was the same project with a different name.

That last sentence is the whole interview. He had been told directly that this area was not a priority, and he reframed the work narrowly enough that he could tell himself the instruction did not apply. That is an extremely common move and it is not dishonest, it is how people who care about a problem talk themselves past an inconvenient decision. He also let his own response times double for a fortnight and his team lead absorbed the complaints. The dashboard was genuinely useful and none of that changes. What a hiring manager now knows is the shape of this person under a no, which is information they were never going to get from the prepared version and which they will need within a month of him starting.

An answer that holds up

Our billing help content was generating repeat tickets and I could not prove it, because our categories were too coarse. My team lead had told me a month earlier that ticket categorisation was not a priority for the quarter. I did the analysis anyway, over about two weeks of evenings and some borrowed afternoons, and my own response times went from four hours to nearly a day while I did it. I told myself I was analysing text rather than changing categories, which was a distinction I invented for my own benefit. The dashboard showed billing at a third of volume, we rewrote three articles, and tickets fell about twenty percent. If I ran it again I would take one afternoon, do a rough sample of two hundred tickets, and bring her the estimate to ask for a week, because the case would have been just as strong and she would have been in it from the start rather than presented with it.

The interviewer asks whether anyone told him not to.

My team lead did, a month earlier, and I decided her instruction was about something narrower than it was. She was pleased with the result when she saw it. She was reasonably annoyed about the route I took to get there, and she was right to be.

Practice this question

Say your answer to this question out loud, then get asked whether anyone told you not to. Answer it now, free, no account.