| Hello, I had a question, partly inspired by a post someone made here a few years ago about what's the fastest way to become employable in tech. I didn't study CS and am beginning to learn about programming in the evenings as my current job (Legal sector, non-technical) is unrelated. At the moment I'm still just learning and doing it for fun but it'd be nice if there was a potential path to doing it for money/being employed one day, if I still enjoy it. I know obviously any job would work, but are there specific types of jobs you'd recommend that are more "tech-adjacent" so I could, to some extent, learn on the job? An example someone used in the previous thread was trying to work in tech support, like an entry job in quality assurance/control (QA/QC), or a tech support role at a small/mid-sized startup. (was also curious if you'd heavily priortise in-person roles to learn from colleagues, or whether it doesn't matter and hybrid/remote roles would suffice - I don't have a preference for the right job, I'm UK-based btw) I was just curious if there are options where I could work around/with software developers and be exposed to more technology during my day job, to then help with learning programming in the evenings/weekends. Or, would you just recommend doing a bootcamp? I know this journey is for the long haul, but was curious if there are any types of jobs I should be targeting: where I can get good exposure to programming and tech in general, without having the experience. |
There is also demand for people with real world experience to join software companies to help build software for their previous Industry. I could be the best developer in the world, but any legal software I could make would suck because I don't know anything about the legal industry.
Also coding/programming is a skill, not a job. You don't have to be an engineer to code. Similar to how not everyone who writes is an author. Learning to code and wanting to become a software engineer is advertised as the same thing, but its really not. Also the job of a software engineer really isn't coding past a certain point, its taking fuzzy business requirements and turning them into technical specifications capable of being implemented. Coding is just a detail at that point, like pouring concrete is a detail of construction to an architect.
I would recommend automating tasks at or building tools for your current job. I personally started in tech support and moved into engineering. But 95% of the people who were in tech support with me are either still in support or moved into services, so its not exactly a golden path. I was only able to make the switch because I was building tools for other support reps, and I was able to pivot that into a full time internal tools developer position.
Also bootcamps have peaked. Maybe do one out of interest, but don't expect it to turn easily into a full time position like its 2015.