Software Engineer

What the role involves

Merion's platform is purpose-built. There is no off-the-shelf debt recovery software that does what we need, so we built our own: a case management CRM, a secure client portal that gives creditor clients real-time visibility of their accounts, debtor-facing payment and communication tools, OIDC-based authentication infrastructure, AI-assisted correspondence drafting, and the reporting layer that ties it all together.

Engineering roles at Merion work across the full stack. Backend APIs, frontend interfaces built with modern web frameworks, infrastructure, security — the team is small enough that the boundaries between those areas are permeable. What we build is used every day by the people who sit alongside the engineering team. When something is broken or slow, the feedback loop is immediate.

That proximity to the operational team is one of the genuine advantages of a small engineering team. Requirements come with context. The person who wrote the spec for a feature can explain the edge case verbally, in real time. Engineers here understand what the tools they are building are actually for — and that understanding improves the quality of the work.

Security and compliance as first-class concerns

The platform handles sensitive financial and personal data governed by the Australian Privacy Act and the Australian Privacy Principles. It supports a regulated business operating under ASIC and ACCC oversight. That regulatory context is not background colour — it shapes engineering decisions at every level, from data architecture to access controls to audit logging to how correspondence is drafted and stored.

Engineering at Merion is not a place where security and compliance are treated as someone else's problem or bolted on at the end. Every member of the engineering team understands the regulatory environment the platform operates in and takes responsibility for building within it. That expectation is set at onboarding and maintained consistently.

The skills this role requires

Web application development — both backend APIs and frontend interfaces — is the core capability. API design matters: the client portal, the payment tools, and the operations interfaces all depend on clean, well-documented, consistent APIs. Security awareness is not a specialist skill that only security engineers need; it is expected across the team.

Data handling discipline — knowing how personal and financial data should be stored, transmitted, and accessed — is essential. Collaborative working with non-technical teams is equally important. The operations and recovery teams are the primary users of what engineers build, and building well means understanding their workflows, not just their feature requests.

Small team, genuine ownership

A small engineering team means there is no abstraction layer between the engineer and the product. There are no separate product, QA, and DevOps functions to defer decisions to. Engineers here own their work — from design through to deployment and support. That is demanding and rewarding in roughly equal measure.

Engineers who want to understand the business they are building for — not just ship tickets — will find this environment suits them. Engineers who prefer to work behind a well-defined interface with clear separation from operational concerns will find it harder.

A note on this page

This is a role type description — not a current job posting. Merion does not publish vacancy listings. If your background suits this role type, register your interest and tell us what you have built and what you want to work on. We will be in touch when a relevant requirement arises.