What Admissions Committees Actually Look for in a Master’s CV

If you’ve ever uploaded your CV into a graduate school application and thought, “I hope this is what they’re looking for,” you’re not alone.

I see this every single cycle.

In a recent live workshop, I walked through how admissions committees actually read master’s admissions CVs — and where strong candidates often leave opportunities on the table.

This post breaks down what I shared in that session, plus what I’ve learned from serving on admissions committees and reviewing thousands of applications over the years.

What an Admissions Committee Really Is (and Isn’t)

When applicants hear “admissions committee,” they often imagine one admissions officer skimming applications late at night.

That’s not how it works.

In my experience, admissions committees are supplemental to the admissions office. When I served on the admissions committee for Carnegie Mellon’s Master’s in Computational Finance, I didn’t work in admissions — I supported decision-making by evaluating candidates from a career and outcomes perspective.

Admissions committees often include:

• faculty

• academic advisors

• staff

• career services professionals

• sometimes students or alumni
  

The goal is to get a holistic view of you — beyond GPA alone.

When I review applications, I’m asking:

• Are you academically, professionally, and technically prepared?

• Is there a clear through-line from your past experience → this program → your career goals?

• Do you understand your gaps compared to other candidates — and have you taken steps to address them?

What Your CV Is Supposed to Do in the Application

Your CV should tell me what I can’t fully see elsewhere.

Your transcript tells me you took Machine Learning.Your CV tells me:

• what you actually built

• which tools you used

• how deep you went

• and why it matters for the program you’re applying to
  

I use the CV to understand:

• your technical preparation

• your research depth

• your leadership and initiative

• how intentional you’ve been about preparing for this program
  

Admissions has already spent hours reviewing your application. When it reaches me, I’m being asked to give targeted feedback on specific points in your file. 

If I can’t find the information I’m looking for quickly, I’m not able to advocate on your behalf. And when I’m reviewing a hundred CVs in a short amount of time, I can’t afford to read between the lines for any one application.

The Biggest Mistake I See: Treating a CV Like a Resume

This is where a lot of strong applicants go wrong.

A recruiting resume is designed to be skimmed in seconds. It’s tailored to one job and leaves a lot out on purpose.

A master’s admissions CV is different.

Your CV is allowed to be:

• more academic

• more detailed

• more comprehensive

That means it should include:

• projects

• research

• leadership

• academic awards (with context)

• initiative outside formal work experience
  

In the U.S., employers usually don’t care about Dean’s List or GPA past a certain point. Admissions committees often do — if it helps us understand your readiness for the program.

How Long Your CV Should Be

For most master’s programs: 1–2 pages.

Once a CV pushes past about a page and a half, it usually becomes less helpful. Longer CVs make sense for:

• PhD programs

• faculty roles

• research-heavy positions
  

For master’s admissions, I want relevance — not volume.

What Actually Strengthens an Application: Showing You’ve Closed Your Gaps

No applicant is perfect.

What I care about is whether you:

1. understand where you’re weaker than other candidates, and

2. have taken initiative to address that.
   

If you’re applying to financial engineering with no finance background, your CV should show:

• relevant coursework

• certifications

• applied projects using financial data
  

If you’re light on programming, I want to see:

• current coursework

• independent projects

• proof you’re actively upskilling
  

Your CV is where you demonstrate that you’re not just hoping to “catch up later.”

What Strong CV Bullets Actually Do

During the live workshop, we reviewed CVs in real time, and the same pattern came up again and again.

Strong bullets answer three questions:

• What did you do?

• How did you do it (tools, methods, skills)?

• What was the outcome?
  

Vague bullets make me guess. Clear bullets build confidence.

You’re Writing for Two Audiences at Once

One thing most applicants don’t realize: you’re writing for two different readers.

• The specialist (faculty or technical reviewers)

• The generalist (admissions officers, advisors, career staff)
  

If your bullet is so technical that a smart generalist can’t follow it at all, you lose impact.

A simple fix:

• define acronyms once

• lead with the goal before the method

• give just enough context for non-specialists to understand why it matters

Projects Matter — Especially for Technical Programs

For analytics, engineering, and CS-adjacent programs, your projects often carry more weight than your job titles.

A strong projects section usually includes:

• a clear project title (you can rename it)

• dates (to show scope)

• tools and technologies

• 1–3 bullets covering:

  • goal or hypothesis

  • methods used

  • outcome or insight

  • collaboration or stakeholders (if applicable)
    

If you’re applying to management-leaning programs, I also want to see how you worked with others — not just the technical execution.

Leadership and Extracurriculars Belong on a CV (When Done Right)

Yes — leadership experience matters, especially for management-oriented programs.

When I review CVs, I’m also thinking:

• Who will contribute to the cohort?

• Who will shape the classroom experience?

• Who has already demonstrated leadership?
  

Leadership entries work best when they include:

• your role

• what you led

• who it impacted

• what changed as a result

A Note for International Applicants: Language Matters

One quick thing I flagged during the workshop: certain phrases don’t translate well across countries.

For example, the word “ministry” in the U.S. often has a religious connotation. If you’re applying internationally, be mindful of how institutional language may be interpreted by U.S.-based reviewers.

Small wording changes can prevent confusion.

Section Order Is Flexible — Story Is Not

I usually recommend education first for master’s applicants.

After that, the order is flexible:

• Projects above experience if the program is technical

• Experience first if it’s more applied or professional
  

What matters is that your CV tells one clear story toward the program you’re applying to.

Final Thought: Consistency Matters More Than Perfection

One of the biggest issues I see right now is inconsistent tone — especially when parts of a CV feel AI-generated and others don’t.

I’m not looking for perfection. I’m looking for clarity, consistency, and intention.

If your CV reads like one voice telling one story, you’re already ahead.