Two points
1. Maybe its time to move on, problem with small tech companies is there has to be an opportunity for you to move into.
2. I wouldn't compare technical PM promotion to developer growth.
Otherwise, next time you have the "take more ownership" conversation don't hesitate to ask for specifics where you can do that. Development goals shouldn't be guess work.
I've been with this company for about a year, we just closed another $10M series B so at this point I want to figure out how I can leverage my position since we're without a doubt now very much in a growth phase. I've read about and heard about people who started out at as engineers at "growth stage" startups and then somehow leveraged their way to far more meaningful and high earning positions. I'm just reaching in the dark as to how one actually does that, aside from being a "good" employee and working hard.
Competing with FAANGs is a losing game, and probably not relevant for 98% of technology roles. I would highly recommend that you pick a few key senior engineers and compensate them well via paid time off and salary. When you have major problems this will be the group of technologists that will fix it for you.
For your mid-tier to junior technologists look for individuals that are trying to transfer into tech roles and don't have alot of experience BUT can demonstrate real ownership of problems in whatever business they were previously in.
For mid/jr level people one of the most important things you can provide is a clear path that shows your company is willing to invest training in your software & common industry tools.
As for finding them: check out your local technology meetup groups (online or in person), look for recommendations from your social network, check about posting opportunities with local universities/colleges.
The symptoms you describe have happened to me, might not be the same cause but worth sharing. At a certain point I felt like it had been months since I had delivered anything of engineering value.
The underlying issue was that my priority alignment is heavily skewed towards delivering solutions to technical problems. On discussing with my leadership, while they appreciate that I'm hands on their read was my organizational experience and "oversight" for major projects was the most valued.
Knowing that really helped me to relax a bit and understand that I won't always be working late nights to deliver some sweet resiliency workflow and thats fine.
TLDR: sync with your leadership and ask what value you bring so you can align your time to their priorities. Warning, this may not be a fun conversation.
If you're not working, it can be easy to lose momentum. If nothing else, check-in and being held accountable for actions and follow-ups is important. So is the sense of having work to do. Even without my bag of uncommon hacks, there is value in this alone.