* Play to your strengths
Leverage your experiences and map them over to software. The only real difference is that the QA and shipping process can be updated hourly vs hardware which takes months at minimum, so build perfection isn’t as hard of a constraint.
Leverage your finance, strat, and operations knowledge. That’s basically the Eng. Manager’s job (Director level/VP level?). Most coders can’t tell you the business value of their code/tasks - that’s a problem to bridge the value prop back to the business side. Also most “Eng” think there’s infinite resources, but don’t account for costs $$$ to use cloud services.
My advice: * learn the software construction process * DO NOT GO INTO IMPLEMENTATION - unless you’re super passionate about it, there’s no way to be proficient or good at it in 1.5 years - college grads will lap you. CS grads by default have done it for 4years and are still usually not that ready to switch from solo academia into a team, corporate standard.
Hope that gives you a perspective to consider!