Applications

How to write a résumé for an internship or graduate job

Create a clear early-career résumé that turns coursework, projects, and part-time experience into evidence employers can quickly understand.

Design for the first scan

A recruiter should be able to understand your direction, strongest evidence, education, and practical skills in a few seconds. Use familiar section names, consistent dates, clear headings, and enough white space. Decorative graphics, rating bars, and dense sidebars often make the important information harder to find.

For most students and new graduates, one page is enough. Two pages can be reasonable when every section adds relevant evidence, but length is not the goal. Put your most role-relevant section first after your contact details: that may be experience, projects, research, or education.

  • Use a readable type size and strong contrast.
  • Include city and country, email, phone, and a useful portfolio or LinkedIn link.
  • Remove a full street address, photograph, or personal details unless local norms or the employer explicitly require them.

Turn experience into proof

You do not need a previous internship to show professional value. Coursework, student societies, personal projects, volunteering, caring responsibilities, competitions, and customer-facing jobs can all demonstrate useful skills. The key is to explain what you did, the setting in which you did it, and what changed because of your contribution.

A strong bullet usually starts with a specific verb, names the object or problem, and finishes with an outcome or scale. Instead of ‘Responsible for social media’, try ‘Planned a four-week content calendar for a student society, coordinating six contributors and increasing event registrations from 80 to 125.’ Never invent a number; a concrete deliverable or decision is also a valid outcome.

  • Replace adjectives such as hardworking with observable actions.
  • State your individual contribution inside group projects.
  • Use numbers only when you can explain where they came from.

Make projects useful to a reviewer

A project entry should answer four questions: what problem did you address, what did you build or analyse, how did you approach it, and what was the result? Link to a portfolio or repository only when it is organised, accessible, and safe to share. A reviewer should not need to reverse-engineer your contribution from a folder of files.

Choose two or three projects that collectively demonstrate the role's core abilities. For a data role, one clean analysis with a clear question and honest limitations can be stronger than five tutorial clones. For a design role, show decisions and iteration, not only the final screen.

Tailor without starting again

Maintain a master résumé containing all credible bullets, projects, modules, and skills. For each role family, create a focused version by changing the order, selecting the most relevant evidence, and matching the employer's language where it truthfully describes your experience.

Check every claimed skill against a simple test: could you discuss how you used it in an interview? Group skills into meaningful categories and avoid long lists of tools you have only opened once. Finally, export a selectable-text PDF, use a clear filename, and read the document once at 100% zoom before submitting.

  • Mirror important terms naturally; do not copy whole sentences from the posting.
  • Proofread contact details, dates, tense, and link destinations.
  • Ask someone to tell you the story they understood after a thirty-second scan.

AI disclosure: This article was generated by AI.

Your next step

Turn the guide into one small action today.

Use what is useful now, keep a note of what you learn, and return when you reach the next stage of your search.

Browse open roles All career guides