Early, small, and hiring slowly

Paystruct is in early access and the team is small. There are no listed roles at the moment. If Australian construction, security of payment or building software people rely on is your ground, we would still like to hear from you.

Make an approach

There are no open roles today

We would rather say that plainly than keep a page of positions that do not exist. When roles do open, in engineering or in working with the businesses using Paystruct, they will be listed here.

Hiring is limited while Paystruct is in early access.
Speculative approaches are read, and kept on file.
If there is nothing that fits, we will say so rather than leave you waiting.
Roles are listed on this page when they exist. There is no separate list.

People who have felt the problem, or who cannot let a detail go

People from construction

Contract administrators, quantity surveyors and project managers who have run a claim cycle, chased a payment schedule that never came, and watched a claim fail on a date. You know what the document has to survive.

People from law

Construction and security of payment practitioners. A good part of the work is turning a statutory requirement into a check software can make honestly, without overstating what it has actually established.

Engineers who care about correctness

The product is dates, arithmetic and documents. Nearly right is wrong. If the edge case is the part of the problem you find interesting rather than annoying, this is that kind of work.

People who will talk to users

Nobody here is far from the people running claims. The people who build Paystruct are the people who answer support, and that is not going to change.

Narrow, deep, and unglamorous

This is not a broad product. It does one thing for one industry in one State, and the difficulty is in how exact it has to be. Most of what makes it good is invisible until the day somebody disputes a claim.

See what that looks like

Reading the Act and the cases decided under it, then writing checks that can be defended.
Counting business days with Queensland public holidays and the December shutdown.
Pulling payment terms out of contracts that were never written to be read by software.
Getting a claim onto A4 so the person who has to respond to it actually can.
Keeping the record of what was served, when, to whom and by what method.
Saying clearly when the product does not know, instead of guessing.

Write to us anyway

There is no formal process, no queue and no recruiter. Use the contact page and tell us what you would want to work on.

Go to contact

Say what you have done

Not a cover letter. What you have worked on, what you were actually responsible for, and anything we can look at.

Say what you would own

Point at the part of the work above that you want. Being specific is worth more here than being broadly enthusiastic.

Have a look at the product

Set up a contract and build a claim. The first contract is free, and it will tell you more about the problem than this page can.

Expect an honest answer

If there is nothing open, we will tell you that and keep what you sent. If something opens that fits, we will come back to you.

Not looking for a job?

Some of the most useful things you can send a product like this have nothing to do with a job: a contract administrator explaining how their claim cycle really runs, or someone pointing out where the product is wrong about the Act. That is welcome, and it goes to the same place.

Other ways in

Read why Paystruct exists before you write.
Use it. Early access is free and there is no credit card.
Tell us where it is wrong. Corrections about the Act are taken seriously.

See what you would be working on

Setting up a contract and building a claim takes less time than writing to us about it, and it is free while Paystruct is in early access.

Get started Talk to us