How Claude Help Me Build My $200k+ ML Resume

Structure

Structure can vary, and you should tailor it to each role. The goal is to get the most important information showcasing your fit for the job into the top third of the page.

However, in general the following works well for the majority of cases.

• Header
• Summary Statement
• Skills
• Experience
• Projects
• Education

You only really need the first 4 sections in the majority of cases.

Header

All you need is:

• Your name.
• Job title or how you see yourself. (Put data scientist if in doubt, don’t say “aspiring”).
• Contact details.
• Location.
• Relevant links like LinkedIn, GitHub, Medium, Kaggle etc. No more than 4.

One thing to ensure is that the links work.

Summary Statement

A summary section used correctly can instantly tell the recruiter that you are fit for the job; it can also be a detriment if you spew rubbish and fill it with too much exaggeration.

You realistically should only have a summary section after 2+ years of experience in the field, as it allows you to “summarise” your expertise and showcase the results you have generated.

There is a slight exception, though: when you are changing roles. This is to provide the recruiter with context for your application based on your previous experience.

• Years of experience.
• Demonstrate results.
• Specialisms.
• No fluffy language such as “passionate,” “determined,” or “hard-working”
• No cliches or vague language.

There is no “correct” summary as it will really depend on your situation and the role you are applying for.

Technical Skills

For data science jobs, technical skills are so important and you will immediately be filtered on these, hence why you should have them right at the top of your resume.

You should only have three rows for this section

• Languages — Split by Proficient and Familiar:
• Proficient — Programming languages you feel comfortable working in.
• Familiar — Programming languages you have worked in the past with, but not overly confident at the moment.
• Technologies — List tools you have worked with or feel comfortable working in e.g. AWS, Git, Docker, GCP, Linux, Bash.

Experience

This is the most essential part of your resume, but arguably the most challenging to get right.

Start by drafting your experience bullet points and then we will refine them with Claude to make them really standout.

However, the better your drafts are, the better Claude will optimise them, so start with the following:

• 3–5 bullet points max experience.
• Don’t use your actual job title; you are allowed to be “creative” and make it sound more impressive, so it stands out.
• Only have experience that is relevant for the job.
• Weight your most recent experience more, or the experience most relevant to the role.
• Use active action verbs all the time, like “developed,” “led,” “optimised,” “generated,” and “improved” as it’s clear you did the work.
• Weave in technical details, don’t be too scared to be too granular and stuff in keywords.
• Use numbers, metrics and especially financial impact in every bullet point. If you struggle with this, it’s where Claude will come in handy and I will show you how to do this later on.

Projects

Projects are very similar to experience, but it’s often hard to measure business impact because the work isn’t for the business.

Either way, you need to think of them as experience because that’s the closest “experience” you have to the job role if you are adding this section in.

Here are some general principles to follow:

• Make sure to use numbers and metrics, as you would for the experience, in every bullet point.
• Provide links to your projects, and make sure they actually work.
• Make sure your project’s GitHub or portfolio website is well laid out, with a clear README.
• If you can add unit tests, a front end dashboard or website and any other end-to-end technologies you used to built the project.
• If you have many projects, add the most relevant ones for the role you are applying for

Education

This section doesn’t need to be too complicated, all you need is:

• University and degree
• Grade or expected (if its good, if not leave it blank)
• Graduation or expected graduation date

Following these checklists will give you a sufficiently good resume that we can now use Claude to optimise even further.

Claude Optimisations

I want to go over the three most impactful optimisations Claude can do for your resume.

Financial Impact

Many of my clients tell me how hard it is to link their work to financial impact.

To be blunt about it: if you work for a company, everything you do ties back to financial impact in some way. They employ you to generate a return on your salary.

So there’s always a way to connect your work to the bottom line; you just need to get creative with it.

Enter Claude.

You might not immediately see how your work connects to financial impact, but Claude can help guide you through that process. 

I want you to use this prompt:

“[Paste your bullet or task description here]”

Walk me through this step by step:

Ask me clarifying questions about what this task/project actually did — the scale, who used it, what process it touched.

Identify the possible financial levers this work could plausibly connect to (e.g. cost savings, revenue growth, time saved, risk/error reduction, retention, efficiency gains).

For each lever you identify, tell me exactly what data or numbers I’d need to find to quantify it (e.g. “hours saved per week x hourly cost of that role” or “% reduction in errors x average cost per error”).

Tell me where I might realistically find that data (my own project notes, team dashboards, a manager, finance/ops team, etc.).

Once I bring back the numbers, help me rewrite the bullet in an “action → method → quantified result” format.

Do not invent or estimate any numbers on my behalf — only help me identify what to look for and how to calculate it once I have the real data.