Now
Tech Lead on data-heavy backend systems. I own planning, estimation, technical decisions, and delivery. I do the majority of the backend work myself and coordinate a project manager, a senior frontend engineer, and a senior backend engineer.
Cape Town, South Africa · globally remote · SAST (UTC+2)
Tech Lead · Senior Backend / Software Engineer
Production systems · data pipelines · APIs · cloud · AI-assisted engineering
Globally remote Senior / Lead backend · Cape Town · SAST
Now
Tech Lead on data-heavy backend systems. I own planning, estimation, technical decisions, and delivery. I do the majority of the backend work myself and coordinate a project manager, a senior frontend engineer, and a senior backend engineer.
Focus
Globally remote Senior, Lead, and Staff-track backend roles. Production systems, data pipelines, APIs, cloud, and AI-assisted engineering.
01
Paid production first. Homelab is labelled practice.
current
The South African wine industry needs import, export, and domestic data in one production system. Source of truth for a large cut of that data is a legacy Mapper system. The business depends on that data landing correctly every month, and on import/export jobs completing.
Tech Lead. I do the majority of the backend. I own the destination database and application path: monthly synchronisation from Mapper into our MySQL (tables over two million rows), import/export jobs, and recovery when a run fails. I own planning, estimation, technical decisions, and delivery, including annual feature phases (major domestic-data work in 2026).
Treat Mapper as the client's legacy extractor; own load, schema, validation, and repair on our side so a failed month can be traced through PHP and MySQL instead of guessed.
I coordinate a project manager, a senior frontend engineer, and a senior backend engineer. I am the client-facing technical owner.
Monthly Mapper syncs and wine-industry import/export continue in production on tables over two million rows. Failed jobs get a recovered data path. Annual phases, including 2026 domestic data, ship under this lead.
current
A production PHP product had to stay up for a client I own. The original on-prem host failed. Delivery still needed spec, cost, and sign-off, not only tickets.
I own the client relationship for engineering: planning, estimation, technical decisions, and delivery. I operate the application and guest OS.
On hardware failure I containerised the legacy app with Docker on spare CentOS and restored publishing the same incident. The app now runs on an Azure VM; I operate the guest OS.
Client-facing owner. Pull requests and a post-deploy health window.
Production restored after host failure; still running. Delivery loop from spec to sign-off remains mine.
hosted
A production PHP fleet needed a rebuildable AWS environment.
Freelance with a friend. Terraform for the stack in af-south-1.
Environment in code: compute, RDS, pipeline.
Shared freelance delivery.
Live at fleet.wiums.co.za. Public repo github.com/EttieneW/tf-fleet-iac.
homelab
No industry Kubernetes cluster at work.
Private streaming stack; I treat uptime as my problem.
Docker on Linux; k3s/k3d to practise cluster failure.
Solo.
Homelab only — not paid production Kubernetes.
02
Kubernetes (k3s) and Terraform are listed under skills as homelab / freelance.
03
April 2022 – Present
Tech Lead and Senior Backend Engineer
June 2018 – March 2022
Backend / Software Engineer
04
05
I am applying as a Tech Lead and senior backend engineer — eight years in production, currently leading SAWIS BI. That system holds South African wine import, export, and domestic industry data. Each month we synchronise from a legacy Mapper pipeline into our MySQL database; some tables exceed two million rows. I do the majority of the backend, I coordinate a project manager, a senior frontend engineer, and a senior backend engineer, and I own planning, estimation, technical decisions, and delivery, including annual phases and the 2026 domestic-data work.
I like hard debugging: when a sync or import fails I follow the data, not the ticket title. On Indawo, when the host died I containerised the app with Docker and brought production back. I hold AWS DevOps Engineer Professional and I run Linux, Docker, and CI/CD in production. I use Cursor, Grok, Claude, and Codex every day as engineering tools — not as a substitute for owning the system.
I work globally remotely from Cape Town (SAST). Production languages today are PHP and SQL; I learn the house stack on the job.
Thank you. I would welcome a conversation.
06