I don't think this is strictly related to software engineering, though. I think most people doing horizontal career transfers use some form of the above to achieve success.
I don't think this is strictly related to software engineering, though. I think most people doing horizontal career transfers use some form of the above to achieve success.
I'm not sure if this is still the case for people, but I faced a lot of discrimination from management over my lack of degree. Especially managers who "inherited" me. Some of it was petty too, like all the other devs on my team were software "engineers" but since I lacked a degree, I was a software "developer". AFAIK, it wasn't a salary thing either.
It's not difficult to get a degree, especially if you have experience in the field. So I would say that it's worth it.
To me an engineer has a degree in engineering (including software engineering, which focuses on large-scale infrastructure, not algorithms). In many countries engineers are legally liable for what they implement.
can you elaborate on what you mean by this?
However, government jobs almost always have a hard degree requirement. I'm not sure why this is. I wouldn't take government jobs as representative of the industry.
There are a surprising number of loopholes. For example, many federal engineering jobs require any one of the following:
1) A bachelors degree in engineering
2) Sufficient college coursework without a degree with relevant experience
3) A non-engineering degree with sufficient engineering coursework
4) passing the engineers in training (EIT) exam with relevant experience (which doesn't necessarily require a degree to sit for)
5) A professional engineer (PE) license (which, in some cases, doesn't require any college)
I do think HR is biased towards just looking for degrees. Probably out of either laziness or risk-aversion.
"Our engineering is backed by MIT graduates"
"Our engineering is backed by the best engineers"
One sounds a LOT better to a client. It's a lot easier to sell a product when you can lean on an actual credential than a vague superlative. Even if your vague superlative is absolutely true.
Unless it’s crypto. Then I’m still “yeah but nah tho”.
I tell him alot since I want to be honest, I don't know how much longer extremely basic, low end website/api development will stick around. With Github Copilot currently I can see it almost replaced, but with what we get into in the future, I don't think we'll need people who at best call an api and display the data on a website with no other thought or architecture.
I guess I've never seen a position which only did API calls from JS and formatted data. That's always been wrapped up with develop/implement parts of the API as well. Maybe I've not worked in enough "enterprise" shops?
You can teach yourself pretty much all of a CS curriculum by buying a stack of textbooks listed on CS syllabi, and then going to town. Naturally, you’ll build projects while doing this.
Do some LC and prep for interviews.
You don’t need to get a CS degree to get SDE interviews. It helps, but isn’t necessary. And to pass technical rounds, you don’t even need to have read most of that stack of CS textbooks. You need some bits and pieces from that stack of books, and be quick on your feet with LC medium.
If your friend is good at standardized tests, then LC is right up their alley.