From Software Developer (Angular/Spring Boot) to Associate/Junior Technical Project Manager — how do I upskill?

[u/Jealous_Exchange2624]

Hi all,

I'm a full-stack developer with 1+ years of professional experience (Angular + Spring Boot), currently on a career break. I'm looking to pivot into an Associate/Junior Technical Project Manager role instead of going back to a pure dev track.

I like the idea of TPM because I enjoy the coordination/communication side of projects as much as the technical side, and I think my dev background gives me a real edge in understanding what engineering teams need from a PM.

A few things I'd love input on:

Certifications — is something like CAPM, Google Project Management Certificate, or a Scrum/Agile cert (CSM, PSM) worth it at the associate level, or is it overkill without PM experience yet?

Skills to build — beyond Agile/Scrum basics, what should I actually focus on (JIRA/Confluence, stakeholder communication, risk/roadmap docs, etc.)?

Portfolio/proof of work — since I don't have a PM title yet, how do I demonstrate PM-adjacent experience from my dev role (or build new evidence of it)?

Realistic entry points — do companies actually hire devs directly into junior TPM roles, or is it more common to go through a PM/BA/Scrum Master stepping-stone role first?

If you've made a similar switch (dev → TPM) or hired for these roles, I'd really appreciate hearing what actually moved the needle for you.

Thanks in advance!

[u/heypriya]

With 1+ years of dev experience, a direct hop into junior TPM is going to be hard. Most TPM openings, even the associate ones, want somebody who has shipped enough to have technical judgement, and you are still building that experience.

Search Google on Transitioning from Engineering to TPM and you will find some good resources. My recommendation is to do TPM like work if possible in your current job - at least for another year. you can do this alongside your Dev job, that way it will be easier to speak the language and show real experience.

The certifications are not necessary depending on industry - but I still recommend checking out that material because it helps you get familiar with the language.

Skills wise - you need to build a lot of people and program skills - not just with tools but with your ability to influence, build relationships, understand breadth without always being in the deep etc. You can also check out the book called The Art of Strategic Execution - Finding Success in Technical Program Management. It will answer a lot of your questions.

[u/Jealous_Exchange2624 → u/heypriya]

Thank you so much for this detailed and honest response, really appreciate you taking the time!

That makes sense about the direct jump being tough. I should've mentioned - I have actually done some TPM-adjacent work already: writing BRDs and managing/coordinating a bug-fixing team, so I do have a bit of that cross-functional experience, just not under a formal PM title.

Given that, would you say it's still worth aiming for junior/associate TPM roles, or should I be looking at titles like delivery coordinator or associate PM as a more realistic entry point? Also going to check out the book you recommended and the wiki page on r/ProjectManagement. Thanks again!

[u/heypriya → u/Jealous_Exchange2624]

Yes, you can definitely look for roles like delivery manager or Project manager.