A stronger interview answer replaces broad claims with a specific situation, personal action and supported outcome. You do not need more dramatic language. You need enough detail for the listener to understand what you actually did.

This exercise improves a fictional answer about documenting a repeated setup problem. It is not a real candidate's story. Use the editing method with your own experience rather than adopting the sample as a personal claim.

What is weak about the first answer?

Fictional first draft: “I am proactive and a good team player. People had problems setting things up, so I helped everyone and made the process much better. The team was very happy.”

The answer contains conclusions but little evidence. We do not know what setup failed, which part the speaker owned, what they changed or how they checked the result. “Everyone” and “much better” are especially broad claims.

Which questions reveal the missing evidence?

  • What repeated problem did you observe?
  • What was your responsibility?
  • What did you personally change?
  • How did someone use or review the change?
  • What result can you honestly support?

These questions should recover real facts. If a detail is unknown, leave it unknown. Editing is not permission to create a metric or add praise that never happened.

What does a clearer version look like?

Fictional revised sample: “In a study project, two teammates could not run the local app because the setup notes omitted a required configuration file. I reproduced the problem on a clean folder, added the missing step and asked a teammate to follow the revised notes without my help. They reached the startup screen. I then added a short troubleshooting section for that specific failure. The check was limited to our local setup, not a full deployment test.”

The revision makes the action and evidence visible. It also states the boundary. It does not claim the documentation solved every setup problem.

How much background is needed?

Only enough to explain the decision. The listener does not need the whole project's history before hearing about the missing step. If a detail does not affect the problem, action or result, consider removing it.

Keep necessary context, such as whether the work was a class project or a professional responsibility. Shortening should not make a small exercise sound like a production incident.

What if there is no measurable result?

Use an observable outcome. A teammate completing the documented setup is a valid bounded result in this fictional example. A claimed productivity percentage would need a real measurement and comparison.

If the change was never tried, say what you produced and what remains unverified. You can still explain the reasoning without pretending the intended benefit already happened.

Try the editing exercise yourself

Take one answer containing “helped,” “improved” or “worked on.” Underline each broad claim and add the action or observation behind it. Remove any statement you cannot support.

Read the revised version aloud to a listener. Ask them to identify your contribution and its limit. A stronger answer is one they can understand and question, not one that contains more impressive adjectives.

References and next practice

careerservices.fas.harvard.edu — career

Browse interview topics · Practise a question in Interview Challenge · How to Prepare for an Interview