Product Engineer

Workyard puts everything between the job site and the office on autopilot for contractors. GPS-verified time tracking, automatic cost coding, compliance caught before it becomes a problem, and verified data flowing straight into payroll and accounting without anyone touching it twice. Thousands of workers clock in with Workyard every day across construction businesses in the US. We are building a team where the best work of your career happens. Real ownership from your first month, people around you who are exceptional at what they do, and a company small enough that what you build is unmistakably yours.

About us: Workyard was built by a brother-and-sister team who ran payroll for 500+ field workers and couldn't find a single tool that got the hours right, so they built one. Founded in 2018, pivoted from staffing marketplace to SaaS in 2021 when marketplace customers started asking to use the tool for their whole team. Today the company has about 70 people across Australia and the US and is growing fast.

The Role: We don't hire engineers to take tickets. We hire them to build products. You’ll own the lifecycle of delivering products end to end. Shape ideas with Product Managers, build it alongside your engineering peers, ship it, measure it and help decide what happens next. You’ll build for one of the largest industries in the US and one of the least digitized. Plenty of contractors still run payroll off paper timesheets, spreadsheets and a foreman's memory. The rules are hard. Multi-rate overtime, prevailing wage, certified payroll, union agreements and crews moving between job sites every day. Getting that right in software is the work.

What you'll own:

• Understanding how contractors really work. Dig into our customer research, alongside product managers to learn how crews, foremen and office teams run their day.
• Taking products from first conversation to production. Own the full path from discovery through technical design, build, release and every iteration after.
• Making the calls that matter. Decide what we should build, how to build it and what to leave out.
• Holding the bar on good software experiences. Weigh in on design, review code with care and help the engineers around you get better.
• Making the tradeoffs. Balance speed, accuracy and simplicity on every project.

You’ve owned a product end to end. You've taken something meaningful from idea to production, written the code and stayed accountable for whether it worked. Roughly 3+ years building and shipping production software. You’re a strong full-stack engineer. You write clean production code with sound fundamentals. This role needs range with a front-end lean, not deep systems specialization. You design data models that hold up.

You think about how records relate, how they change over time and what happens when an integration sends something messy. You spend time with the people you build for. You have a habit of wanting to understand the people who use what you build, and you can point to things you built differently because of it. You have high standards for simple experiences. Something that technically works isn't good enough. The higher bar is judging if something is simple to use and easy to understand.

You communicate clearly and work well with others. You can explain a technical decision to a customer, a sales rep or an engineer and have each of them understand it. You prototype early. When you have an idea, your first move is to build a rough version with AI tools and test it. You’re comfortable without a map. You work well with loose direction and lots of autonomy.

Who you are: You're an engineer who also is a product thinker. You'd rather understand the research yourself than be handed a spec, and you'd rather ship something rough on Tuesday than something perfect next month. You care about the code, but you care more about whether it changed someone's day in the field. You solve problems with other people, not around them.

This role is not for you if: Working on deep technical problems excites you more than solving customer facing problems. You'd prefer someone else be accountable for the product experience, scoping and planning, you just want to focus on coding. You're not interested in learning how construction, payroll or the business side works.