Hello everyone,
I am a developer with 3+ years of experience with full stack technology so mostly .Net and React along with some side projects in other languages. I wanted to ask if anyone has had any luck moving from high-end projects, to lower end projects(C++). I’ve become extremely interested in lower level projects like, embedded programming, firmware, drivers, compatibility layers but I don’t have any professional experience in those fields.
I understand that projects like these are high priority so they are less interested in taking a risk for a Dev without professional experience in C, C++, or Rust, even if they liked the candidate. I just wanted some insight
You must log in or register to comment.
In terms of skills I moved in the opposite direction as the tools got more advanced. There’s nothing stopping you from learning if you’re interested and have the time.
In terms of career development I think it’s a big mistake. There aren’t a ton of jobs there and it’s not getting better.
Interesting that’s partially why I thought going lower end would be better. More no code / AI tools seem to be taking the higher end applications by storm. Lower end is more complex and critical so I figured the jobs there would be better. Also with the addition of new chip architecture I figured the industry would have their work cut out for them
Lower end is more complex and critical
In that case, I suggest:
- Taking into consideration, the US Govt. mandates and learning Rust.
- This would only work out in the long term though, as in most places, there is not a demand for it yet
- I feel like it will catch on, considering they do have some points and a lot of power.
- If you are going with the short term one, getting familiar with C, C++ and being able to visualise memory.
- The visualise memory is required anyway. Alright, maybe not strictly required (I worked in a Govt. workplace and a lot of them could not) but it is important to excel.
You’re early enough in your career that going for a junior position in a company that does that sort of work should be easy enough. You could also do some solo projects and display on GitHub if you want to get an intermediate level position.
I’ve bluffed my way into technology changes every five or so years, across my career.
It went, for me, like:
Why do you want to do this, when you mostly have experience with that?
“It looks interesting.”
Do you have experience with this?
“No. But I know how to read the documentation, I pay attention and ask questions when my colleagues explain something, and I studied the basics of this, in college.”
It doesn’t usually land me the job. But all I needed was an occasional “yes” here or there, to get started on something new, and expand my experience.
Plus, even the “no” interviews have still been good for my professional network.
