I'm a fullstack engineer based in Cape Town, and right now I'm building Volley, a mobile app for matching squash players, from the ground up. NestJS, Prisma, PostgreSQL, React Native, TypeScript and Supabase, all of it mine to own, from the database schema through to the last pixel. It's the project that says the most about where I am as an engineer at the moment.
Before I went fullstack, I spent close to a decade in high volume, precision driven imaging work. I shot e-commerce product photography under strict production targets at Superbalist.com, then ran imaging workflows as a Senior Photographer at TFG Labs, alongside years of freelance work doing UX focused content. It's part of why I notice when spacing is half a pixel off or a colour doesn't quite sit right, the sort of thing that's hard to teach and easy to spot once you've spent years actually looking at images for a living.
My time at Kurtosys combined hands-on engineering with product training. I translated dense fintech platform workflows into documentation and onboarding that enterprise teams could follow, which did a lot to sharpen how I explain technical decisions to people who aren't technical.
A squash player who builds squash apps. I understand what I'm building because I actually live it, and that's the bit that separates a developer from someone who's just solving a brief.
I'm looking for fullstack, front-end, or product-minded engineering roles where craft and technical depth both matter, not just one or the other.
What sets me apart as a developer
Most engineers need a designer to flag a spacing or colour inconsistency. I usually catch it first.
Because I can judge the code and the visual result at the same time, I get from spec to shipped without the usual back and forth with design. Fewer review cycles, and it looks right the first time.
