It's basically all downsides pretty much, and the only upside is being able to work on your passion - which is what motivates people who get into those fields.
Yes!! I can totally relate to what you are saying. I got started because I was interested and I am still passionate about it. But there is only so much that I can do. It just doesn't make sense for me to continue for PhD because even with PhD there is no guarantee that I would be able to get somewhere as I am definitely not someone coming from those top20 universities.
So by definition I rule out the chances of being an average research engineer. That's one clarity! Thank you!
Since I have most background in hard niches as you mentioned above, is there a way to transition to something else? What would the possible path be like if my ultimate goal is to become staff engineer or principal engineer?
This really depends on your previous experience. If, for example, you have previous experience with C++ (which is what is often used in those hard niches), it would make sense to just apply to generic C++ roles, and work your way up to high salary by getting promotions or changing companies. If you're in the US, it probably wouldn't hurt to apply to FAANG-type companies, as they rely heavily on the leet code, so your lack of concrete experience in things they do will not be a big problem (likely will just get you a low pay grade, but you can change that with promotions later).
Comments
Yes!! I can totally relate to what you are saying. I got started because I was interested and I am still passionate about it. But there is only so much that I can do. It just doesn't make sense for me to continue for PhD because even with PhD there is no guarantee that I would be able to get somewhere as I am definitely not someone coming from those top20 universities.
So by definition I rule out the chances of being an average research engineer. That's one clarity! Thank you!
Since I have most background in hard niches as you mentioned above, is there a way to transition to something else? What would the possible path be like if my ultimate goal is to become staff engineer or principal engineer?
This really depends on your previous experience. If, for example, you have previous experience with C++ (which is what is often used in those hard niches), it would make sense to just apply to generic C++ roles, and work your way up to high salary by getting promotions or changing companies. If you're in the US, it probably wouldn't hurt to apply to FAANG-type companies, as they rely heavily on the leet code, so your lack of concrete experience in things they do will not be a big problem (likely will just get you a low pay grade, but you can change that with promotions later).