Breaking into SA tech as a junior or career-switcher

Right now we're tracking 3,286 entry-friendly tech jobs across South Africa. That's roles where the listing genuinely accepts juniors, learnerships, or career-switchers, not the usual "junior with 5 years experience" wishful thinking.

Browse them here →

How to spot a real junior listing

"Junior developer with 3–5 years experience" is not a junior role. It's a mid-level role with junior pay. Skip those: they're wasting your application energy.

A genuine entry-level listing usually has at least one of these signals:

• "0–2 years experience" or "recent graduate" stated clearly.
• A learnership or graduate programme name in the title.
• "Will train" or "no prior commercial experience required".
• "Bootcamp graduates welcome" or "portfolio considered in lieu of experience".

Use the Entry level filter on our jobs page; we flag listings that genuinely signal junior-friendliness, so you don't have to read between the lines on every one.

What to learn first

Pick one stack and get genuinely productive in it. Don't try to learn React and Django and AWS and SQL and TypeScript in parallel. The fastest path to a first job is being clearly competent in a narrow area.

For SA junior roles, three high-yield options:

• Frontend: HTML/CSS/JS → React or Vue → TypeScript. Lots of junior postings. Portfolio matters most.
• Backend: Python (Django/FastAPI) or Node.js → SQL → a deployed project. Slightly fewer junior postings, but better progression.
• Data analytics: SQL → Excel/PowerBI → one BI tool. Excellent crossover path for career-switchers from finance or operations.

Where to find junior-friendly companies

• IT consultancies and systems integrators are often the most consistent junior hirers: they need volume and tend to have structured graduate intakes. Look for phrases like "graduate programme" or "cadet" in the listing title.
• Banks and large financial services firms run formal tech academy and graduate programme cycles, often open to non-CS degrees. These usually open once or twice a year. Worth tracking their careers pages directly.
• Learnerships and coding schools (government-backed and private) are not jobs, but they're one of the most reliable pipelines into a first role. Completing one significantly improves your odds. Many SA companies hire from their alumni pool specifically.
• Startups and product companies hire more sporadically at junior level but tend to offer better mentorship and faster progression. Filter by "Entry level" on the jobs page and look for smaller company names you don't recognise. Big brand companies get flooded with applications.

Build something real ✦ and make AI part of how you built it

A deployed project that works beats a perfect codebase that doesn't exist. But in 2026, the bar has moved. Hiring managers aren't just asking "can this person ship something?" They're asking "can this person ship something competently with AI tools?" A todo app built without touching an LLM signals you haven't been paying attention.

For dev roles specifically, you need to show AI-assisted development as part of your workflow, not an afterthought. That means using tools like Cursor, GitHub Copilot, or Claude to build faster, and being able to talk about how and where you used them, what worked, and where you still had to think carefully yourself.

For non-dev tech roles (data, QA, ops, business analysis), the bar is slightly different: show that you can automate things, build simple tooling, or use AI to cut down manual work. A dashboard that pulls live data, a script that automates a report, a workflow you built in a no-code tool. All of these count.

• Host it somewhere live (Vercel, Netlify, Render; all have free tiers). A GitHub link alone isn't enough; recruiters rarely clone and run.
• It doesn't need to be original, but it needs to be real. A functional app that solves a small actual problem is more compelling than a half-built ambitious project with no working demo.
• Write a short README: what it does, what you used, how AI tooling helped, and what you'd improve next. Explaining your process signals self-awareness; most junior candidates skip this entirely.

Your CV as a junior

Keep it to one page. Junior CVs that run two pages signal poor judgement, not experience. The sections that matter:

• Skills: List the specific technologies you can actually use, not every tool you've touched once. If you'd struggle to answer an interview question on it, leave it off.
• Projects: One to three entries, each with a link, the tech used, and one line on what it does. This section matters more than your education for most junior dev roles.
• Education/training: Degree, bootcamp, learnership: whatever applies. Include completion date. SA employers increasingly weight portfolio over credentials for junior hires.
• Drop the "About me" paragraph. Replace it with a one-line summary: what you can do and what kind of role you're looking for.

Remote work as a junior: think carefully

Remote roles exist at junior level and it's tempting to filter for them. But fully remote is often harder to grow in when you're starting out. You learn faster sitting near people who've been doing the job for years. Asking a quick question over someone's shoulder, watching how a senior works through a problem: that's hard to replicate over Slack.

Hybrid roles (a few days in the office) are often the better trade-off early in your career: you get the mentorship benefit without commuting every day. Don't rule out in-office roles in your city if the company or team is strong. The learning return can be worth it for year one.

When you're not getting callbacks

If you're sending applications and hearing nothing, the problem is usually one of three things:

• You're applying to the wrong roles. Check if the listings you're targeting genuinely say "entry level" or "junior". Mid-level roles disguised as junior are common and will filter you out at the CV stage regardless of effort.
• Your CV isn't getting through the first 10 seconds. Recruiters scan quickly. If your skills and a link to a project aren't visible in the top third of the page, they've already moved on. Restructure, don't just rewrite.
• You don't have anything to show. Even a simple deployed project changes the conversation. "I built X and it does Y" is a hook. A list of courses completed is not.

Give any single change three to four weeks before deciding it's not working. The job search has a lag; the feedback loop is slow.

How to actually apply

• Quality over quantity. Five well-tailored applications a week beats 30 spray-and-pray. Personalise the cover note for each role. Most juniors don't, which makes it easy to stand out.
• Read the listing's must-have skills and mirror the language back in your application. Not as keyword stuffing; as honest alignment. If they want SQL and you know SQL, say so explicitly with an example.
• Follow up after applying. Send a short LinkedIn message to the hiring manager or recruiter named in the listing. Most juniors never do this. It moves you from a passive application to a name they've actually seen twice.
• Track what you've sent. A simple spreadsheet with company, role, date applied, and status stops you applying to the same role twice and helps you spot patterns in what's working.

The harder truth

Junior tech hiring in SA is competitive. After a period of aggressive hiring, many companies pulled back and are now leaning toward experienced hires. That doesn't mean junior roles don't exist (they do) but it means you need to be strategic: target companies and sectors that hire juniors as a matter of course, not as an exception.

The good news: once you have 12 months of commercial experience, the next move gets dramatically easier. The first job is the hard one. After that, you're inside the industry.