Construction is one of the world's most important industries, and one of the most underserved by software. We're building the operating system for construction, bringing together the information and tools builders need to run their business. Come help us let builders build.

📍Melbourne, hybrid - the team is generally in our Richmond office Mon/Wed/Fri, plus time on customer sites and in their offices ⏰ Full time

Why BuildPass?

Builders spend too much time working around spreadsheets, PDFs and paper. BuildPass brings estimating, finance, scheduling, safety and site management into one platform, from the first estimate to the final payment.

Today BuildPass powers:

• 1,000+ head contractors, 100,000+ subcontractors and 500,000+ field workers across Australia, US, Canada, and NZ
• 3.2M+ site sign-ons, 1.5M+ forms, 140k+ drawings and defects logged on real jobs
• An AI layer that works on a builder's live data - agents, MCP and multi-modal assistants - from the finances to the office to the field

We're building a trusted record of a construction business: its people, projects, costs and what's happening on site. That gives AI useful context, and making it work takes a close understanding of how customers operate. You'll work alongside builders and our product and engineering teams to turn that context into workflows people use, and bring what you learn back into the platform. Read the BuildPass method.

The role

As a Forward Deployed Engineer, you'll work directly with customers to understand a problem, build a solution and help them put it to use. You'll sit in Customer Success, partner with CSMs and Support, and work closely with Product, Engineering and AI Operations. Roughly half your week will be spent with customers on calls, on site and in their workflows; the other half will be hands-on building.

The right answer might be a better workflow, a configuration change, a data migration, an integration or an AI automation. You'll help the customer choose an approach, agree what success looks like, and follow it through from discovery to a tested solution they can use. When a change belongs in the core product, you'll work with Product Engineering on a clear brief backed by customer evidence.

Examples of what you'll work on

• Our largest accounts. Be the technical counterpart to CSMs: join the calls, ask the second and third why, and turn vague asks into solvable problems.
• Solutions on and around BuildPass. Build and roll out configuration, integrations with the tools builders already use, data migrations, scripts and AI workflows using BuildPass Agent, MCP and our APIs. Test the result, respect customer permissions and data, and leave clear documentation and ownership for what you build.
• Automation for the customer team. Take the manual work off CS and Support - implementation requests, imports, register setups - with tools, automations and agents.
• Resolve technical blockers. Fix what you can directly, and hand off what you can't with repro steps and evidence.
• The feedback loop to product. Spot patterns across accounts and turn useful solutions into shared tools, templates or product improvements with the relevant team.

What success looks like

• In 90 days: you understand the priority workflows in your first accounts, have delivered a scoped solution customers are using, and can show what changed. You've also identified the next technical opportunities with Customer Success and Product.