The biggest mistake candidates make when talking about their achievements.

By Rehearsa Team · 2026-10-12

You have delivered projects, solved problems, and helped your team succeed. Then an interviewer asks, “What achievement are you most proud of?” You describe the project, list everything you worked on, and finish with: “It went really well.”

The experience may be impressive. The answer does not yet show why.

The biggest mistake is describing what you did without making clear what changed because of your contribution. Candidates often present responsibilities as achievements, hide their decisions behind “we”, or quote a number without explaining its significance. The interviewer is left to guess what the story proves.

This guide shows you how to make that evidence visible without exaggerating, taking credit for other people's work, or turning your answer into a sales pitch.

Quick answer: how should you talk about an achievement?

Explain the problem, your specific contribution, and the outcome. Give enough context to show why the result mattered, then connect the example to the role you want.

A useful starting sentence is:

“I am proud of [achievement] because it changed [meaningful outcome]. My specific contribution was [decision or action], and we measured the result through [evidence].”

This is a preparation prompt, not a script to memorise. Replace it with language you would naturally use.

Why a list of activities is not enough

Compare these two statements:

• “I created reports, attended stakeholder meetings, and supported the launch.”
• “I identified that the launch report counted repeat users as new customers. I corrected the definition and added a validation check, so the team could make its launch decision using a reconciled customer count.”

The first shows involvement. The second shows judgement, ownership, and a useful outcome.

An achievement does not have to mean a dramatic revenue increase. Preventing an error, reducing rework, improving accessibility, helping a colleague become independent, or making a decision more reliable can all be meaningful achievements. What matters is that you can explain the difference you made.

For related problems, read 10 Common Interview Mistakes.

What interviewers may be assessing

Different employers use different criteria. There is no universal scoring formula, but achievement questions commonly help interviewers explore the following:

You do not need to announce every category in your answer. Choose a story that naturally contains the evidence.

A simple structure: problem → contribution → outcome → relevance

This is a compact way to prepare the same evidence covered by the STAR method.

1. State the problem and why it mattered

Give the interviewer a baseline. What was difficult, slow, unreliable, or missing? Who was affected?

Weak: “We had a reporting project.”

Stronger: “Our support leads used three spreadsheets to prepare the weekly review, and inconsistent definitions meant they spent time reconciling numbers instead of deciding what to improve.”

Keep this short. The answer is about your contribution, not the full history of the organisation.

2. Name your contribution and your decision

Be precise about what you owned. Explain one or two important actions and the reasoning behind them.

Weak: “I helped improve the process.”

Stronger: “I mapped the conflicting definitions with the support leads, agreed a shared definition of a resolved case, and built checks that flagged mismatches before the review.”

The decision is often the most revealing part of the answer. Why was that approach better than the alternatives?

3. Show the outcome with honest evidence

Explain what changed, over what period, and how you know. Numbers are helpful when they are accurate and meaningful. They are not mandatory.

Weak: “Everyone was happy with the result.”

Stronger: “The leads adopted the shared report for the next four weekly reviews, and the reconciliation issues recorded in our review notes stopped recurring during that period.”

If the result is early, say so. If the outcome belongs to a team, distinguish the team result from your contribution.

4. Explain why the story matters for this role

One sentence is enough:

“That experience is relevant here because your team needs someone who can turn inconsistent operational data into decisions people trust.”

Do not force a connection. Choose the right story in the first place. The Hiring Manager interview preparation guide can help you identify which evidence matters most.

Before-and-after examples

The examples below are fictional illustrations. Their figures are not benchmarks or claims about Rehearsa users. Use your own experience and only evidence you can defend.

Example 1: improving an operational process

Question: “What achievement are you most proud of?”

Weak answer:

“I managed the onboarding process. I arranged meetings, updated documents, and worked with different teams. We onboarded lots of customers and received positive feedback.”

Stronger model answer:

“I am proud of making customer onboarding more predictable. Customers were repeatedly asking who owned their next step, and handovers between sales and support were unclear. I owned the handover checklist and worked with both teams to agree named owners and a single status update. I piloted the checklist with ten customers before extending it. In that pilot, missed handovers fell from four in the previous comparable group of ten to one. That is a small sample, so I would not claim it proves a long-term reduction, but it gave us enough evidence to adopt the checklist and keep tracking it. My main contribution was turning an unclear handover into a process people could follow.”

Why it works: It gives a baseline, names the candidate's ownership, explains the pilot, and avoids treating a small sample as conclusive proof.

Prepare: Identify one process you improved and how you verified that the change helped.

Example 2: a product manager explaining a team outcome

Weak answer:

“I launched a new feature that increased activation by 20%. It was a big achievement for me.”

Stronger model answer:

“Our team improved onboarding completion from 40% to 48% in a controlled experiment. That is an eight-percentage-point increase, or a 20% relative increase. My responsibility was identifying the main drop-off point, working with design on the proposed change, and agreeing the experiment's success metric and support-related guardrail. Engineering delivered the implementation and our analyst checked the experiment results. The improvement held over the experiment period without a material increase in support contacts. I am proud of how we connected a user problem to a measurable decision, rather than launching a feature and assuming it helped.”

Why it works: It distinguishes percentages from percentage points, shares credit, and explains the candidate's judgement rather than only naming the outcome. In your own answer, be ready to explain the experiment design and remaining uncertainty.

