How to answer "How do you define success?" — a definition you can prove

Most answers to this question are borrowed straight from a poster — "success is a journey, not a destination," or some version of "helping others succeed." They sound nice and reveal nothing, because they could come from anyone about anything. A real answer to this question is closer to a personal standard: the specific bar you actually hold your own work to, and evidence that you hold yourself to it.

Why interviewers ask it

This question is a quick way to check values (what do you actually optimize for — outcomes, growth, recognition, the work itself?), standards (is your bar for "good" high, low, or realistic?), and fit (does your definition line up with how this team measures its own work?). A team that defines success as shipping fast and iterating needs a different kind of person than one that defines it as getting things exactly right the first time — this question is a fast way to surface that alignment, or the lack of it, before an offer is made.

The framework: Standard → Evidence → Scope

1. Standard. State the actual bar you hold yourself to — not a platitude, a real criterion you use to judge your own work. Something specific enough that not everyone would define it the same way.
2. Evidence. A brief, real moment where that standard showed up — where you either met it and it mattered, or fell short of it and noticed.
3. Scope. How that personal standard fits the level or kind of work in front of you now — individual output, a team's outcome, or a customer's result, depending on where you are in your career.

The Evidence step is what turns a definition into a demonstrated standard rather than an assertion. Anyone can say "success means doing good work" — fewer can point to the specific moment that shows what "good" actually means to them in practice.

A worked example

"For me, success on a piece of work isn't just that it shipped — it's that six months later, nobody's had to go back and rebuild it because it didn't hold up. Early on I shipped something fast that technically worked, and it caused three separate follow-up fires over the next two months because I'd cut corners on edge cases to hit a date. That was the moment I recalibrated: fast and technically working isn't success if it just moves the real cost downstream. Now I measure a project's success less by the launch date and more by whether it's still quietly doing its job a few months later without anyone thinking about it — which is part of why I care so much about getting the foundational pieces right up front, even when it costs a little time now."

Standard (durability over speed, stated specifically) → Evidence (a real moment that shaped the standard) → Scope (tied to how the person actually approaches project work now). The definition is earned, not recited.

Adjusting the answer to your career stage

Earlier in a career, success is often reasonably defined around individual output and growth — did the work meet a real bar, did you learn something that changes how you'd do it next time. Further along, it tends to shift toward outcomes beyond your own hands — did the team succeed, did a decision you made hold up, did something you built or led outlast your direct involvement. Neither version is wrong; the mistake is describing team-level success when you've never actually had that kind of scope, or the reverse. The honest version, grounded in your actual experience so far, is the one worth telling — the same self-audit that helps answer "tell me about yourself" honestly rather than reaching for something that sounds more senior than it is.

Common mistakes to avoid

• A poster-quote answer. "Success is a journey" or similar platitudes say nothing specific about how you actually judge your own work.
• No evidence. A stated standard with nothing behind it is a claim, not a demonstrated value.
• Defining success purely by external recognition. "Success is getting promoted" or "being recognized" can read as more about status than the work itself.
• A definition that doesn't match the role's scope. Describing organization-wide impact for an individual-contributor role you've never held can sound like overreach.
• Too abstract to evaluate. A definition with no concrete criterion — nothing you could actually check against — leaves the interviewer with nothing to remember.

The bottom line

"How do you define success?" rewards a real, specific standard over an inspirational quote. Name the actual bar you hold your own work to, back it with a genuine moment that shaped it, and scope it honestly to your level of experience. That combination reads as someone who's actually thought about their own standards — not someone reciting the first definition that came to mind.

Related: Tell me about yourself · Do you have any questions for us? · Why should we hire you?