Half of what people put on a PM resume is not project experience, and half of their real project experience never makes it onto the page. The reason is simple: almost nobody has been given a clear definition of what counts as a project.
Without one, people guess. They leave off the office move or the system rollout they ran because nobody called them a project manager at the time, and they pad the page with everyday tasks dressed up as projects. Hiring managers notice both, and the padding makes them trust the rest of the resume less.
In this video, I cover:
- The four markers that make something a project: a goal, an end, other people, and something to figure out
- The fastest version of the test, and real examples run through it
- How to find the projects hiding in your work history, volunteer work included
- How to cut the padding without underselling yourself
- Why size is not one of the markers
- The payroll changeover that became the strongest line on one resume
Ready to close the Experience Gap? Join The Eddie System and gain real PM experience inside a live PMO environment.
Want the full breakdown? Read the complete article →
Ready to gain real PM experience?
Once you have counted what you already have, the next step is building more. Inside The Eddie System you work through governed projects across many industries in a live PMO environment and make the calls yourself.
