How to read your MPE report

What each part of the report tells you, how it was worked out, and what it means whether you're hiring or it's your resume.

An MPE report compares one resume against one job description. It quotes what the resume says about each thing the role asks for. It doesn't check whether the claims are true and it doesn't predict how someone will do in the job.

If you're hiring, it shows you where the evidence is and where to dig. If it's your resume, it shows you what a recruiter can see on the page, and what they'll likely ask you about.

What a level means

Every capability is scored on the same six levels, for the role and for the resume. A level describes how someone did the work, not how big their job was:

These are the six stages of the Dreyfus model of skill (Rousse & Dreyfus). A resume rarely describes how someone thinks, so MPE writes each stage as a question about what a resume line can show, one per stage, as listed above. Every resume line is checked against all six, and a yes only counts when the line's own words say it - MPE quotes them. The line's stage is the highest question it answers yes, and a capability's level is the highest stage among the lines that show that work. The role's level is read from the posting with the same six questions. Title, team size and budget don't set the level - that is what scope is for.

The higher stages are hard to reach on purpose. A resume line rarely says someone acted without deliberating, and a posting rarely asks for it, so L5 and L6 show up only when the words are there.

Scope

Scope is the size and complexity of what the person was accountable for, kept apart from the level. Two people can work at the same level, one at a start-up and one at a global company, and scope is what tells them apart. It is built from three things the resume states: who the work affected (from one team up to several organisations - a 6 is kept for people who created an industry or changed how one works), whether the person owned it, led it or contributed, and how complex it was (several divisions or stakeholder groups aligned, a regulated environment, other work depending on it, first of its kind, national or international, a stated size of 1,000 people or $100M or more). A dollar figure or headcount is one part of it, never the whole. Three or more complexity factors add a point. Each capability gets a score from 1 to 6 next to the score the role asks for, and the overall score is the middle of them. If the resume doesn't state enough, scope shows as not shown - MPE never guesses.

If you're hiring: read scope next to the level. A high level at a small scope and a high level at a large scope are different hires.

If it's your resume: say who the work affected, what you were accountable for and what made it hard. If it isn't on the page, it can't be counted.

The headline

The first bold line sums up the result: how many capabilities are met or exceeded out of the total, how many fall short and by how much, and which one is weakest.

If you're hiring: this tells you how much of the role the resume covers at a glance.

If it's your resume: this is the first thing a recruiter reads about you, and the weakest capability is what they'll notice first.

Probe in interview

These are the capabilities where the resume doesn't show enough to meet what the role needs. Each one names what the role asks for.

If you're hiring: ask the candidate about each one. A gap on the page isn't always a gap in the person. The work may be there and just not written down.

If it's your resume: expect to be asked about each of these. Have a real example ready that shows how you did the work, what you decided and what came of it. If you've done the work and it's not on your resume, that's worth fixing before you apply again.

The four boxes

If you're hiring: compare Power Score across candidates for the same posting. Use Below Target to see how many areas you'd need to probe.

If it's your resume: Below Target is the count that matters. It's how many areas a recruiter will see as short.

Every capability, scored

Each capability is marked against the level the role needs:

A capability that isn't a match doesn't mean the person can't do the work. It means the resume doesn't show clearly enough how they did it. The level comes only from what's written on the page. Someone can have done the work at the right level and still score short if their resume says what they were responsible for, but not what they decided, how they did it or what came of it.

Some capabilities have no resume line showing the exact work, only related work. Those are listed with the related lines and count as not met. Related work is never scored.

If you're hiring: treat a stretch or a gap as a question, not a verdict. Ask the candidate to walk you through how they did that work. Related work is a lead to follow, not proof.

If it's your resume: a stretch or a gap is telling you where your resume undersells you, or where you really are short. If you've done the work, rewrite the line so it shows the decision you made and the result. If you haven't, expect to be asked about it.

Stated requirements

These are the yes or no items in the posting, like a degree, a certification or time in a sector. They're checked, not graded, and each one is marked as one of:

A higher degree meets a lower one, so a master's covers a bachelor's ask.

If you're hiring: a related credential is worth a question, not an automatic no.

If it's your resume: if a posting names a specific certification you don't hold, expect it to come up. Be ready to say how yours compares.

The spider chart

This shows the role's level (purple) and the resume's level (blue) for every capability at once. Where the blue sits inside the purple, the resume shows less than the role needs.

About the role

This is a plain summary of what the posting asks for: what the person is hired to deliver, what the role leans on hardest, and what would rule a candidate out. Both readers should check it matches their understanding of the job.

Dreyfus stage and scope

These describe how the person worked and how big the work was, read across all the scored capabilities. They are kept apart, so two people at the same stage can still be told apart by the size of what they did:

If you're hiring: read these against the role. Enterprise scope on a team-level role can mean overqualified as easily as strong.

If it's your resume: these show how your resume reads as a whole. If they sit lower than you'd expect, your resume may describe what you were responsible for rather than what you decided and did.

Execution risk, readiness and confidence

These answer three different questions, so they won't always agree:

If you're hiring: medium readiness with low risk usually means a strong profile with one open question on the main work. Ask about that first. High risk means the gaps sit where the role depends on most.

If it's your resume: low confidence means one line is carrying each capability. More lines that show the same work in different roles help.

Title against scope

Each job title on the resume is compared with the scope its lines show. Where they differ clearly, the report notes it - for example a VP title with team-level scope shown, or a director title with organisation-wide scope. It is MPE's reading, not a finding on its own.

If you're hiring: ask about it. Titles mean different things in different companies.

If it's your resume: if your title undersells the work, the lines are where you show it.

Alignment analysis

This is a written summary of what the resume shows against the role, with short quotes from the resume.

Capability pages

Each capability has its own page with these parts:

If you're hiring: the quoted lines are what the score rests on. Check them yourself.

If it's your resume: these lines are exactly what a reader sees as your proof. A line that says what you were responsible for, without what you decided and what came of it, scores lower than one that does.

Run your first evaluation - free
Listed on