Why interviewers ask this

Companies say they want people who challenge the status quo, but what they are actually screening for is judgment about which battles are worth fighting and how to raise a challenge without burning trust. This question separates candidates who genuinely notice inefficiency and act on it from those who simply comply with whatever exists. It also reveals how you handle the risk of being wrong, since challenging an accepted practice always carries some social and professional exposure.

How to structure a strong answer

Describe the existing practice plainly and why it had persisted, often it is not that people were careless, it is that nobody had revisited it in years. Explain what specifically prompted you to question it and the evidence you gathered before raising it, since a challenge backed by data lands very differently from a challenge based on a hunch. Close with how you actually proposed the change and what resulted, including any resistance you had to work through.

Example answer

At my previous company, every new hire's laptop had to be manually configured by an IT technician, a process that had been in place for years and typically took two full days per employee. When we started hiring faster, I noticed this was consistently delaying new hires' first productive day, so I timed the process for three separate onboardings and found that roughly 70 percent of the steps were identical across every role. I put together a proposal for a standard imaging script covering those common steps, with technician time reserved only for role-specific software, and presented it with the time data to my manager and the IT lead who owned the process. There was some initial pushback since the manual process felt safer to the team, but after a two-week pilot showed zero setup issues and cut onboarding time to half a day, it became the new standard.

Common mistakes to avoid

Do not tell a story where you challenged something purely for the sake of being seen as innovative, without a real problem behind it. Avoid framing it as you unilaterally changing something without buy-in from the people who owned the process, since that reads as overstepping rather than leadership. Also make sure the story includes actual resistance or friction, a challenge nobody pushed back on rarely demonstrates much skill.

Get real-time help in your next interview
Live Interview Help listens to your interview and surfaces personalised answers in real time. Free 20-minute trial on Google Meet, Teams, and Zoom.
Install Free on Chrome
Check your CV against the job description first
Free AI-powered CV Match Check scores your CV against any job description: missing keywords, weak impact metrics, and ATS parsing risk, before you even apply.
Check My CV Free

Frequently asked questions

What if my challenge to the status quo did not succeed?
That can still be a strong answer if you show good reasoning and a professional response to being told no. Explain what you learned about the constraints you had not considered, since that shows maturity rather than stubbornness.
How do I avoid sounding like I think my previous employer did everything wrong?
Frame the existing process neutrally, as something that made sense at the time or under different conditions, rather than as an obvious mistake. This keeps the story about your judgment rather than about criticizing former colleagues.

Before your next interview, it helps to have the fundamentals down. Our complete guide to preparing for a job interview covers the basics, and the STAR method is a reliable way to structure almost any answer under pressure.

Try an AI mock interview free
A real voice interviewer that questions you, drills into weak spots, and scores your answers, grounded in your actual CV and the job description.
Try a Mock Interview Free