Senior Software Engineer

About this role

If you've spent the last few years doing serious payments work inside a big business and you're starting to wonder whether the salary is worth the politics, this might be worth three minutes of your time.

Here's the situation.

A profitable Australian fintech, bootstrapped, no VC, genuinely good margins, is adding a senior engineer to their payments platform team. They build payment gateway technology used by real businesses across Australia, and they're now investing in the people who'll help them take it global.

The work is technically interesting. You'd be working on .NET Core and AWS, including a greenfield integration project and a substantial rewrite, inside a PCI compliance environment. The team is small, distributed, and good. There's no layer of middle management between you and the people making decisions.

Why it might be worth considering a move.
Most senior engineers in payments aren't unhappy with the work. They're unhappy with everything around the work: the approval chains, the meetings about meetings, the distance between what they build and whether it matters.

This business doesn't operate that way. The Head of Engineering is technical, direct, and expects people to think for themselves. You'd get a broad requirement, work out the architecture, and get on with it. That's it.

It's 100% remote. The team spans Australia and Southeast Asia. And the salary is competitive for someone operating at this level.

What they're actually looking for.
Someone with strong .NET and AWS experience who has worked in or around payments before. PCI-DSS familiarity helps. If you haven't worked in a PCI environment before but you're the kind of person who'd go and learn it, that's fine too.

Beyond the technical side: they want someone who can take ambiguity and turn it into a plan. Someone who writes their thinking down, invites scrutiny, and iterates without ego. 3rd-party API integration experience is gen...