Prepare: Practise the follow-up, “What did you personally own?” Use the Product Manager interview guide to build relevant stories.

Example 3: a graduate without commercial metrics

Weak answer:

“I got a good mark on a group project. I worked hard and helped everyone.”

Stronger model answer:

“I am proud of helping our four-person university team deliver a working prototype after we fell behind. I noticed that we were each building against different assumptions, so I proposed a shared requirements checklist and a short integration session twice a week. I owned the data import module and documented its inputs so the other members could test against it. We delivered the agreed prototype by the deadline and demonstrated all five required user flows. The grade was a team outcome; my contribution was reducing integration confusion and making my part easy for others to use. I learned that reliable handovers matter as much as finishing your own work.”

Why it works: It uses specific, verifiable evidence without inventing revenue, customer impact, or professional seniority.

Prepare: Look at coursework, volunteering, societies, part-time work, or personal projects. For more examples, browse Graduate Interview Questions.

Example 4: a technical achievement with an incomplete outcome

Weak answer:

“I redesigned a service to make it faster. It should save the company a lot of money.”

Stronger model answer:

“I am proud of improving a slow reporting endpoint. I profiled it and found that repeated database queries were the main bottleneck. I replaced those queries with a batched lookup and added regression tests. In our staging load test, the 95th-percentile response time fell from 1.8 seconds to 0.9 seconds at the same request volume. The change had not been released when I left the project, so I cannot claim a production or revenue outcome. The achievement I can evidence is identifying the bottleneck and delivering a tested improvement ready for release.”

Why it works: It separates measured test performance from an unverified business outcome.

Prepare: Know the environment, measurement method, and limits of any technical result you quote.

How to choose the right achievement

Start with the job description, not the biggest number on your CV.

• For an analytical role: choose evidence of sound reasoning, reliable data, or a better decision.
• For a leadership role: show how you enabled others, handled trade-offs, or improved team performance.
• For a customer-facing role: explain the customer problem and how you improved the experience.
• For a technical role: connect your implementation to reliability, usability, maintainability, or another relevant outcome.
• For an early-career role: show initiative, learning, collaboration, and dependable delivery at your actual level of responsibility.

Prepare two or three examples so you can answer different questions honestly. A story about rescuing a deadline is not always the best evidence of strategic thinking.

What if you do not have numbers?

Do not manufacture them. Look for other concrete evidence:

• A process was adopted and continued to be used.
• An error was detected before a release or customer communication.
• A deliverable passed agreed acceptance criteria.
• A stakeholder used your analysis to choose between options.
• A colleague could complete a task independently after your training.
• A recurring problem stopped appearing in documented reviews.

Separate observation from interpretation. “The team adopted the checklist” is an observable outcome. “It transformed company culture” is a much larger claim that needs much stronger evidence.

If you estimate a result, clearly label it as an estimate and explain the basis. If you cannot support it, leave it out.

Avoid these five follow-on mistakes

1. Using “we” so much that your contribution disappears

Use “we” for the shared result and “I” for your actions:

“We delivered the launch. I owned the customer research and used the findings to narrow the initial scope.”

That is clearer than either claiming the entire launch or making yourself invisible.

2. Quoting a result without its baseline

“Errors fell by 50%” could mean two errors became one. Give the actual counts, period, or scale when you can, and do not overstate what a small sample proves.

3. Treating sequence as proof of causation

If sales increased after your campaign, other changes may have contributed. Say “sales rose during the campaign period” unless you have evidence that supports a stronger causal claim.

4. Oversharing confidential information

Use permitted, anonymised details. You can describe a problem, your reasoning, and a directional outcome without naming a customer or disclosing commercially sensitive figures. Never invent replacement figures and present them as real.

5. Spending so long on context that the achievement gets rushed

As a practice target, try a first version of roughly 60–90 seconds, with more time on your actions and outcome than on the background. Follow the interviewer's format if they specify one, then leave space for follow-up questions.

Prepare for the follow-up questions

A polished opening answer is not enough if it falls apart when the interviewer probes. Be ready for:

• “What did you personally contribute?”
• “How did you measure the result?”
• “Why did you choose that approach?”
• “What was the hardest trade-off?”
• “Who else contributed?”
• “What would you do differently?”

Write brief evidence notes, not memorised paragraphs. If you do not know a detail, say so rather than improvising a figure. Browse Hiring Manager Interview Questions for further practice.

A seven-day preparation plan

Short on time? Choose one relevant story, check the evidence, and rehearse the answer and two follow-ups. Quality is more useful than a large bank of vague examples.

Final checklist

Before your next interview, ask yourself:

• Did I explain why the problem mattered?
• Can the interviewer identify my specific contribution?
• Did I explain at least one decision, not just an activity?
• Is the result concrete and accurately described?
• Have I separated team credit from personal ownership?
• Have I acknowledged any limits or uncertainty?
• Does this story demonstrate something relevant to the role?
• Can I answer follow-up questions without inventing details?

The goal is not to make your achievement sound bigger. It is to make its value easier to understand.

Put your achievement story into practice

Reading a strong answer and delivering your own are different skills. Use Rehearsa Interview Practice to rehearse aloud and review how clearly you explain your contribution and result. Your evidence still needs to come from your own experience.

Start a free Rehearsa trial, or compare plans before choosing your next practice session. For more preparation, explore the Interview Mistakes collection and the complete STAR method guide.

More Interview Mistakes guides · Start free trial