We have deliberately advertised one role with a wide band, because we would rather meet good people than argue about titles. Where you land depends on what you have actually shipped.
To be in the conversation at all:
- Solid Python, with Git, and enough SQL to check your own results
- You have called REST APIs and handled JSON and webhooks in something you built
- You have built at least one thing with an LLM API and can explain, in detail, where it breaks. Personal projects count. Hackathons count. "I read about RAG" does not
- A degree in computer science, software engineering, AI or data, or the equivalent proven in work
To be at the top of the band:
- 5+ years software engineering, including 2+ years running LLM or agentic systems in production, where "production" means real users and real consequences
- Hands-on RAG: embeddings, vector databases, retrieval design, and the evals that prove quality
- Enterprise integration depth: REST, webhooks, OAuth or JWT. Salesforce experience is a real advantage
- Cloud engineering with Docker and CI/CD. Google Cloud preferred, AWS or Azure welcome
- You have set engineering standards for other people and are happy mentoring a less experienced engineer
- You can sit with a non-technical department head in another country, work out what they actually need, and translate it into a system
Nice to have at either end: multi-agent frameworks (LangGraph, CrewAI), Model Context Protocol, FastAPI, education sector experience, and previous remote work with an international team.
Some of our strongest applicants come from South African software houses and product teams (Entelect, BBD, DVT, Synthesis, Dariel), local scale-ups and fintechs (Takealot, Yoco, Luno, JUMO, Prodigy Finance, Lula), data and engineering teams inside the big insurers and banks (Discovery, Old Mutual, Standard Bank, Momentum), or from remote contracting for overseas clients.
What matters most:
- Self-directed. Remote work makes this non-negotiable. Nobody is going to stand behind you
- Motivated by impact. You want to watch the thing you built change how a business operates
- Comfortable with ambiguity. This function is still being defined and you get a say in it
- Commercially minded. You ask whether the build is worth the time before you start it
- Fast learner. The tooling moves weekly and you enjoy that rather than resenting it
Remote setup requirements:
- A private, quiet home workspace
- Uncapped fibre internet with a mobile data backup
- Backup power (inverter, UPS or generator) able to cover your full working day through load shedding
- Your own machine capable of doing real development work