CaseMentor
← All recruiting guides

Write a résumé a recruiter can understand

Turn a responsibility into evidence of your contribution without inflating the result.

Start with the decision you helped make

Pick an experience with a clear problem and a contribution you can explain. Work, research, volunteering and student responsibilities can all provide evidence. Write the situation in plain language before compressing it into a bullet. A reader outside your organisation should be able to tell what was difficult and what you personally did.

Separate your work from the team outcome

A project may have saved money or improved service, but that does not mean you caused the entire result. Identify the analysis, conversation, design or implementation you owned. If others delivered the outcome, say how your work helped them. Use a number only when you know what it measures, the time period and the basis for attributing it to the work.

Use evidence you could defend in an interview

A count, scope, adoption decision or observed change can be useful when a financial result is unavailable. Do not turn an estimate into an achieved saving. If no outcome has been measured, describe the decision or deliverable honestly. Keep working notes on where your evidence came from; the final bullet can remain short.

Edit for the vacancy

Select experiences that show you have done work the role calls for. Remove unexplained internal acronyms, repeated duties and claims such as "excellent communicator" that have no supporting example. Review the actual application instructions for document format and length. Read the exported file yourself before submitting it; formatting in an editor is not proof that the final document is readable.

A fictional example

Starting point

Responsible for improving onboarding and working with stakeholders.

A more useful version

Mapped the induction handoffs across three volunteer teams and introduced a shared owner checklist, adopted for the next intake.

This fictional rewrite names the work, its scope and an observed outcome. It does not invent a percentage improvement or imply that adoption proved better performance.