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.
this post was submitted on 15 Nov 2024
5 points (100.0% liked)
Experienced Devs
3961 readers
3 users here now
A community for discussion amongst professional software developers.
Posts should be relevant to those well into their careers.
For those looking to break into the industry, are hustling for their first job, or have just started their career and are looking for advice, check out:
- Logo base by Delapouite under CC BY 3.0 with modifications to add a gradient
founded 1 year ago
MODERATORS
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.
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.