Just giving my own perspective, not claiming anyone else's is wrong.
As another poster said, startups are tricky. I've worked for two, and the first was a poster child hostile work environment, doing subpar work for angry clients with ridiculous expectations. The second was an incredibly positive experience though the pay was junk. Now I'm at an enterprise, and burned out like I was at the first startup, but have identified a different path forward (heading into SRE now) as I know the root cause of this mentality now.
At the end of the day, if you're not interested or passionate about what you're working on, and you don't have clear upward mobility within your org, it's time to move on. Otherwise, it feels like your career stagnates and you think the career itself is the problem, not the current employment situation.
If you dislike the industry, you might still not like product/engineering-management roles.
It seems to me like myself, you need to find out what kind of work you like, what you'd explore for your own curiosity even if you are not paid.
Trying out OS/networks/compilers/data-science/research roles might be worth your while. But, if core CS is not your thing, it's possible you will find management roles (product/engineers) more satisfying.
The the exact opposite of my experience.
The problem though, is anyone can start a startup, and so you need to be sure you don't fall in with bozos. If you have a 5-person startup, and someone is "Head of Product" and full of their own ideas and talking down to engineers (or otherwise making them feel as you describe) then most likely you have a bozo on your hands, perhaps due to ego inflation during years of successful hoop jumping promoted by our education system & corporate culture.
The bottom line is that product management is one of the hardest disciplines, and within tech it's filled with wannabes who schmoozed their way in but don't actually have the chops. This is not the end of the world if they are humble and willing to take input from engineering. The flip side though, is that as an engineer you need to be customer and business-centric in your thinking—not all engineers can/want to do this, but with the structured thinking the discipline requires you at least have a head start. Good luck.