A complete application in a minute
Tailored resume and cover letter, ready to send.
The Onset, based in Sydney, is building a new payments and billing platform and seeks a Principal Software Engineer from the founding team to shape the architecture and raise the technical bar. This is a greenfield effort where decisions about domain model, APIs, and data flows will drive the product from day one.
You will work closely with the founders, balance shipping with long-term health, and mentor a small team to execute challenging technical problems with high standards.
There are plenty of Principal Engineer roles where the architecture is already decided, the teams are already built and your job is to improve what exists.
This isn't one of them.
I'm working with an early-stage software company building a new payments and billing platform for SaaS businesses. They're assembling a small engineering team around people who have built serious products before and want to do it again from the beginning.
They now want another Principal-level engineer who can raise the technical bar across the business.
The important part is the level.
They don't need someone waiting for a perfectly written requirement, an architecture review board or a Staff+ engineer above them to make the difficult calls.
They need someone who can look at a hard product and engineering problem, understand the trade-offs, decide what should be built and then get involved in building it.
The company is tackling the infrastructure that sits between a software company and its revenue.
That means problems across:
Some of the most important technical decisions are still ahead of them.
You'll have a say in the domain model, service boundaries, APIs, infrastructure, data flows and how the platform should evolve as customers and transaction volumes grow.
Your current title might be Principal, Staff, Senior Staff, Lead, Architect, Founding Engineer or simply Senior Engineer in a company where the bar is unusually high.
More important is what you've actually done.
You'll probably recognise yourself in several of these:
Experience across distributed systems, AWS, APIs, event-driven architecture, SaaS platforms, payments, billing or financial infrastructure would all translate well.
Payments experience is useful, but exceptional engineering judgement matters more.
The attraction isn't having "Principal Engineer" on your LinkedIn profile.
It's the amount of the company you can still influence.
You’ll work closely with the founders and a small group of very strong engineers. There are no layers of management between you and the important technical problems.
You’ll be expected to have an opinion.
You’ll be expected to make calls.
And when something isn't clear, you’ll be expected to help create the answer rather than wait for someone else to provide it.
For the right engineer, that means genuine ownership over architecture and product decisions while the foundations are still being laid.
It also means being part of the group that sets the engineering standard for everyone who joins after you.
Someone who has spent time in a strong engineering organisation, learnt what good looks like and now wants more ownership.
You may have helped take something from 0-to-1.
You may have joined an early company and then lived through the scale-up.
You may currently be inside a large technology business working on complex systems, but you’re increasingly removed from the actual decisions and building.
Or you may simply want to get back to a smaller team where a great engineer can have an outsized impact.
If you're looking for a neatly defined role with established boundaries, this probably isn't it.
If you want to help make the decisions that define a product and engineering organisation from the ground up, it's worth a conversation.