How to Become a Software Developer in South Africa Without a Degree

I spent five years as a warehouse operative at a mine before I wrote my first line of code. No computer science degree, no tech connections, no idea what a "pull request" was. Today I'm a senior software engineer. So when I say you can become a developer in South Africa without a degree, I'm not selling you a course — I'm describing the road I actually walked, including the potholes.

This is the honest, SA-specific version of the roadmap.

First, the honest part

Let's clear the marketing haze:

• It takes longer than the ads say. Twelve to twenty-four months of consistent learning before you're employable is realistic for most people doing this alongside a job. The "become a developer in 12 weeks" pitch is measuring something else.
• The junior market is competitive. Every bootcamp graduate, CS graduate, and career-switcher is applying for the same entry roles, and AI tooling has raised the bar for what juniors are expected to bring. You won't win on paper credentials — you'll win on demonstrable ability, which is actually good news for the degreeless.
• No degree means the burden of proof is on you. Fair or not, you need evidence: things you've built that work. The entire strategy below is organized around generating that evidence.

Companies here do hire developers without degrees — I'm proof, and I've since sat on hiring panels that did it. What they need is a reason to believe you can do the job.

Step 1: Pick one stack and go deep (3–6 months)

The fatal beginner pattern is sampling everything — a week of Python, some JavaScript, a Udemy course on Flutter — and mastering nothing. Pick one path and commit. In the South African market, the safest bets by job volume:

• C#/.NET — banks, insurers, and the large corporates that dominate SA's dev hiring run on it. It's what I chose, and the enterprise demand is steady from Joburg to Cape Town.
• JavaScript/TypeScript (React + Node) — agencies, startups, and remote-friendly work.
• Java — the other enterprise giant, similar market to C#.

Whichever you choose: learn the language properly (variables through OOP, collections, error handling), then SQL (non-negotiable — every SA enterprise job touches a database), then Git, then the basics of the web (HTTP, APIs, JSON).

Free-or-cheap resources are genuinely sufficient: freeCodeCamp, The Odin Project, Microsoft Learn for .NET, CS50 for foundations. What's scarce isn't material — it's the consistency to do 10–15 hours a week for a year. Protect that time like a shift you can't miss.

Step 2: Build proof (3–6 months, overlapping)

Tutorials teach syntax; projects create employability. You need two or three real applications, deployed and public — not to-do lists cloned from a video, but things with your own decisions in them: a booking system for a local business, a load-shedding schedule notifier, a warehouse stock tracker (guess what my first one was).

Each project should demonstrate: a working deployed URL, a database, source code on GitHub with a README that explains why and how, and ideally one feature that was genuinely hard for you. Three of these beat any certificate you can buy, because they answer the exact question the hiring manager is asking: can this person actually build things?

For the full playbook on making projects hiring-manager-ready, I've written up portfolio projects that get developers hired separately.

Step 3: The SA job hunt, specifically

Where the entry points actually are here:

• Learnerships and graduate-style programmes — several SA corporates and consultancies run structured intakes that accept demonstrated skill without degrees. These are gold for career-switchers: they expect to train you.
• Smaller companies and agencies — less credential-focused than the listed corporates, more willing to bet on a strong portfolio and attitude. This is where I got my start.
• Internal moves — if you're employed anywhere with an IT department, the "I taught myself to code, can I automate this spreadsheet?" route is dramatically underrated. Doing small dev tasks in your current job is experience with a salary attached.
• OfferZen, LinkedIn, Pnet, CareerJunction — for the formal market. On LinkedIn, post what you're building as you learn; recruiters here do actually look.

On your CV, lead with projects, not apologies. "Self-taught developer, three deployed applications (links), previously five years' operational experience in mining logistics" reads as determined and grounded, not as "no degree."

And use your non-tech background as the asset it is: you've held deadlines under pressure, worked shifts, dealt with real operations. Enterprises building software for logistics, mining, retail, and finance value people who've lived the domain.

Step 4: Interview prep

Junior interviews in SA are usually: a screening call, a technical assessment (take-home or live coding of fundamentals — arrays, strings, SQL queries, small OOP design), and a culture/team interview. Prepare by re-implementing fundamentals without help, being ready to walk through your own projects in depth (the most common failure I see on panels: candidates who can't explain code they submitted), and having honest answers for "why the career change?" Your story is a strength — tell it with specifics.

What to expect when you land it

Junior salaries vary widely by city and company type — enough to live on, with the real payoff being the trajectory: the gap between junior and senior compensation in SA tech is one of the steepest of any accessible career, and it's climbable in 4–6 focused years. Remote and international work opens up as you grow, too.

The degree question, by the way, evaporates after your first job. Nobody has asked me about my education in years. Experience compounds; the entry barrier is the only barrier.

Five years ago I was checking stock sheets at a mine. The road exists. It's just longer and more ordinary than the ads claim — one consistent hour after another.

Where to go next

• Making the Career Switch — my original decision-point story.
• Switching to a Programming Career at 30+ — for those worried it's too late.
• Your First 90 Days as a Junior Developer — what to do once you're in.