What Is Your Greatest Accomplishment? How to Answer, With a Scored Example

14 min read

Updated October 8, 2026·Originally published October 8, 2026

Answer 'what is your greatest accomplishment' with Stakes–Moves–Proof–Point: pick the story, own your part, end on a line worth repeating. Scored 22 vs 88.

To answer "what is your greatest accomplishment," pick one specific, recent result that relates to the job, and tell it in four beats: the stakes (what was wrong or at risk, in one or two sentences), your moves (two to four things you personally did, in "I" language), the proof (what changed, with a number or an honest approximation), and the point (one closing sentence that says what the story shows). Keep it to about 90 seconds spoken. On a team win, say which part was yours. Do not end on how your manager felt or on a bare fact; end on the point, so the interviewer has one sentence that sums up the story.

The rest of this guide names that four-beat structure, shows how to choose the accomplishment (including how to handle team credit), gives worked examples for five roles including an early-career candidate, lists the mistakes that sink the answer, and shows a weak example answer we wrote and our rewrite, both scored by the Interview Drills scorer.

What is the interviewer actually asking?

"What is your greatest accomplishment?" asks two things at once: what you count as success, and how you get results. The accomplishment you choose shows your values; the way you tell it shows whether you can describe your own decisions clearly.

Published guidance agrees on the first part. The Muse (updated December 23, 2024) puts it this way: "Your choice of greatest achievement will show the interviewer what you consider important," and "They can also get a read on your definition of success." Resume Genius (updated May 28, 2026) says interviewers ask "to understand what parts of your work are most important to you."

The second part is the one candidates miss. The question is a behavioral question in disguise: it does not say "tell me about a time," but it asks for a story, and it is judged like one. The Interview Drills practice scenario for this question ("Your Proudest Accomplishment") is filed under behavioral questions and scored against the STAR structure: situation, your responsibility, your actions, and the result.

The question arrives in several forms, and the same answer works for all of them:

• "What is your greatest accomplishment?"
• "What's your proudest professional achievement?"
• "Tell me about an accomplishment you're proud of."
• "What are you most proud of in your career so far?"

The Stakes–Moves–Proof–Point structure

Stakes–Moves–Proof–Point is Interview Drills' name for a four-beat accomplishment answer: what was at stake, what you did, what changed, and the one sentence you want repeated. It is STAR with the ending made explicit. It is coaching advice, not research data.

The Point beat is the reason this structure exists. The Interview Drills coach note for this question, written into the app's practice scenario, says: "The close is the sentence that gets repeated to the hiring committee, so do not end on a fact; end on the point." An answer that stops at the Proof ("tickets fell by half") leaves the interviewer to work out what it means. An answer that adds one Point sentence ("the fastest support answer is the one a customer never has to ask for") hands them the line to write down.

How to write each beat:

• Stakes. One or two sentences. Include the size of the problem ("about four hundred a month," "two-day response times") and, if it was not obviously your job, why you took it on. The Interview Drills scorer flagged exactly that gap in our own rewrite below (first run).
• Moves. Verbs that start with "I": "I proposed," "I wrote," "I tracked." Each move should be a decision someone else might not have made. Activities with no reasoning sound like a job description.
• Proof. A before-and-after. If you don't know the exact figure, say "roughly" and mean it. An invented precise number does not survive the follow-up "how did you measure that?"
• Point. One sentence, stated as a principle you would apply again, not a feeling. "It was a great feeling" is a feeling. "I learned to fix the question before staffing the answer" is a point. If you want to connect it to the job, add one short clause: "and that's the kind of problem this team is hiring for."

The Point is the line most worth memorizing word for word. Everything before it should be practiced as bullets, not sentences, so it survives an interruption.

How do you choose which accomplishment to talk about?

Choose the accomplishment that is recent, relevant to this job, clearly yours, and backed by evidence — not the one that sounds biggest. A smaller win you can explain decision by decision beats a large one where your part is unclear.

Run each candidate story through five checks:

If two stories pass, pick the one closer to the job's main need. If none passes all five, the Yours check is the one not to compromise on: an answer can survive an approximate number, but not an invisible role.

