Switching into tech

Yes, but it is the harder version of the switch, so plan for twelve to eighteen months of steady work and a first role that may not be glamorous. Without a degree, your proof has to be stronger: real projects, a clear specialism, and a route in that uses the experience you already have.

• Career
• Programming

Engineering graduates from electrical, mechanical, civil, chemical and similar degrees switch into software all the time. Fill the CS gaps that hiring actually tests (programming, data structures, databases, how the web works), build projects that use your engineering domain, and apply as an engineer who codes, not as a beginner.

• Career

Some bootcamps are worth it for some people, but far fewer than the adverts suggest. A bootcamp can help if you need structure, feedback and a cohort, and you can afford it without debt that scares you. Judge a specific bootcamp on audited outcomes, instructor feedback, curriculum depth and contract terms, and try the free route for a month first.

• Career
• Programming

You already have the hardest part: SQL, business context and knowing what good data looks like. Add Python for pipelines, data modelling, an orchestrator, a cloud warehouse, Git and testing. Build one end-to-end pipeline, then move internally by taking on engineering work in your current team before applying outside.

• Career
• Data
• Databases

First check whether it is the path or the circumstances: a bad team, a bad first job or burnout can feel like a wrong career. If the path really is wrong, you are rarely starting from zero. Map what transfers, test the new direction cheaply while still earning, and plan a bridge rather than a leap.

• Career
• Mindset

Yes, but not by collecting courses. Choose a role that uses what you already know, learn the specific skills that role needs, build proof you can show, and expect six to eighteen months of consistent work before the first offer.

• Career
• Data
• Programming

Treat it as a structured return, not a restart from zero. Refresh one modern stack, build two or three small but real projects, explain the gap honestly in one line, and apply to roles that value maturity and reliability alongside code.

• Career
• Web
• Personal branding