Full Stack Developer (TypeScript / Next.js)
Summary
Full stack developer building a TypeScript monorepo for a property inspection business across Victoria, NSW and Queensland. Day-to-day work spans CRM core, automations, third-party integrations, AI/LLM features and a React Native inspector app, using Next.js, Hono, Postgres, Drizzle, Redis, BullMQ and AWS.
Salary: $70,000 – $90,000 per year
About Us
We deliver property inspection services across Victoria, New South Wales and Queensland, and we build the software that runs the whole operation ourselves.
It's a TypeScript monorepo covering the full job lifecycle: enquiry, quote, payment, scheduling, inspection, report, delivery and follow up. Around it sit a partner referral program, marketing automation, an in-CRM phone system, an inspector mobile app and an AI layer that enriches customer data. Real money, real customer records, real phone calls.
Why you might like it here: small team, direct access to the founder, decisions made the same day. You'll get business problems to solve rather than tickets with the answer written in them, own real parts of the product, and see your work in use the same week you ship it. Modern stack, no legacy sprawl.
What You'll Do
Take a business problem, ask the right questions, decide what to build, and ship it
Feature work across the stack: Next.js (React 19), Hono API, Postgres
CRM core: contacts, leads, jobs, quotes, invoices, payments, commissions and payouts
Automations on BullMQ and Redis: campaigns, sequences and customer journeys
Integrations: Stripe, Twilio voice and SMS, Clerk, AWS SES, Google Workspace, mapping
AI features: LLM-backed extraction, enrichment and assistants
Schema design and migrations in Drizzle, with Postgres row level security
The Expo / React Native app our inspectors use in the field
Deployment and monitoring on AWS (ECS, CDK, CodePipeline)
What We're Looking For
We need all of the following, so please have a quick read before applying.
3+ years commercial experience shipping to production. Study and personal projects take real work, but this role needs experience gained on the job.
You've built features inside a CRM, ERP, booking, job management or field service system. Commercial (Salesforce, HubSpot, Zoho, ServiceM8, Simpro, Tradify, AroFlo) or custom internal. Building in it counts, using it day to day doesn't.
Strong TypeScript on both sides. A production React front end and a production Node back end.
You own the database. Schemas in Postgres or MySQL, migrations you've shipped, and you can explain why a query is slow and what index fixes it. We have no DBA.
Third party APIs in production, including the messy parts: OAuth, webhooks, retries, idempotency, rate limits, and what happens when the other end goes down.
A shipped feature calling an LLM API (OpenAI, Anthropic or similar) in a real product, and you can talk about prompting, structured output, cost, latency and where the model gets it wrong.
Onsite on the Northern Beaches, five days. Not remote or hybrid.
Full working rights in Australia.
Bonus points: Stripe and money paths · Twilio, SES and email deliverability · AWS (ECS, CDK or Terraform, CI/CD you've maintained) · role based access and multi-tenancy · BullMQ, SQS, cron jobs · React Native or Expo · property, trades or field services.
Our Stack
TypeScript everywhere: pnpm and Turborepo monorepo, Next.js 16, React 19, Hono, Drizzle, Postgres 18, Redis and BullMQ, Biome, Vitest, Docker, AWS CDK, Expo, Clerk, Stripe, Twilio, OpenAI and Anthropic APIs. You don't need all of it on day one, just a rough sense of what each thing is for.
Probably not the right fit if your commercial work has been front end only or back end only, mostly WordPress, Wix, Shopify or no-code, or short agency projects where you never lived with the system you built. Not a criticism, just a different kind of role.
How to Apply
Send your resume with:
Years of commercial development experience, your suburb, and your right to work in Australia
Which CRM or business system you've built features in, and what you built
One hard technical problem you solved end to end: what broke, how you worked it out, what you shipped
What you've built with an LLM API in production, and what changed once real users hit it
A GitHub profile or a link to something live counts for more with us than a cover letter. We'll get back to you either way.