If you’re an engineer moving into Project Management, your CV is probably underselling you.
The problem I see constantly: technically strong people who list what they did rather than what they changed.
‘Delivered ERP implementation’ tells me very little.
‘Led a company-wide ERP rollout across engineering, production, purchasing and finance — coordinating stakeholder engagement, business process redesign, user training and adoption’ tells me you actually ran something.
A few things that make an engineer-to-PM transition land better on paper:
-Lead with the scope. How many departments? How many stakeholders? What was the scale of what you were managing?
-Name the methodology. PRINCE2, Agile, hybrid — if you used a framework, say so. It bridges the gap for hiring managers who aren’t from an engineering background.
-Show the business impact. Throughput improved. Lead times reduced. Processes standardised. These are the outcomes a business cares about, not the activities you carried out.
Your engineering background is the differentiator. Don’t hide it behind generic PM language. Make it clear that you understand both sides.