Moving Into Tech From a Commerce Degree: Which Paths Actually Pay

The message behind this post

Someone sent me a short, very honest message. They have a commerce degree, they are working, and they are not growing where they are. They want a career in tech "where I get prosperity", and when I asked what felt hardest right now, they wrote a line that stayed with me: life without a handsome salary is like living in a desert.

I respect that honesty. A lot of career advice pretends money is a vulgar reason to change fields. It is not. Wanting financial security for yourself and your family is one of the most legitimate reasons there is. But it also means you deserve a straight answer about how tech pays, how long the switch takes, and which paths make the most sense for someone who studied commerce rather than computer science.

So this post is that straight answer.

My honest read

Yes, you can move into tech with a commerce degree. Plenty of people do, and some of the best data analysts, business analysts, product people and ERP consultants I know came from accounting, finance or business backgrounds.

No, a course alone will not make you well paid. Tech pays well for skills that solve expensive problems, proven through work someone can see. A certificate is a small part of that proof. The internet is full of adverts promising a six figure salary in twelve weeks. Treat every one of those as a red flag.

Your commerce background is an asset, not a gap. You understand ledgers, invoices, margins, reconciliation, cash flow, tax and how businesses actually make money. Most computer science graduates do not. The paths below are chosen because they turn that knowledge into an advantage.

Money in tech grows over time, not on day one. The first tech role may pay similar to what you earn now, sometimes slightly more, sometimes slightly less. The difference is the slope: after two or three years of real experience, the ceiling in tech is usually far higher than in most traditional commerce jobs. Plan for the slope, not the first payslip.

Salaries depend heavily on where you work and who pays you. A local company, a multinational, a remote employer and a freelance client can pay very different amounts for similar work. That is why remote and freelance work, covered below, matter so much for income.

The paths that make sense with a commerce background

Here are the realistic options, compared honestly. Time to job ready assumes around 15 to 20 focused hours a week while you keep your current job.

Which one I would pick in your position

If money and a reasonable timeline are the priorities, I would rank them like this:

1. Data analyst. It is the most direct bridge. You already understand the business questions; SQL and Power BI let you answer them faster than anyone doing it by hand. Every company has data it does not understand, and finance data is where analysts start.
2. ERP or CRM functional consultant. Less glamorous on social media, but consistently in demand and well paid, because companies spend heavily on these systems and need people who understand both the software and the accounting. Odoo is a practical entry point in many markets because small and medium businesses use it widely; SAP and Salesforce carry larger enterprise demand.
3. Business analyst. A strong option if you are good at talking to people and writing things down clearly.

Software development from scratch is absolutely possible, and if you genuinely love building things, do not let anyone talk you out of it. But it is the longest road, and I would only recommend it if the work itself excites you, not just the salary. People who switch purely for money usually burn out before the money arrives.

Why data analytics is the strongest default

Let me make this concrete. A commerce graduate who can do the following is employable:

• Take a messy export of sales or expenses, clean it, and answer a real question ("which products lost margin this quarter and why").
• Write SQL queries with joins, grouping and window functions against a real database.
• Build a Power BI dashboard a manager can actually use, with sensible measures and filters.
• Explain the result in plain language to someone who does not care about the query.

That last point is where commerce people often beat engineers. Analysts are paid for decisions, not charts.

Useful signals along the way include the Microsoft Power BI Data Analyst Associate (PL-300) certification, which is still an active Microsoft credential in 2026, and the Google Data Analytics Certificate on Coursera. Treat both as structure and signal, not as tickets. The portfolio is what gets you the job.

A six month plan for the data analyst route

Around 15 to 20 hours a week, alongside your current job.

Portfolio ideas that use your background:

• An expense and cash flow dashboard for a small business using public or sample data.
• A margin analysis across products and regions.
• A GST or VAT style reconciliation checker that flags mismatches.
• An accounts receivable ageing report that shows which customers pay late.

Each project needs a short write up: the question, the data, what you found, and what a manager should do about it.

How to stay employed while you switch

Do not quit your job to study unless you have at least six to nine months of savings and a very clear plan. Pressure to earn quickly is the fastest way to accept a bad offer or abandon the plan.

Instead:

• Protect your hours. One hour on weekday mornings or evenings and a longer block on the weekend is enough. Put it in your calendar like a shift.
• Use your current job as a lab. Almost every commerce role has spreadsheets and reports. Automate one. Build a dashboard for your team. Suddenly your CV has "reduced monthly reporting time from two days to two hours" on it, from a job you already have.
• Look for an internal move first. If your company has an MIS, finance systems, reporting or IT team, an internal transfer is often the easiest first tech job you will ever get.
• Tell no one you are "leaving commerce". Tell people you are "moving into finance analytics" or "specialising in ERP systems". It is the same move, framed as growth.

Freelancing and remote work as income levers

This is where your salary question gets interesting. The same skills can earn very different amounts depending on who pays you.

• Freelance small jobs first. Excel automation, Power BI dashboards, bookkeeping cleanup and data entry automation are common requests on freelance platforms. Your first projects will be small and underpriced; treat them as paid portfolio pieces, raise rates as reviews accumulate, and never compete only on price.
• Offer your skills locally. Small businesses near you often run on spreadsheets and chaos. A clean reporting setup or an Odoo implementation is worth real money to them.
• Aim for remote roles after you have experience. Remote employers usually want some proof you can deliver independently. A year of local or freelance work plus a strong portfolio makes you a credible remote candidate.
• Build a visible profile. People hire people they have seen. Sharing what you build on LinkedIn every couple of weeks brings opportunities to you. My post on what actually works on LinkedIn for engineers applies just as much to analysts.

Pitfalls that cost people years

• Buying course after course. One good structured course per skill is enough. The rest of the time should go into projects.
• Believing get rich quick promises. No legitimate path makes you rich in weeks. If a programme's marketing is mostly salary screenshots, walk away.
• Chasing every trend. Blockchain one month, AI prompt engineering the next, cybersecurity the month after. Pick one path and give it six months.
• Hiding the commerce degree. Lead with it. "Commerce graduate specialising in financial data analysis" is a strong, clear story.
• Waiting until you feel ready to apply. Start applying by month five or six. Rejections at that stage are information, not verdicts.
• Learning alone. Find a community, share progress, and ask for feedback. Our Discord exists for exactly this.

A final word on prosperity

Prosperity in tech rarely arrives as one big jump. It arrives as a series of steps: the first role that uses your new skills, the first raise, the first freelance client, the first remote offer, the specialisation that makes you hard to replace. Each step is a year or so of focused work.

That can feel slow when you are in the desert. But the desert is temporary if you keep walking in one direction. The people who stay stuck are rarely the ones without talent; they are the ones who change direction every three months.

If you want more reading on the practical side of getting hired, how to apply for software engineering jobs covers applications in detail, and most of it applies to analyst roles too.

Ask your own question

This question, in one form or another, comes to me from people with commerce, engineering and non technical degrees all the time. I am collecting the most common ones, anonymised, with detailed answers in the career questions library.

Student or want early access to the Sefism member area, with a personal learning roadmap and written answers to your own questions? Join the waitlist.

If you would like to talk through which path suits you, I offer free 1:1 career guidance sessions on Topmate.

Stay in touch

• LinkedIn: my main channel for career advice, roadmaps and honest takes on the job market.
• X (Twitter): short, practical thoughts on tech careers.
• Instagram: quick tips and a more personal side.
• Topmate: book a free 1:1 session to plan your switch.
• Sefism Discord: ask questions and learn alongside others making the same move.
• Sefism on YouTube: walkthroughs and talks.

Cover photo by Luke Chesser on Unsplash