Unfortunately, our company doesn't have proper career advancement advice or plan for "basic" levels like Juniors, Mid-level devs, and Seniors. There are role definitions but no guidance on how to progress from one to another.
With the Team Lead role, it's even worse. Nobody I asked around was able to tell me how one goes from a Team Lead to an Engineering Manager or an Architect (two possible roles "above" the team lead).
Now, I've been asking my Engineering Manager to give me at least some ideas about what I should be focusing on to learn skills necessary for the Engineering Manager role, but he can't tell anything except that I should become "visible". He says that if I were indeed ready for that role, I wouldn't be asking about it in the first place. Because "people at this level have to deal with a lot of uncertainty all the time," and asking for a specific career path is the demonstration of my inability to deal with uncertainty and take my career in my own hands.
This makes me feel doubt myself, but on the other hand, I see that other companies, especially those I consider to be successful, do have a clear career path beyond the Team Lead role.
Am I wrong for asking for something clear at this level? Should I indeed figure this out myself?
That being said if you don’t feel like your skills are being acknowledged, you’re not learning new skills while on the job (unlikely in a start up but possible) or that the leap to the next step seems to great at your current job, you could just leave when you do feel ready and have learned enough, seeking your next job at the next level above your current. In the interim try to work with your engineering manager As much as possible to learn from them.
Going into management is different than continuing on the IC path (at least in most companies). As a principal or architect, your job is to find the technical areas that should be explored (e.g. should Kubernetes be used, or Rust or something else), what are the implications of these technologies as well as how well they will solve the customer problems. Splitting the project and working with the rest of the team to have a sound solution. As a manager your job will be to deal with people and conflicts that arise due to various misalignments. Motivating people, making sure projects get delivered, taking responsibilities for things that you weren't aware were happening. Setting direction and making sure everyone is informed on what is going on. These are just the highlights, once you get into the position you get to see the different nuances, e.g. how to talk with person A vs person B. Figuring out what motivates them, what upsets them, what are they good at. Observing people and providing them guidance on how to achieve their goals.
I don't blame my managers/bosses - they are busy figuring out their own careers, they just don't have the interest or time to help someone, unless it directly and immediately benefits their own case.
I've seen this repeatedly - people advance their careers by doing one of the two : first, they are loud and persistent in asking for more money, better position etc and highlighting their work. Second, they jump jobs every 3 or so years, getting better pay and title every time.
You might be the best at what you do, but nobody will care unless you make them care.
I wish someone had told my younger self about this.
It's good you are being proactive. But unfortunately lots of companies aren't clear about how to get promotions etc..is there someone in HR you can talk to? Or the founders?
I would just make sure you're at your A game if you are looking for promotion routes as well.