Full-Stack Developer for Business Insurance Platform
Budget: $20 – $30 NZD
# Senior Full-Stack Engineer (Contract / Freelance) — Tiaki
**Location:** Remote (NZ business; NZ/compatible timezone preferred)
**Type:** Contract / freelance to start, with potential to grow
**Stack:** React, Node, Supabase (Postgres), Vite, deployed on Railway
## About Tiaki
Tiaki is an AI-powered business-risk insurance platform for New Zealand financial advisers, built to operate under the Financial Markets Conduct Act (FSLAA regime). It takes a business through a structured risk assessment and generates the full suite of compliant advice documents — Scope of Service, Recommendation Report, Underwriter Letter, and Statement of Advice — from a single shared data model.
It's a real, working product (live demo, substantial test suite, real domain logic) built by a financial-adviser founder. It's now moving from "works in a demo" toward "advisers rely on it with real client data" — and that transition is what this role is about.
## What I need (the honest version)
I'm a solo founder-operator who ships a lot, fast. The building is going well. What I need is someone to make the **foundation solid** so that what gets built stops shipping subtle bugs and stops being fragile at deploy time. Concretely:
**1. Code review and architectural sanity.**
Review changes before they ship. Catch the class of bug that passes tests but breaks in the real document — cross-record data leaks, state that mutates when it shouldn't, single-source-of-truth violations. Push back on design where it matters.
**2. Test coverage where it's thin.**
The domain/calculation logic is well-tested (~1,400 tests). The UI and interaction layer is not — which is exactly where bugs slip through. I need someone to build a proper interaction/component testing harness (jsdom + Testing Library, and/or Playwright e2e) so that input, state, and rendering bugs get caught automatically, not by me eyeballing generated PDFs.
**3. Deployment and infrastructure hygiene.**
Set up CI/CD so tests and the build run automatically before anything deploys (no more "the server routes didn't get committed" reaching production). Sensible branching, migration discipline (Supabase migrations applied predictably), and a deploy pipeline I can trust.
**4. Build alongside me when needed.**
Once the foundation's solid, help build features — pricing/quoting tools, CRM, the document pipeline — to the same standard.
## What matters to me
- **Correctness over speed, on anything touching numbers.** This is a financial-advice product. A wrong figure on a Statement of Advice is a serious problem. I work with a discipline of "recon before build, prove the dollar-path is safe, single source of truth" — I need someone who respects that, not someone who ships fast and loose.
- **You can read an existing codebase and work within its patterns**, not rewrite everything to your taste.
- **You communicate clearly** — flag what you changed and why, surface risks, ask before guessing.
- **Comfortable working in a codebase where some code is AI-assisted** — you'll be reviewing and hardening, which is the point.
## Nice to have
- Experience with regulated / fintech / insurance products
- Supabase / Postgres depth (RLS, migrations)
- Experience setting up CI/CD from scratch on small teams
- Familiarity with NZ financial-services context (not required)
## How to apply
Tell me about a time you came into an existing codebase and made it more reliable — what you found, what you changed, and how you knew it was better. Include anything you've built or hardened that touched money, compliance, or sensitive data. Links to code or a short note on your approach to testing and review are more useful to me than a CV.
---
*Tiaki handles sensitive business and personal financial data. Appropriate confidentiality and security practices are expected, and references / a short paid trial task are part of the process.*
**Location:** Remote (NZ business; NZ/compatible timezone preferred)
**Type:** Contract / freelance to start, with potential to grow
**Stack:** React, Node, Supabase (Postgres), Vite, deployed on Railway
## About Tiaki
Tiaki is an AI-powered business-risk insurance platform for New Zealand financial advisers, built to operate under the Financial Markets Conduct Act (FSLAA regime). It takes a business through a structured risk assessment and generates the full suite of compliant advice documents — Scope of Service, Recommendation Report, Underwriter Letter, and Statement of Advice — from a single shared data model.
It's a real, working product (live demo, substantial test suite, real domain logic) built by a financial-adviser founder. It's now moving from "works in a demo" toward "advisers rely on it with real client data" — and that transition is what this role is about.
## What I need (the honest version)
I'm a solo founder-operator who ships a lot, fast. The building is going well. What I need is someone to make the **foundation solid** so that what gets built stops shipping subtle bugs and stops being fragile at deploy time. Concretely:
**1. Code review and architectural sanity.**
Review changes before they ship. Catch the class of bug that passes tests but breaks in the real document — cross-record data leaks, state that mutates when it shouldn't, single-source-of-truth violations. Push back on design where it matters.
**2. Test coverage where it's thin.**
The domain/calculation logic is well-tested (~1,400 tests). The UI and interaction layer is not — which is exactly where bugs slip through. I need someone to build a proper interaction/component testing harness (jsdom + Testing Library, and/or Playwright e2e) so that input, state, and rendering bugs get caught automatically, not by me eyeballing generated PDFs.
**3. Deployment and infrastructure hygiene.**
Set up CI/CD so tests and the build run automatically before anything deploys (no more "the server routes didn't get committed" reaching production). Sensible branching, migration discipline (Supabase migrations applied predictably), and a deploy pipeline I can trust.
**4. Build alongside me when needed.**
Once the foundation's solid, help build features — pricing/quoting tools, CRM, the document pipeline — to the same standard.
## What matters to me
- **Correctness over speed, on anything touching numbers.** This is a financial-advice product. A wrong figure on a Statement of Advice is a serious problem. I work with a discipline of "recon before build, prove the dollar-path is safe, single source of truth" — I need someone who respects that, not someone who ships fast and loose.
- **You can read an existing codebase and work within its patterns**, not rewrite everything to your taste.
- **You communicate clearly** — flag what you changed and why, surface risks, ask before guessing.
- **Comfortable working in a codebase where some code is AI-assisted** — you'll be reviewing and hardening, which is the point.
## Nice to have
- Experience with regulated / fintech / insurance products
- Supabase / Postgres depth (RLS, migrations)
- Experience setting up CI/CD from scratch on small teams
- Familiarity with NZ financial-services context (not required)
## How to apply
Tell me about a time you came into an existing codebase and made it more reliable — what you found, what you changed, and how you knew it was better. Include anything you've built or hardened that touched money, compliance, or sensitive data. Links to code or a short note on your approach to testing and review are more useful to me than a CV.
---
*Tiaki handles sensitive business and personal financial data. Appropriate confidentiality and security practices are expected, and references / a short paid trial task are part of the process.*