Who built MPE
I'm Joseph Braithwaite. I spent 25 years leading transformation work in financial services, healthcare, technology and the public sector, then sent 5,003 applications and got about 50 responses. I built MPE because I wanted to know what my resume was telling the people reading it, measured against the job they were hiring for. You can check the same thing on yours.
Why MPE reads capability instead of matching words
A match score counts how many of the posting's words show up in the resume. It was built to sort a big pile quickly and it does that, but it can't tell you whether the person did the work, and anyone can raise it by adding the right words. Candidates have learned to do exactly that, so most resumes now say the right things and the words have stopped telling you much.
MPE starts with the job description. It pulls each capability the role asks for in the posting's own words and sets the level each one needs, on a six-stage scale of skill from Novice to Mastery. Then it scores what the resume shows against that level and puts the resume line behind every score, so you can check it yourself. Where the resume doesn't show a capability, the report says it's a gap.
The same resume can read very differently against two jobs, because the jobs ask for different things at different levels. The three example reports on the homepage show one resume read against three roles.
What MPE doesn't do
It reads what the resume says. It doesn't verify claims, predict performance or make the hire. The person hiring makes that call, and the report tells them where to spend the interview.
Who it's for
Anyone hiring, whether that's a recruiter, a search firm or an in-house team, and anyone applying who wants to know what their resume shows before they send it.
Get in touch
MPE-Copilot is based in Toronto, Ontario. Email [email protected]. If a report gets something wrong, tell me. That's worth more to me than a compliment.