Contract software engineer, tech lead and architect for Australian teams
I take remote contract work with engineering teams in Australia as a senior software engineer, tech lead or solution architect. I work from Cape Town, eight to nine hours behind Sydney and six behind Perth.
That offset is the point. We talk at the end of your day, I work while you sleep, and the pull request is there when you start.
What I do on contract
- Tech lead. I join your team and own delivery: planning, pull request review, mentoring, and shipping alongside the engineers. More on how that works.
- Senior software engineer. Hands-on backend and full-stack work in Python, TypeScript, Go, Rust, Ruby and PHP, with Rails, Django and FastAPI on PostgreSQL. More on contract engineering.
- Solution architect. System design, data models, cloud infrastructure on AWS and GCP, and migration plans that ship in steps. More on architecture work.
Most contracts mix the three. I hold the Google Cloud Professional Cloud Architect and AWS Solutions Architect certifications.
What suits this arrangement
- Work with a clear outcome. A migration, an integration, a performance problem, a service to design and build.
- Architecture and review. Design documents, technical due diligence and pull request review, all of which are written work.
- Leading delivery for a team that writes things down. Planning and review run async; the daily call covers the rest.
It doesn’t suit a role built around all-day pairing or constant meetings. If that’s what you need, hire locally.
Relevant work
I built the payment platform and core APIs at Yola as it grew from 10K to 11M users, and architected the backend for BLU Loyalty, a loyalty platform with 9 million users.
I co-founded and sold a software studio after 200+ delivered projects, most of them for clients I worked with remotely, with written specifications and handovers.
My own products are public, so you can read the code first: Craaft, Ecko and Lumen. The full list is here.
Working hours
Cape Town is GMT+2 all year. Sydney, Melbourne and Brisbane are eight hours ahead, and Sydney and Melbourne move to nine during daylight saving. 15:00 to 17:00 in Sydney is 07:00 to 09:00 in Cape Town, and that is our live window each day.
Perth is six hours ahead, which gives a shared half day: 13:00 to 17:00 in Perth is 07:00 to 11:00 for me.
I work async-first and in English, in your tools: your repository, your tracker, your chat.
How a contract starts
With a two-week sprint. We agree the problem, I join your team’s tools and rituals, and I ship something real. At the end of the two weeks we both decide whether to continue. There is no notice period and no exit clause.
After that I work a fixed number of days a week, agreed up front and held.
I invoice monthly from my own company, in Australian dollars, on 30-day terms.
Questions
How much do your hours overlap with Australia?
About two hours a day with the east coast, at the end of your afternoon, and four with Perth. The rest runs async, with written handovers at each end of the day.
Does the time difference slow things down?
For well-specified work it speeds things up, because the work continues overnight. For work that needs constant live discussion it gets in the way, and I’ll tell you if yours looks like that.
Do you also work as a fractional CTO?
Yes. A few days a month of technical leadership works well across this time difference. See the fractional CTO page.
Do you work on site in Australia?
Not day to day. I work remotely, and I travel for occasional on-site visits by arrangement. Roles that need a full-time on-site presence aren’t a fit.
How do you invoice?
From my own company, registered in South Africa, in Australian dollars. I send one invoice at the end of each month for the days worked, payable within 30 days.
Need senior work done while your team sleeps?
Tell me what the team is building and where it’s stuck. We scope it together, I ship something real inside two weeks, then you decide.
GMT+2 · Full EU and Gulf overlap · US East mornings · Singapore afternoons