CV.

My CV is what gets me through the door to online assessments. For me it comes down to two things: a clear structure, and showing impact on every line.

Structure

I stick to the same sections, in this order:

1. Header: name, location, and contact links (email, LinkedIn, GitHub, portfolio).
2. Education: university, degree, dates, relevant coursework, and grade.
3. Work experience: role, company, dates, and a few bullet points for each.
4. Projects: project name, the tech stack, and a couple of bullet points.
5. Programs & awards: hackathons, workshops, and programs I've been selected for.
6. Skills & interests: technical skills and interests together in one section, because they go hand in hand.

Showing impact

Everything on my CV should show impact. For work experience and projects, I quantify wherever I can and write every bullet the same way:

Developed X, using Y, resulting in Z.

• X is what I built.
• Y is the tech I built it with.
• Z is the result. This is the part that shows impact, so I put a number on it whenever possible: users, hours saved, percentage improvements, people helped.

For projects, I also want the reason to come through: I built this because of something, and it resulted in something.

A made-up example of the format:

Built an internal reporting dashboard using React and TypeScript, cutting the time the team spends on weekly reports by ~30%.

Skills and interests

I split this section into rows:

• Languages: e.g. Java, Python, TypeScript.
• Frameworks & tools: e.g. React, Spring Boot, AWS.
• AI tools: e.g. Claude Code.
• Interests: what I'm into outside of tech.