Location: Cape Town, South Africa
Remote: Yes (preferred, any timezone)
Willing to relocate: No
Technologies: TypeScript, Next.js 15, React, Node.js, PostgreSQL, Payload CMS 3.x, Tailwind CSS, Directus, Cloudflare Workers/Pages, Docker, Linux, Git, REST APIs, AI integrations (Claude/OpenAI)
Résumé/CV: Available on request
Email: [email protected]
GitHub: https://github.com/joshuatza
Summary: Senior Full-Stack Engineer with 6+ years of experience shipping production applications end-to-end. I specialize in TypeScript across the stack — Next.js, Node.js, React, PostgreSQL — and I'm most effective when given ownership of a problem and the space to solve it properly.
Most recently, I delivered a greenfield estate administration CRM solo in under 3 months — Payload CMS 3.x, Next.js 15, PostgreSQL, 14 collections, 28 migrations, from zero to production. Before that, I built admin platforms on Directus, contributed to multi-tenant SaaS products, and worked across various contract engagements spanning React frontends, Node backends, and cloud infrastructure.
I care about clean data modelling, sensible architecture, and writing code that the next person can actually maintain. I work well async, communicate directly, and don't need hand-holding.
Currently building two SaaS products on the side (estate administration AI tooling and a consumer cooking app), which keeps my stack sharp and my shipping instincts sharper.
Open to full-time remote contracts, fractional engagements, or project-based work. Billing in USD, GBP, or ZAR.
A few notes on the choices I made: I kept it tight and direct, which tends to land better on HN threads where hiring managers skim fast. The solo CRM delivery is your strongest recent proof point so it leads the experience section. I left the SaaS side projects in because they signal initiative without overshadowing availability. Swap in your actual email and GitHub before posting.
Fascinating approach — using VSA to compress graph traversals into O(1) SIMD operations is a clever way to sidestep the RAG vs graph DB trade-off. Curious about a couple of things: how do you handle fact deletion or correction once something is superposed into the accumulators? And what does the query interface look like from the agent's perspective — is it purely similarity-based via Hamming distance, or do you support structured relational queries too?
A few notes on the choices I made: I kept it tight and direct, which tends to land better on HN threads where hiring managers skim fast. The solo CRM delivery is your strongest recent proof point so it leads the experience section. I left the SaaS side projects in because they signal initiative without overshadowing availability. Swap in your actual email and GitHub before posting.