Applications and interviews · 6 min read
How to find software jobs in South Africa
Use a small, honest portfolio and search the employer's own engineering and graduate roles.
Software work is not one occupation. A front-end developer, test engineer, data analyst and operations engineer solve different problems, even when a job board places them in one category. In South Africa the employer may be a bank, telecoms company, research body or global technology firm with a local office. Start by choosing a function and reading live role descriptions. Then show evidence that you can do the work, not just a list of languages you have heard of.
Read the job as a set of problems
An employer's own advert is more useful than a generic technology keyword. Amazon's Cape Town careers page shows engineering roles alongside finance and sales, while Vodacom has separate early career routes and a general jobs search. Open the individual role and note the actual tasks, location, experience and work arrangement. A software development role may emphasise design and testing; a support role may emphasise incident response and communication. Do not assume that a broad title tells you the daily work or that a remote label means you may work from any country.
Make a two-column match: requirements you can demonstrate and requirements you need to learn. Essential criteria are not the same as a wish list, but do not ignore a required degree, security clearance or local work authorisation. Where a graduate stream has its own eligibility rules, read that programme's current page rather than applying the rules of a previous year. Save the role URL and exact requisition number before tailoring your CV. This also helps you verify later invitations.
Build a portfolio that survives technical questions
Choose two or three projects that show decisions, not a large collection of unfinished tutorials. For each, explain the problem, users, your contribution, tools, tests and one difficult trade-off. A simple service with clear error handling and documentation can say more than a visually elaborate copy of an existing product. If you worked in a team, identify your part. Never publish a former employer's source code, keys, customer data or internal diagrams. A public repository should be something you have permission to share.
Link to a demo only if it works and the employer can understand what to try. A README should state how to run the project and which limitations remain. If the job is in testing, show how you designed cases and reported a defect. If it is in data, show the data source, cleaning decisions and validation. If it is in infrastructure, explain deployment, monitoring and rollback. A graduate can use coursework but should label it accurately. A self-taught candidate can use the same evidence framework without claiming a qualification they do not hold.
Use South African hiring routes thoughtfully
Search the career pages of employers that build or operate software, not only specialist technology brands. A bank may need developers, cybersecurity staff and systems analysts. A telecoms group may have product, network and technology teams. Public bodies may publish ICT vacancies in the DPSA circular with a different application method. Do not copy one CV across all of these roles: reorder projects and achievements to match the work that each organisation describes.
Check whether the advert is for a permanent role, graduate programme, internship or contractor engagement. Early career programmes can have separate tests and documentation. If an agency advertises a role without the client's name, ask who the legal employer will be and where the work takes place. Keep a tracker of application date, role, portal, contact and outcome. Reopening a previously rejected application with an identical CV is unlikely to add evidence; a new project, qualification or better match may. Work.net.za links to original applications and is free for job seekers.
Prepare for an interview as a conversation about work
Practise explaining your own code or analysis from first principles. Describe the requirement, the design you chose, how you tested it and what you would change. A technical exercise may be less about a perfect algorithm than about reasoning, communication and safe assumptions. Ask what tools and time are allowed, whether you can use documentation and how the exercise will be assessed. Do not pay for leaked solutions or give another person access to your accounts. Verify the invitation through the official employer portal.
If you do not know an answer, state what you would check and how you would reduce risk. Be ready to discuss a defect you found after release, a review comment you accepted or a time you changed your design. These examples are more credible than claiming mastery of every tool in the advert. For a remote interview, test audio, network and access to the exercise beforehand. Keep a local copy of your project notes, but do not share confidential work samples merely to impress the panel.
Evaluate the offer and keep building evidence
Read the written offer for title, legal employer, location, remote policy, basic pay, on-call expectations, equipment, probation and intellectual property terms. If the role includes a rotation or graduate training period, ask what happens afterward. A high salary figure alone does not describe the workload or employment status. Use the employment contract and general Basic Conditions guidance to frame questions about leave and hours. Ask before signing if the arrangement is unclear, especially when work is for a client of an agency.
After a rejection, separate a gap in evidence from a gap in skill. If several employers ask about testing and your project has none, add real tests and document why they matter. If the role requires a qualification or experience you cannot yet show, look for a nearer entry point instead of padding the CV. Follow a small set of genuine employers and learn from their current requirements. Technology names change quickly; the durable advantage is being able to demonstrate how you solved a real problem responsibly.
Sources and further reading
Explore this topic
Frequently asked questions
Do I need a computer science degree?
Follow each employer's current requirements. Some roles specify a qualification; others emphasise demonstrable experience or an equivalent route.
Can I publish a project from my old employer?
Only with permission. Build a separate sample using data and code you may lawfully share.
Is every Cape Town technology role remote?
No. Read the individual advert for the site and work arrangement.
Should I pay for a technical test?
No. Verify the process through the employer's official careers contact.