We are a small actuarial and data-engineering consultancy. We grow deliberately, hire opportunistically, and pay close attention to the seniority mix on the team. If you are looking for somewhere to build modern engineering practice around actuarial work — with the senior people on it, not the junior people learning on your work — this is the right kind of firm to talk to.
Why people stay
Senior-led delivery
The senior on the engagement is the senior doing the work. Analysts and specialists work alongside senior actuaries, not in their slipstream. The work that comes back to you in review is the work the senior actually has an opinion on.
Modern engineering, real actuarial
Version control, CI/CD, testing, observability and lineage applied to actuarial and reporting work — not as background slogans, as protocols we hold ourselves to on every engagement. You will be expected to use them, and shown how, if it is new to you.
Variety without burnout
Insurance, banking, investments, BI, model validation, AI-assisted workflow design. Our nine practices and five accelerator products mean the next engagement does not have to be the same as the last. The price of variety is that you read regularly and write regularly — we expect both.
Currently open
If you are interested but the specific role below is not a match, scroll to the section after the roles — we keep a standing invitation open.
Actuarial Specialist
Senior-supported delivery on actuarial valuation, IFRS 17 reporting and assumption review across South African life insurers and investment-management businesses. The work is on the real engagement deliverables — statutory valuation, embedded value, close cycles — not background research for a senior to present.
What you would be doing
- Running IFRS 17 close cycles alongside the client actuarial team
- Building and maintaining versioned assumptions registers
- Reconciling actuarial-to-finance lineage on multi-fund books
- Writing methodology notes that hold up under statutory audit
- Communicating findings clearly enough for a board or regulator to act on
What we are looking for
- Progressing through the ASSA exams; TASSA or above is a plus
- 3–7 years in actuarial practice (life, health or general)
- Comfort with IFRS 17, SAM and EV terminology
- A view on where actuarial work needs better engineering
- Willingness to write your own working papers, not delegate them
Data Engineer
Build versioned, lineage-tracked pipelines for actuarial and finance workloads. IFRS 17 ETL, lakehouse build-outs, orchestration and the integration layer that makes reporting reproducible six months later. You will pair with actuaries; your work has named senior actuarial reviewers, not only engineering reviewers.
What you would be doing
- Building ETL and orchestration for actuarial close cycles
- Standing up lakehouse / warehouse data products with proper lineage
- Writing the integration layer between actuarial engines and downstream reporting
- Instrumenting pipelines so failures are visible, not silent
- Explaining what you built to a non-engineering audience — in writing
What we are looking for
- 3–7 years in data engineering
- Python and SQL at production quality
- Working knowledge of one of: dbt, Spark, Airflow, or a major cloud data service
- Reproducibility and lineage treated as first-class concerns
- Either prior financial-services exposure or willingness to learn the domain seriously
If your role is not listed
We hire opportunistically. If you read the rest of this site and recognise the kind of firm you want to be at — even when there is no current opening for your specific profile — tell us. We meet good people roughly twice a year for roles we have not yet posted.
What we are interested in hearing about: what you have actually shipped, what would be different if you had built it again, and what you are trying to do next that you cannot do where you are.
Contract and fractional specialists
We also work with independent actuaries, data engineers, BI specialists and software engineers where the scope is clear and the fit is right. We do not treat contractors as anonymous overflow. A good contract engagement has a named outcome, a named reviewer, access to the context needed to do the work properly, and visible credit for the contribution.
If you are independent and this is the kind of work you want to be known for, use the same expression-of-interest route and tell us where you are strongest.
How we hire
- A first conversation. Thirty minutes, with a senior. Honest on both sides about what the work is, what the firm is, what is missing today.
- A working session. Not a Hackerrank test. We sit with a real (anonymised) problem from a current engagement — a piece of code, a reconciliation, a methodology question — and work it together for an hour or two.
- Meet two more of the team. Including someone you would work with day-to-day, not only the people doing the hiring.
- References, an offer, a start date. We close inside three weeks of the first conversation when both sides want to proceed.