ABOUT
Junior developer. Accessibility-first. Neurospicy. I build for everyone — because I think differently too.
I think in patterns and pictures, so most of my projects start with design docs broken into phases — usually with a Mermaid diagram or flow chart. Accessibility isn't a separate practice; it's the brief, because building for how I read tends to mean building better for how everyone reads.
What I work with
- Frontend
- React, JavaScript, TypeScript, Astro, CSS, semantic HTML, WCAG 2.2, W3C APG patterns
- Backend
- Express, REST APIs, Integration testing
- Databases
- SQL (SQLite, Postgres via Supabase), schema design, Knex migrations + seeds, indexing strategies
- Tooling
- Vite, Vitest, Playwright, axe-core, Git, Cloudflare Pages, Vercel, Anthropic / OpenAI APIs (used in my Dev Academy ai-chatbot project)
- Practice
- TDD where it helps, scaffold-first learning, design-doc-driven work, accessibility audits. Currently learning: AI agent + worker patterns for the Learning Companion Project.
How I work
I roadmap projects into design docs, flow charts, and diagrams broken into phases — each phase ships something deployable, and I work small pieces at a time. Clean code matters to me; readability and accessibility live at the top of my philosophy. I find code difficult to read myself, so making it easier for me to read tends to mean making the finished result easier for everyone who ends up using what I build.
I match the tool to the shape of the work: Astro for content-shaped sites because it gets out of my way, Next.js when there's real client-side state, Express + Knex when I want to wire the relational layer by hand.
What I am looking for
Junior or graduate developer, Auckland-based, open to remote. Looking for a team where accessibility is the default not the add-on, documentation is part of the work, and there's room to learn the parts of the stack I haven't lived in yet. I'm applying through Summer of Tech 2026/27.
Email [email protected] or grab my CV.