How do you take credit for a team accomplishment?

Name the team result once, then switch to "I" for the part you owned, and say in a few words who did the rest. That last part sounds like modesty, but it is what makes your claim believable: when you say what the engineer did, the interviewer can trust that the rest was you.

Two rules keep this honest. First, never claim the whole result if you owned a slice of it — follow-up questions about the part you didn't do can expose the gap. Second, don't shrink a real contribution into "we" to sound humble. The interviewer is not hiring your former team.

Does it have to be a work accomplishment?

A work or school accomplishment is the safer choice, because it is easier to connect to the job. A personal accomplishment can work if it shows a skill the role needs and you can tell it with the same detail — what you decided, what changed — and connect it to the job in the Point. If the interviewer asks for your greatest personal accomplishment, answer that question, and still end on what it shows about how you work.

What does a strong answer sound like in different roles?

A strong answer has the same four beats in every role; what changes is where the stakes and the proof come from. The five examples below are illustrative answers written for this article. The people, settings, and numbers are fictional, and no real employer is described. They are written shorter than a full 90-second spoken answer; aloud, the extra time goes into the Moves.

Early-career: student or recent graduate

An early-career candidate's accomplishment can come from a part-time job, an internship, a class project, or a club. The size of the win matters less than a clear decision and a before-and-after.

"I worked the front desk at my university's tutoring center, and every exam week the walk-in line ran past an hour while tutors sat idle in the afternoons. I pulled two semesters of sign-in sheets and saw that almost all the demand came in a three-hour evening window. I proposed moving two afternoon shifts to evenings, built a simple booking form so students could reserve a slot, and texted reminders the day before. That semester the longest wait during exam week dropped to about twenty minutes, and the director kept the schedule the next year. What it taught me is to check the data we already collect before asking for more staff."

Why it works: the stakes have a number, the moves are three of the candidate's own decisions, the proof is an honest approximation plus a sign it lasted (the schedule was kept), and the last line is a principle, not a feeling.

Registered nurse

A clinical accomplishment should show judgment and a change in how the unit works, not only a hard shift survived.

"On my medical-surgical unit, handoffs at shift change kept missing pending lab results, and twice in one month a result sat unreviewed for hours. I drafted a one-page handoff checklist with a pending-results line, piloted it with the four nurses on my rotation for two weeks, and adjusted it after their feedback before our manager rolled it out to the unit. In the next three months we had no missed pending results at handoff that I'm aware of. The point I took from it: a safety fix has to be easier than the old habit, or nobody uses it."

Why it works: it credits the manager for the rollout and keeps the pilot and the design as the nurse's own; it states the proof carefully ("that I'm aware of") instead of overclaiming.

Software engineer

An engineering accomplishment should name the problem in business terms before the technical moves, so a non-engineer on the panel can follow it.

"Our nightly data export failed about once a week, and each failure meant the finance team started the day without numbers. I traced the failures to one job that retried forever on bad input, so I split it into smaller batches, added a dead-letter queue for records that failed validation, and wrote an alert that named the bad record instead of just saying the job failed. Over the next quarter the export failed twice, and both times finance had their numbers by mid-morning. It taught me to make failures specific — a precise alert fixes more than a clever retry."

Account manager

A sales or account accomplishment should show the moves behind the number, not only the number.

"Last year one of my largest accounts told us they were evaluating a competitor at renewal. I asked for a meeting with their operations lead rather than the buyer, because the complaints in their support tickets were about setup, not price. I mapped their five biggest setup problems, brought in our implementation team to fix three of them within a month, and sent a short written update every two weeks until renewal. They renewed for two years and added a second team. What I'd repeat: find the person who feels the problem, not just the person who signs."

First-time team lead

A manager's accomplishment is the hardest place to separate "I" from "we," because the team did the work. Make your moves the decisions only a lead could make.

"When I became lead of a five-person support team, our backlog had grown to around three hundred open tickets. I stopped assigning tickets by who was free and set up queues by product area, so each person built depth in one area. I took the oldest fifty tickets myself for the first two weeks so the team could start clean on their queues, and I ran a fifteen-minute review every Friday to move people where the backlog was growing. Within six weeks the backlog was under fifty, and it stayed there. The team closed those tickets; my contribution was the system. The point for me: before asking people to work faster, check how the work reaches them."

