The solutions architect role was ok in that I got to do more program management stuff in addition to architecting systems. I didn't like being on the sell side though because I found project managers keep cutting budget to win the project.
I am considering trying program management roles. I like interacting with stakeholders. My ultimate goal is engineer management, but I doubt anyone will give a chance in this market. Does anyone have advice what's the next best role that will help reach this goal?
Have you ever fallen in love with a problem? How good are you in describing your customer's job?
If you had to reverse-engineer the offering of your past jobs, how would you describe the value they created for users? What would they lose if they stop using them?
I was in a similar boat, and still am, frankly, but at this point I have decided that dealing with people is a big No-No for me, so I will stick to the IC track.
This way I will have to get good at coding and my skills but my head will also be free of bullshit. Ideally, I would have my own LLC and get work that way, but that also seems very difficult to do.
It seems that asking the questions that you're asking involves some kind of "spark" and brings to mind the saying "anything worth doing is hard" or something like that.
So I would say if you are confident that you want to do Engineering Management is just apply to jobs and tweak your resume in the best way possible, and explain how your previous roles aligned with engineering management.
And I mean really become a beast about this. Make your resume slide through to the Recruiters table with zero friction.
And then good luck on your interviews.