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.
What people tell me
My degree is in something other than computer science, such as commerce, mechanical or telecom engineering, or I have spent years in a non-coding role. I am not growing where I am and the salaries in tech look far better. I have tried a course or two, but I keep wondering whether I am too late, which course to take, and whether companies will even consider someone like me.
A composite of the messages behind this question, with personal details left out.
Key takeaways
- Tech hires for demonstrated skill far more than for the name of your degree, especially at startups and mid-sized companies.
- The fastest route uses your existing background: finance into data or fintech, engineering into embedded or automation, product into analytics.
- One focused path with projects beats five certificates. Certificates support a portfolio; they do not replace one.
- Salary growth in tech is real but not instant. Plan for a modest first role and faster growth after it.
- Consistency over months matters more than talent. Budget realistic weekly hours before you start.
The honest answer first
People from commerce, mechanical engineering, telecom, operations and product roles move into tech every year. It is not a myth and it is not reserved for prodigies. But the version sold in advertisements, where a three-month course leads to a large salary, is not how it usually goes.
What actually works is narrower and slower: pick a role, learn what that role needs, build evidence, and get in front of people who hire for it. Your degree is not the obstacle. Lack of direction and lack of proof are.
One more honest point. If the main reason is money, that is valid, but tech pays well for skills that are in demand, not for being in tech. A careful choice of role matters as much as the switch itself.
Match the role to what you already have
The biggest mistake career switchers make is starting from zero when they do not have to. Your background is an advantage in the right role.
| Your background | Roles that use it | Core skills to learn |
|---|---|---|
| Commerce, accounting, finance | Data analyst, business analyst, fintech operations, ERP or accounting software specialist | Excel to an advanced level, SQL, Power BI or Tableau, basic Python |
| Mechanical or electrical engineering | Embedded systems, automation and PLC, CAD or simulation software, data for manufacturing | Python or C, basic electronics or control systems, SQL |
| Telecom engineering | Network engineering, cloud and infrastructure, data analysis, IoT | Networking fundamentals, Linux, a cloud platform, Python |
| Product, operations or support | Product analyst, QA and test automation, technical support engineering, solutions roles | SQL, testing practice, scripting, communication with engineers |
| No strong preference | Web development or QA automation | JavaScript or Python, Git, one framework, testing |
Look at the middle column and pick the role that sounds like work you would still enjoy after a year. That decision matters more than which course you take.
What a realistic switch looks like
- Month 1: decide and validate. Read twenty real job listings for your chosen role in your city or for remote work. Write down the skills that appear most often. That list is your syllabus, not a course outline.
- Months 2 to 4: core skills. Learn the top three skills from your list with one structured resource each. For data roles, that is usually SQL, a visualisation tool and spreadsheets. For development, one language, Git and one framework.
- Months 5 to 7: build proof. Create two or three projects that look like the job. A data analyst builds a dashboard from a real public dataset and writes up what it shows. A web developer builds and deploys an application someone could use.
- Months 8 onwards: apply and keep building. Rewrite your CV around projects and transferable experience, reach out to people in the role, and apply steadily while adding to your work.
Some people land a role in six months; many take twelve to eighteen, especially while working a full-time job. Both are normal.
Transferable experience is worth more than you think
A commerce graduate understands ledgers, reconciliation and financial reporting, which is exactly what a fintech or ERP team wishes its engineers understood. A mechanical engineer knows how physical systems fail. Someone from product knows how users behave. When you write your CV, lead with the technical projects, then show how your previous domain makes you more useful than a generic junior candidate.
Courses, bootcamps and degrees
- Free, structured material is enough for most people to start: freeCodeCamp, The Odin Project, roadmap.sh for sequencing, and the free tiers of the major data and cloud learning platforms.
- Paid courses or bootcamps help if you need structure and accountability, not because the certificate opens doors by itself. Check what graduates actually did afterwards before paying.
- A second degree is rarely necessary for industry roles, though some employers and visa routes do filter on it. Check listings in your target market before committing years to one.
Browse the Sefism resource library for courses and roadmaps grouped by topic.
Is it too late for me?
Age and years spent elsewhere matter far less than people fear. Teams hire people in their late twenties, thirties and beyond who switched from other fields, and they often value the maturity, reliability and communication that come with a previous career. What counts against a candidate is not when they started, but whether they can show recent, working evidence of the skills the role needs.
Mistakes that slow switchers down
- Starting a new course every time the last one gets hard.
- Choosing a role by salary headlines alone, then finding the daily work does not suit you.
- Hiding the previous career instead of using it.
- Applying only through job portals with no outreach.
- Quitting a paying job before you have skills, savings or a clear plan.
Keep your current income while you switch
Unless you have savings for a long gap, learn alongside your current job. Protect eight to twelve hours a week, and look for ways to use new skills where you already work: automating a report, building a dashboard, cleaning up a spreadsheet process. That becomes real experience you can put on your CV.
If you are still stuck
For a detailed plan aimed at commerce graduates, read Moving into tech from a commerce degree. For the general route into development, see How to start your career as a software engineer. If you want help choosing a direction for your own background, book a free 1:1 session.
Was this answer helpful?
Read next
- Moving Into Tech From a Commerce Degree: Which Paths Actually PayAn honest guide for commerce graduates who want a better paid career in tech: how salaries really grow, which paths turn a finance and business background into an advantage (data analytics, business analysis, ERP consulting, fintech, QA, development), a six month plan, how to switch without quitting, and the pitfalls that cost people years.
- How to Start Your Career as a Software EngineerA practical route into the first software engineering job: pick one language and stop shopping, build things too big for a tutorial, learn the five fundamentals you cannot skip, get your code in front of a human, and apply earlier than you feel ready. Includes a twelve month shape to work to and an honest read on what the current entry level market has changed.
Your situation is not quite this one?
Members get written answers to their own questions, a roadmap built for them and feedback on their projects. Early access is open to X and Instagram followers and university students. Prefer to talk? A free call works too.