I'm in my mid-30s and I work as a Senior Product Manager at a software company (not a big one). I'm not really happy and I'm wondering if I should go back to coding. Albeit, I haven't been in a coding role in almost a decade.<p>My entry point into tech was web development (teens/college) but found myself intrigued by design and UX challenges, so I went from a front-end developer in college into product/UX design and did that for some years.<p>What I know now that I didn't know then:
- Every role / skill set has its challenges, especially when you get into the more advanced tiers. In my early 20s I thought that "coding wasn't for me" because I was hitting seemingly insurmountable walls. Now I know those are simply the challenges that help you level up.
- You can be good at anything and get whatever job you want if you set your mind to it. Surely some of us are more right-brained or left-brained, but I feel like there is an argument to why coding is creative and how PM/design is technical.<p>I guess I just miss coding. I miss not dealing with people problems. I miss the incremental feeling of achievement with shipping code. I don't like that my work performance is dependent on politics, ambiguity, and people stuff instead of things working or not working.<p>Product management doesn't have that same joy for me and I'm not sure if this is right for me.<p>How do I get back into a coding job?
Will my trajectory / resume be a hindrance?
What are your salary requirements? That's probably the biggest sticking point, as you won't be a senior dev (in terms of coding skills). I'd address that relatively quickly in any interview process.<p>I think your skillset is well aligned with a team lead who has one foot in the coding world and one in the product/project management world. That's probably the type of role I'd look for. In my experience, consulting companies are far more forgiving for this type of transition than product companies are.<p>So I'd take the following steps:<p>* do some coding in your spare time to see if it matches with your ideas. No sense in making the jump if you are wrong. You might see if there's any small projects/hackfests you could participate in as a coder at your current company.<p>* write up a resume emphasizing your technical skills. This can be coding, requirements gathering, QA, architecture review/feedback, etc. Minimize your prouct management experience.<p>* find a consulting company looking for a team lead or senior engineer in a tech stack that you are comfortable in and get to know the hiring manager. Ask them for coffee and explain your situation and ask for their advice (people love to give advice) on how to find a coding job. Are there specific things you can do to make the transition easier.<p>* make a list of consulting companies that you'd like to work for and look at their jobs page. Apply, but do it through the back door, via someone you know there. If you don't know someone, find someone you can get to know (even a weak connection like an interaction on HN or Twitter is far better than applying through the front door)<p>* get hired :). Do a good job there, and make sure you get as technical as possible. Given your background, the company may pull you towards the project management side, but resist.<p>* after you've been there for 1-2 years, look around for a product company if that is your end goal.<p>HTH.
Another way to look at it is to take your current job and make it "yours".<p>If you hate politics, don't play them.<p>If you hate ambiguity, create clarity.<p>If you hate people stuff, leave it to people managers.<p>You can be a successful PM and focus more on the creative sides, but only you will be able to do that. Most people just do the job as their managers think it should be done, and that's super fixed minded. Create your own definition of what a PM could be capable of doing that matches your intuition.<p>Otherwise just look to pivot to a IC coding role as PMs do this all the time and vice-versa.
There's nothing stopping you from getting back into coding in general, that'd probably be the first step. Rivers Cuomo (of Weezer fame) can still be spotted around github issues and stuff - just as an example of someone who still codes even though it isn't their main job.
Maybe you can stay at your current Org and pivot to some more code related tasks - start small and gain familiarity and work up from there. You'd have good support from others you already know and a good "thing" to put on a resume. No experience is bad experience for someone in your position.<p>Best of luck to you<p>Edit: was thinking on this and maybe just getting a dev env. for your work's codebase could be a good first step. even if it's just commented out code making a merge request and making a production deploy could be valuable too - however that may look
> I miss not dealing with people problems.<p>As a coder, you don't get to ignore people problems. Unless you're very junior, and can get away with expecting your manager to filter that stuff out for you. Beyond that, if you want to get anywhere... you need to build relationships with your coworkers, users, testers, prod support people, manager, etc.
I knew a newspaper journalist in his late 30s / early 40s who became a developer, and by the time I met him he was a senior developer and highly respected in the team and business. He was working at a tech 'scaleup' who were valued at +£2bn and that had been around for c.10 years. I think given your a PM and already in tech, it shouldn't be a problem. I'd use the fact you were a PM to your advantage.
I had this twice in my career, and in both cases I got back into coding as a freelance. Somehow it worked out well, possibly because of how your knowledge / experience is measured. I won't claim it was easy though.
What do you do as a PM? Do you really make business decisions or just write stories/review UX screens?<p>IMO running a real product is the second best (and hardest) things to do. The first being running a company.<p>For this to be true, you should really like the product. And your decisions should directly impact product revenues. And product revenues should directly impact your income.<p>If that’s not the case with your current product, consider trying another one before switching back to coding.
> Will my trajectory / resume be a hindrance?<p>On the margin, but not in totality. Will you get a Super Duper Senior Coder job right away like somebody who's been coding that entire time? Of course not. Will you get SOME coding job? Sure.<p>Just pick up some web dev stack that's popular (e.g. JavaScript/TypeScript/React), get somewhat comfortable with it (a handful of weekend projects) and then start applying places.<p>I will say you picked a really bad time, tons of companies are laying people off and freezing hiring.
i'm heading down the PM path from a CS degree background, working at a tech company for ~2 years. sometimes i wish i had gone into dev work so i could get better satisfaction in the day to day. it also seems like PM hiring is very picky which worries me if i lose my job. anecdotally lots of career pages have lots of open dev positions but few PM roles. is this a factor in your thought process for switching?