How to Answer "What Is Your Greatest Accomplishment?"

To answer "What is your greatest accomplishment?", pick one recent, work-related result that shows a skill the new job needs, explain the problem in a sentence or two, spend most of your answer on what you personally did and why, then state the outcome and link it to the role. The interviewer is not grading the size of the win. They are learning what you count as success, how you think, and whether you can explain your own work clearly.

What the interviewer is really asking

This question sounds open-ended, but it is doing several jobs at once. Knowing them helps you choose the right story.

• What you value. The accomplishment you choose signals what you consider important: saving money, helping a customer, shipping on time, building something new, fixing something broken.
• How you work. The middle of your answer shows your process: how you spotted the problem, weighed options and got other people on board.
• Whether you can own results. Interviewers listen for the difference between "I was there when it happened" and "I made this happen."
• How you talk about yourself. They want confidence without exaggeration, and credit for others without hiding your own role.

If you treat it as a chance to show those four things, the answer almost writes itself. If you treat it as a chance to list your best numbers, it tends to sound like a resume read aloud.

How to choose the right accomplishment

Most people default to the biggest thing they have done. A better approach is to pick the most relevant thing. Before the interview, write down three or four candidates and test each one against these filters.

Relevance to the job

Read the job description and pick out the two or three problems this role exists to solve. An accomplishment that shows you solving a similar problem is worth more than a bigger win in an unrelated area. If the posting stresses improving onboarding, a story about cutting new-hire ramp-up time beats a story about winning an award for something else. This is the same matching you would do when you tailor your resume to a job description, applied to a spoken answer.

Recency

A result from the last few years shows your current level. An older story is fine if it is clearly your strongest and most relevant, but be ready for "What have you done more recently?"

Your share of the credit

Choose something where your decisions changed the outcome. If you were one of twelve people on a project, it can still work, but only if you can point to a part that was yours.

A story with friction

The best accomplishments include an obstacle: a tight deadline, a skeptical stakeholder, missing data, a budget cut. Friction is what makes the story interesting and what shows your judgment. "I did my job well and it went fine" is not an accomplishment story.

Something you can discuss in depth

Expect follow-up questions. Pick a story where you remember the details, can explain why you made each choice, and would be comfortable if the interviewer asked what you would do differently.

A simple structure that keeps you under two minutes

The STAR method (situation, task, action, result) works well here, with two adjustments: keep the setup short, and add a closing line that connects the story to the new job.

• Context (about 15 seconds). Where you were, what was at stake, and what made it hard. One or two sentences.
• Your actions (about 60 seconds). Three or so specific things you did, in order, with the reasoning behind each. This is the heart of the answer.
• The result (about 15 seconds). What changed. Use a number if you have an accurate one; otherwise describe the change concretely.
• The bridge (about 10 seconds). Why it matters for this role: "That is the kind of problem I understand you are working on with..."

Here is an illustrative example for an operations coordinator applying to a logistics company. The details are invented to show the shape of a good answer:

"In my current role, our warehouse kept missing same-day shipping cutoffs because orders were picked in the sequence they arrived, not by deadline. I was asked to look into it. I spent a week logging where orders stalled, found that most delays came from a handful of rush orders sitting behind bulk ones, and proposed a simple priority tag in our order system. The floor leads were skeptical, so I ran it with one shift for two weeks and shared the results with them before asking to roll it out. After that we stopped missing cutoffs on most days, and the leads started suggesting their own tweaks. I am proudest of that last part, because the change stuck. Your posting mentions improving fulfillment speed, and that is exactly the kind of problem I like working on."

Notice what it does: a short setup, specific actions with reasons, a result described honestly, and a bridge to the job. It also shows persuasion, which is often what separates a good accomplishment from a great one.

What if you do not have a big number?

Many strong accomplishments do not come with a clean metric. You can still make the result concrete:

• Before and after. "Reports used to take two days to assemble; now they are ready the morning after month-end."
• Who noticed. "The client renewed and asked for me by name on the next project."
• What it unlocked. "Because the backlog was cleared, the team could finally start the migration that had been postponed twice."
• What it prevented. "We caught the error before the invoices went out."

If you want help turning fuzzy results into credible ones, our guide on how to quantify your resume when you don't have numbers covers honest estimation methods you can reuse out loud. Never invent a figure. If an interviewer asks how you measured it, you need a real answer.

Early-career and career-changer versions

If you are new to the workforce or changing fields, your best example may come from school, a side project, volunteering or a previous career. That is fine. What matters is that the skill transfers.

• Students and new graduates: a project where you organized people, met a hard deadline or taught yourself a tool. Be specific about your role in the group.
• Career changers: choose an accomplishment from your old field that uses a skill central to the new one, then name the skill explicitly in your bridge. A teacher moving into training design might describe rebuilding a curriculum that made a difficult unit easier for students, then point out that designing learning for adults uses the same process.
• Returning after a break: a recent accomplishment outside paid work (running a community event, managing a family project, finishing a certification) can show you are current, alongside a strong example from before the break.

Mistakes that weaken good answers

• Listing several wins. The question asks for one. Pick it and go deep. If the interviewer wants more, they will ask.
• Long setup, short action. If you spend a minute on background, you have little time left for the part that shows your skill.
• All "we", no "I". Credit the team, but make your role unmistakable.
• Repeating your resume bullet word for word. The interviewer has read it. Add the reasoning and the obstacle the bullet could not fit.
• False modesty. "It wasn't really a big deal" undercuts the whole answer. State what happened plainly and let the facts carry it.
• An accomplishment that raises a concern. A story about working every weekend for months may read as poor planning rather than dedication, depending on the employer.
• No bridge. Ending at the result leaves the interviewer to connect the dots. Do it for them in one sentence.

Handling the follow-up questions

A strong answer often invites deeper questions. Prepare short responses to these before the interview:

• "What was the hardest part?"
• "What would you do differently?"
• "How did others react?"
• "What did you learn that you still use?"

The "do differently" question is not a trap. A thoughtful answer, such as wishing you had involved a stakeholder earlier, shows self-awareness, which is the same quality interviewers look for when they ask you to talk about a time you failed.

A 20-minute prep worksheet

Do this once before your next interview and you will have an answer you can adapt for several questions, including "Why should we hire you?" and "Tell me about a time you went above and beyond."

• Step 1 (5 minutes): List four accomplishments from the last few years. Do not filter yet.
• Step 2 (5 minutes): Next to each, write which requirement in the job posting it matches. Cross out any that match nothing.
• Step 3 (5 minutes): For the best remaining one, write one line of context, three actions with a reason for each, one result line and one bridge line.
• Step 4 (5 minutes): Say it out loud twice and time it. Cut background until it fits under two minutes.

Keep your second-best accomplishment ready too. If an earlier answer already used your top story, you will want a fresh one. You can also reuse the same material in your answer to "Why should we hire you?" by summarizing the result in one line.

Bringing it together

The best answer to this question is not the most impressive one you can think of. It is the one that matches what the employer needs, shows how you think, and leaves the interviewer able to picture you solving their problem. Choose relevance over size, spend your time on your actions, describe results honestly, and finish with a clear link to the role. When your resume is tailored to each job, the right accomplishment is usually already sitting in your top bullets, ready to be told as a story.