Why it works: "The team closed those tickets; my contribution was the system" draws the credit line in one sentence.

What mistakes sink an accomplishment answer?

The mistake to fix first is a hidden role — a team result with your part left vague. The others are hedging the opening, ending on a reaction instead of a result, and choosing a story that doesn't fit the job.

Three of these — claiming too many accomplishments, embellishing your part, and tying the accomplishment to a salary or bonus — appear on Novorésumé's list of answers to avoid (updated February 24, 2026). Three others in the table — the hidden role, the hedged opening, and the reaction as result — are what the scorer flagged on its first run of the weak example below, along with a missing Action.

What a scored answer actually looks like

A vague team-effort answer scored 22 out of 100 on all three runs, and a rewrite built on Stakes–Moves–Proof–Point scored 88 on all three runs. We wrote both answers as examples (they are not from users) and typed them into the Interview Drills scorer — the same prompts, model, and scoring schema the app uses for its "Your Proudest Accomplishment" practice scenario, in typed-answer mode — and scored each one three times on October 8, 2026. Typed answers carry no voice signal, so Delivery here judges how the text reads; spoken answers are also measured for pace, filler words, and pauses.

Answer (first take, typed):

"I'd say I'm really proud of a lot of things. Probably the biggest is that I helped my team hit our targets last year, which was a big team effort. We all worked really hard and I contributed a lot to that. It was a great feeling to see everything come together, and my manager was really happy with the results."

Overall score: 22 / 100 on all three runs. First run:

• Clarity 28 · Confidence 30 · Structure 18
• Conciseness 42 · Delivery 35 · Audience awareness 20

What the scorer flagged (first run, condensed):

• "We all worked really hard and I contributed a lot to that" hides your role; replace it with one concrete thing you specifically owned
• No quantified result: "my manager was really happy" is a feeling, not a result — replace it with a number
• "I'd say I'm really proud of a lot of things. Probably the biggest is…" signals you're choosing your answer in real time; open directly on the accomplishment
• The Action is missing: it should be half the answer or more, with the specific decisions and steps you took

Our rewrite (written by us, specific and owned, then scored the same way: 88 on all three runs):

"Last year our support team was answering billing questions by hand, about four hundred a month, and response times had slipped to two days. I proposed a self-serve billing page, wrote the content for the twelve most common questions, and worked with one engineer to add it inside the app. I tracked the questions weekly and rewrote the three pages people still contacted us about. Within three months billing tickets fell by roughly half and response times got back under a day. What I took from it is that the fastest support answer is the one a customer never has to ask for."

First run of the rewrite:

• Clarity 92 · Confidence 90 · Structure 87
• Conciseness 91 · Delivery 88 · Audience awareness 84

The rewrite is Stakes–Moves–Proof–Point in order: the stakes have two numbers (four hundred a month, two days), the moves are four "I" decisions, the proof is an honest "roughly half," and the last sentence is a point, not a fact. The changes are ownership and specificity, not polish: the hedges disappeared because there was no longer anything vague to hedge.

Even at 88, the first run listed four improvements, and the first two match the Stakes and team-credit advice above:

• No sentence says why this was the candidate's problem to solve — "I proposed" doesn't tell the interviewer whether it was assigned or spotted
• "Worked with one engineer" leaves the split of work unclear; say what you did and what the engineer did
• The opening states the facts but creates no tension
• The closing line is strong but doesn't connect the story to the role being hired for

One note on length: the rewrite is 103 words, which is about 40 to 50 seconds at a conversational pace of 125 to 150 words per minute (the range used in our guide to how long interview answers should be). The 90-second target leaves room for the Task sentence and the engineer's role the scorer asked for, without padding.

How is this different from "what are your strengths" or "tell me about a time you failed"?

"What is your greatest accomplishment" asks for one result and the story behind it; "what are your strengths" asks for a quality, with a result as proof; "tell me about a time you failed" asks for a mistake you owned and what you changed. The same story can serve more than one of them, but the beat you lead with changes.

