Senior Full Stack Engineer

Remote within Australia, with the option of working from the Taree NSW office. Full time position. Own the VIABUILD product codebase alongside the founder and ship construction software to production every week. VIABUILD is part of CALDON™ Group, a construction intelligence platform that changes how builders run their businesses.

This position exists to give VIABUILD a second pair of senior hands on the product so the founder is no longer the only person able to build, review and deploy it. The Senior Full Stack Engineer owns the codebase jointly with the founder, ships work to production without supervision, makes architectural calls that hold up as the product grows, and pushes back honestly when something is being built the wrong way. Success means the product keeps moving at speed with fewer defects reaching customers, and the founder can step away from the code for a fortnight without the product stalling.

Reports to: Founder, Oryn Technologies Pty Ltd trading as VIABUILD

What this position owns:

• Build: Core construction management application. Design and ship features across jobs, budgets, purchase orders, variations, progress claims and supplier invoices. Deploy your own work to production and verify it behaves as intended once live. Ship changes that founding builders notice and can use. Write and maintain Postgres schema, migrations and row level security policies that keep builder data separated correctly. Fix defects found by customers ahead of new feature work. Keep the Next.js, TypeScript, Supabase and Vercel stack current and coherent rather than accumulating parallel patterns.
• Extend: Oryn document intelligence and automation. Build and improve the text, vector CAD and vision extraction pipelines that turn builder documents into structured data. Integrate LLM capability into product workflows so it holds up under real customer data rather than in a demo. Measure and improve extraction accuracy on real documents and record what changed. Progress the read-only MCP server and the step graph automation engine from in flight to production ready. Handle failure modes, retries and cost so pipelines stay predictable as volume grows.
• Decide: Architecture and technical direction. Make architectural calls independently when the founder is not available. Write down each significant design decision, the options considered and the reasoning. Review the founder's code honestly and say clearly when something has been built the wrong way. Raise what should not be built and argue the case for cutting scope. Flag technical debt that will bite within the next quarter and propose the fix.
• Communicate: Working well without a shared room. Keep written updates clear enough that the founder always knows what is shipped, what is next and what is blocked. Document how systems work so a third engineer can be onboarded without a handover meeting. Hold a straight weekly conversation with the founder about priorities and trade offs. Respond to production incidents and communicate status and resolution in writing.
• Carry: Production ownership and reliability. Take full responsibility for the product in production, including monitoring and incident response. Run the product end to end for a fortnight without the founder involved. Keep deployment frequent and low drama with small, reversible changes. Reduce the founder's required time in the codebase quarter on quarter. Set up and maintain the guardrails, tests and checks that catch problems before customers do.

The role involves owning the product codebase alongside the founder and shipping to production yourself. The stack is Next.js, TypeScript, Supabase and Vercel. The work spans the core construction management app covering jobs, budgets, purchase orders, variations, progress claims and supplier invoices, plus Oryn, our document intelligence layer running text, vector CAD and vision extraction pipelines. A read-only MCP server and a step graph automation engine are in flight.

What a good week looks like: Meaningful work merged to main and deployed. One or two things shipped that a customer will notice. A real design decision made and written down. And a straight conversation with the founder about what we should not be building.

Where we are: Fifty founding builders are using the product. We are pre-revenue and preparing to raise. Whoever takes this role is joining before it is safe. The person who suits it wants ownership and speed rather than process and certainty. Someone who needs a mature engineering organisation around them will not enjoy it.