[ChristinaM]

I did it. I did a Master's (never had any intention of a PhD) in engineering, mostly focused on OR decision making applications in geography. So I knew maps and could write Matlab and Python scripts and I'd played around with some C/C++. I progressed into a tech career starting with a place where the mapping & geography knowledge was a huge asset. My CS experience was limited to 2 undergrad courses and reading a few books. It's taken a few jobs since then and about 5 years but I'm definitely purely a software developer now. Two things that I think helped were having a technical bachelor's degree (even though it's not CS) and having some projects I could talk about that that meant I knew stuff about the company's products that CS students wouldn't tend to know, like mapping projections and norms in GIS. When they asked me questions about stuff like sorting algorithms, I could explain some assumptions I would make based on the kind of work they do, not just give the generic 1st year CS course answer. Dev Bootcamp or similar might be worthwhile to give you some buzzwords for your resume and some projects you can show off. If you can get those on your own or your experience buzzwords match what you see in job postings, then it's probably not worthwhile. I wouldn't put the bootcamp on my resume, I'd put the skills and projects it got me down as personal interest projects.