Break Into Project Management From Any Tech Role

This is the move I actually made. QA Lead to Junior PM at a mobile games studio in 2019. Ten years on I run programme and operations for an enterprise AI and software company. Nobody handed me a route, so I found one slowly and made most of the avoidable mistakes on the way.

Thirty minutes to skip the slow part.

We cover which parts of your current work already count as project management and how to write them so a hiring manager sees it, which gaps genuinely block the switch and which ones you are worrying about for no reason, how to get PM work before anyone gives you the PM title, and what the first ninety days look like once you land it.

The route in differs by where you start. QA and support people already own release readiness and stakeholder pressure and usually undersell both. Developers have delivery credibility and struggle to show they can run scope and people. Designers already manage stakeholders and rarely frame it that way. Business analysts are closest and get stuck at the coordination ceiling. We start from where you actually are.

We also cover whether you should want this at all. Some strong engineers and designers move into PM for the wrong reason and regret it, and I will tell you if that is what I am hearing.

Who this is for: anyone at zero to five years in QA, software, design, support, data or business analysis who wants to move into project or programme management.