Senior Software Engineer, Risk & Compliance

About Us

Hello Clever is building the next generation of payments and loyalty infrastructure by turning every transaction into growth for merchants.

We’re an AI-powered fintech operating across 26+ markets, helping businesses move money in real time and convert payments into measurable outcomes like higher repeat rates, bigger baskets, and smarter customer engagement. Our platform combines local account-to-account rails, embedded cashback and loyalty products, and powerful data intelligence through Clever AI, so merchants can launch offers, optimise ROI, and scale faster, all through a single integration.

We recently crossed $70M in live ARR and are on track to pass $100M by the end of 2026-just 2.3 years after reaching our first $1M. It’s an exciting milestone that reflects the scale of what we’re building and the opportunity ahead.

We’re also proud to be recognised on the global stage, including being named Australia’s fastest-growing fintech, recognised in Forbes Asia’s Top 100, ranked among the AFR Fastest-Growing Companies, and selected for Inc. Magazine’s Best in Business.

The Role

You will own technical delivery of risk and compliance initiatives within our Integration team, working directly with Compliance stakeholders to understand their workflows and turn requirements into production software.

This is a hands-on engineering role spanning internal interfaces, backend services, data flows, and third-party integrations. You will improve existing systems and build new tools where needed, taking work from problem definition through implementation, release, and ongoing operation.

Compliance retains ownership of compliance policy, screening rules, configuration, and risk decisions. You will own the engineering that makes those controls work reliably, provide technical evidence and recommendations, and help Compliance operate the systems effectively. This is not a compliance-officer, investigator, people-management, or general cybersecurity role.

Key Responsibilities

Our initial priority order is merchant KYB, transaction screening and monitoring, investigation tooling, supporting vendor integrations, and compliance reporting. Integrations will be delivered alongside the workflows that depend on them.

• Merchant KYB Workflows: Build and improve Know Your Business workflows for merchant onboarding, including information collection, screening-provider integration, status visibility, and review handoffs.
• Transaction Screening & Monitoring: Connect payment and transaction data to risk and compliance systems. Improve data completeness, timeliness, and accuracy, and implement Compliance-approved controls across relevant payment flows.
• Internal Investigation Tools: Build interfaces and workflows that give Compliance the merchant, transaction, alert, and case context they need. Support review queues, investigation history, escalation, and traceable decisions without replacing Compliance judgment.
• Vendor Integrations: Implement and maintain integrations with verification, screening, and transaction-monitoring providers. Own API and webhook handling, data mapping, failure recovery, and visibility into integration health.
• Compliance Reporting: Build reliable dashboards and reports for KYB turnaround, manual workload, alert outcomes, and monitoring coverage. Make reporting definitions and underlying data traceable so Compliance can understand and use the results.
• Monitoring Quality: Investigate technical causes of noisy or incorrect alerts, such as incomplete data, duplicate events, or mapping errors. Support Compliance with evidence for evaluating rule effectiveness; rule and configuration changes remain under Compliance ownership and approval.
• Production Reliability & Controls: Build appropriate access controls, audit trails, testing, and monitoring for sensitive workflows. Make processing failures and coverage gaps visible, document recovery procedures, and help resolve production issues with the Integration team and vendors.
• Cross-Functional Delivery: Work with the Integration Team Lead and Compliance to prioritise initiatives, define acceptance criteria, and plan safe releases. Document systems, train internal users, and remain accountable for technical quality after launch.

What Success Looks Like

In the first six months, success means observable progress against agreed baselines:

• Less manual work: Compliance spends less time on repetitive data entry, copying between systems, and preparing routine reports.
• Faster merchant KYB: Avoidable waiting and rework decrease, with clearer onboarding status and handoffs, without bypassing required checks or approvals.
• Fewer false positives: Technical sources of incorrect or duplicate alerts are reduced, with Compliance validating improvements against monitoring coverage and detection quality—not simply a lower alert count.
• Better reporting: Compliance can reliably see KYB progress, workload, alert outcomes, and monitoring coverage using consistent definitions and traceable data.
• Dependable operations: New workflows and integrations are used in production, with visible failures, documented recovery paths, and clear technical ownership.

Specific targets will be agreed with the Integration Team Lead and Compliance after establishing current baselines and confirming delivery priorities.

What You Bring

• Experience independently designing, shipping, and operating production software as a senior engineer.
• Strong backend and integration engineering skills, including APIs, webhooks, relational databases, background processing, and asynchronous workflows.
• Ability to build usable internal web interfaces as well as the services and data flows behind them.
• Sound judgment about data integrity, duplicate and out-of-order events, third-party failures, and safe recovery in systems that handle sensitive information.
• Experience turning operational workflows into maintainable software by working directly with the people who use it.
• Production engineering discipline: focused testing, observability, clear documentation, careful releases, and ownership of issues after launch.
• Ability to translate Compliance requirements into technical designs, explain trade-offs clearly, and work within defined approval and decision boundaries.
• Clear written and verbal communication in English for collaboration with distributed engineering and Compliance stakeholders.

Bonus Points

• Experience in payments, fintech, banking, or another regulated environment.
• Experience with merchant KYB, KYC, AML screening, sanctions screening, fraud prevention, or transaction-monitoring systems.
• Experience building analyst workspaces, review queues, case-management workflows, or operational reporting.
• Experience with backend application frameworks, event-driven integrations, and SQL-based reporting.
• Experience working with verification or screening vendors and diagnosing issues across application, data, and external-service boundaries.

Why Join Hello Clever

• A clear operational problem: Build tools that help Compliance spend less time moving information between systems and more time on work that requires judgment.
• End-to-end ownership: Shape and deliver workflows across internal interfaces, services, integrations, and production operations.
• Direct stakeholder access: Work within the Integration team and directly with the Compliance teams using your software.
• Payments impact: Improve the systems behind merchant onboarding and payment-risk monitoring while protecting control quality and customer trust.