If you used your best story for the strengths question earlier in the interview, tell a different one here, or refer back to it briefly and add the part you didn't cover. Repeating the same story in full in one conversation signals a thin set of examples. Building six to eight stories ahead of time avoids that; the method is in how to build an interview story bank.

What follow-up questions should you expect?

Expect follow-ups that test whether the story is really yours: "What was your specific role?", "How did you measure that?", and "What would you do differently?" Each is easy if the story is true and you prepared bullets rather than a script.

• "What was your specific role?" Restate the credit line from your answer, then add one detail you left out.
• "How did you measure that?" Name the source ("our ticket system's monthly report") and say whether the number is exact or approximate.
• "What would you do differently?" Name one real decision you'd change — a step you'd start sooner or a person you'd involve earlier. "Nothing" makes the story sound too perfect.

How do you practice this answer?

Write the four beats as five bullets — stakes, two moves, proof, and the Point sentence in full — then say the answer aloud two or three times in different words, keeping only the Point sentence fixed. Time one take: aim for about 90 seconds, and if you pass two minutes, cut the stakes before you cut the moves.

Listen back for three things: whether the first sentence is a hedge, whether any "we" sentence hides what you did, and whether the last sentence is a point or just a fact.

Interview Drills is an AI-powered interview training platform designed for people who have a real interview coming up. It diagnoses interview weaknesses with a free 3-minute quiz, prescribes a 14-day training track of practice drills, scores spoken answers on six dimensions in under 60 seconds, and, on the Interview Accelerator and Interview Pro plans, feeds the candidate's resume into scoring and feedback.

If you are not sure which part of your interviewing needs work, the free 3-minute quiz (25 questions, no account needed) identifies your interview persona and blind spot.

Frequently asked questions

What is a good answer to 'what is your greatest accomplishment'?

A good answer is one specific, recent, job-relevant result told as a short story: what was at stake, the two to four things you personally did, the evidence that it worked (a number or an honest approximation), and a final sentence that states the point of the story. It should take about 90 seconds spoken and be about your actions, not your team's effort or your manager's reaction.

Can I talk about a team accomplishment?

Yes, as long as the interviewer can tell exactly which part was yours. Name the team result once, then switch to 'I' for the part you owned and say who did the rest: 'I wrote the content and scoped it; one engineer built it.' An answer that says 'we worked really hard and I contributed a lot' leaves your role invisible, which is the one thing the question is trying to find out.

What if I'm early in my career and have no big accomplishment?

Use the most job-like thing you have actually done: a part-time job, an internship, a class project, a club, or volunteer work. The size of the win matters less than whether you can show a decision you made and what changed because of it. A fixed schedule at a campus job, told with a before-and-after, is a stronger answer than a vague claim about a large project.

Should I pick a personal or a professional accomplishment?

Pick a professional or academic one unless the personal one shows a skill the job needs and you can tell it with the same detail. The Muse's guidance makes the same call: choose a professional accomplishment unless a personal accomplishment is especially relevant to the role. A personal milestone like a marathon can work for a role where discipline is the point, but you still need to connect it to the job in your last sentence.

How long should my answer be?

About 90 seconds spoken, and no more than two minutes. The Interview Drills practice scenario for this question targets 90 seconds. Spend the largest share on what you personally did, keep the setup to one or two sentences, and plan your last sentence before you start so the answer ends on purpose instead of fading out.

Is 'what are you most proud of' the same question?

Close enough to use the same story. 'Greatest accomplishment' leans toward the size of the result; 'most proud of' also invites why it mattered to you. With the Stakes–Moves–Proof–Point structure, the Point line covers both: it states what changed and why you would do it again. If the interviewer adds 'outside of work,' they are asking for a personal one.

What should I avoid when answering this question?

Avoid saying you have too many accomplishments to choose one, avoid exaggerating your part, and avoid making a salary or bonus the accomplishment itself; Novorésumé lists all three as answers to avoid. Also avoid ending on someone else's feelings ('my manager was really happy'), because a reaction is not a result.