Product Lead

Lead a product end-to-end: the clients, the roadmap, the code, the design. This is one of the first hires into the new Product team we're building at InDebted, organised into pods built for an AI-native way of working.

Reports to: Head of Product

Location: Sydney (hybrid, 3 days: Tue/Wed/Thu)

Start: As soon as possible

ABOUT THE ROLE

InDebted is a digital-first collections platform operating across seven markets. We've replaced call-centre collections with software, AI and empathy. Now we're building the Product organisation that fits how InDebted operates today: self-contained product pods, small end-to-end teams that lead a product fully, including its client relationships.

Receive is our first-party receivables product. It's coherent and important, which is why it's the right place to start. You'll be the product lead for Receive end-to-end, and the patterns you set here become how product works across InDebted.

Receive serves two very different people: the clients who configure and rely on it, and the consumers on the other side, who are often managing a debt at a stressful moment. Building something that works for both, and treats people fairly when it matters most, is the heart of the job.

The short version: you lead the Receive product. You're the main product point of contact for clients, you drive the roadmap with engineering and the Head of Product, and you bring a builder's bias to action. The role goes beyond traditional product management. It brings together design and direct customer engagement, because in an AI-native world those aren't separate jobs any more.

WHAT YOU'LL LEAD

Clients. You partner with the Receive sales executive on each client, with a clear split. They lead commercial conversations: pricing, growth, contract, expansion. You lead product conversations: usage patterns, feature feedback, configuration, technical escalations and the product side of business reviews. You're introduced during the sales cycle and stay on as the client's primary product contact. The systems that hold those relationships together sit with you too: CRM workflows, client-facing documentation, self-serve portals and AI-powered tooling. When a support process is manual and painful, you automate it. When a question gets asked five times, you ship documentation.

Discovery. Good product calls start with understanding people, not just collecting their requests. You talk to clients about the jobs they're trying to do, and build a real feel for what the experience is like for someone managing a debt. Because this is collections, that understanding carries weight: fairness, consumer protection and the rules that apply are a design input from the start, not a compliance step at the end.

Product. You drive what we build next, in partnership with the Receive engineering team and the Head of Product. You hold a clear thesis for where Receive should go, size the opportunities and are as comfortable deciding what not to build as what to build. There's no extra layer between you and the engineers: you do the product work directly, shaping the experience for both the clients who configure Receive and the consumers who interact with it.

The numbers you'll move. Product performance is the headline: collection rates, platform usage, feature adoption. Then client outcomes: NPS, time-to-resolution. Then how the pod runs: time from client feedback to shipped change, and the share of support handled by AI. You move these deliberately, forming hypotheses and testing where you can, and you know the difference between a number that moved and a change that caused it.

WHAT YOU'LL BUILD

How close you get to shipping production software varies piece to piece. Some work is yours end-to-end, some you'll start and engineering will finish, some engineering leads and you contribute. We're deliberately not drawing that line hard, because in an AI-native team it only keeps blurring. What matters is that the pod ships and customers get what they need.

Representative examples:

• A feedback-to-product pipeline: capture client signal from email, chat, calls and the product, AI-triage by theme and severity, surface a weekly prioritised brief. Likely yours end-to-end.
• An AI-powered product support loop across questions, bugs, config help and escalations: detect, classify, respond, fix, communicate. Built with engineering.
• A client-facing self-serve layer: docs, dashboards and setup flows that reduce per-client support load. You'll likely design and ship most of it.
• A business-review toolkit: AI-generated client summaries, usage data and opportunity briefs.
• Product features: sometimes you'll prototype end-to-end and the prototype becomes the spec, sometimes you'll build the first cut and engineering takes it the rest of the way.

Claude Code is the daily driver. You use Claude Code or equivalent AI coding tools as a native part of how you work, going from idea to working artifact in hours, not sprints.

WHO YOU ARE

We care more about what you've shipped than the title you did it under.

The builder mindset. You've built working things, whether you came to it through engineering, design or data. You're comfortable in a repo, you can go from idea to working artifact in an afternoon, and you use AI tools natively. When something needs building, you're hands-on rather than handing it off.

The client bar. You can be the face of InDebted to a client's operations, finance or compliance team. You write well, you run a meeting and you hold your own with a Head of Collections or a CFO, because you know front-line feedback is where the best product decisions come from.

The product instinct. You start from the problem, not the feature. You can run discovery, separate signal from noise, frame a sharp thesis and prioritise hard under real constraints. You're fluent with data and experimentation, and you care about doing right by people in a vulnerable moment, which in collections is both an ethical bar and a product one.

The shape of you. Deep in one of engineering, design or data, and genuinely curious across the other two. Frustrated by the gap between "client said" and "engineering shipped", and want to close it yourself. Comfortable owning the product without a PM layer above you.

HOW THIS DIFFERS FROM A CLASSIC PM ROLE

This role is more hands-on than a typical product management job. Specs, roadmaps and stakeholder work still exist, but they're a means to an end, not the centre of gravity. The centre of gravity is building. If the part of product you love most is the making, you'll feel at home.

You don't need to tick every box. If you're strong on the core, which is building, product judgment and being great with customers, and excited to grow into the rest, we'd love to hear from you.

HIRING PROCESS

Three stages, designed to assess what you actually do.

1. Intro. A 30-minute call with the Head of Product, a two-way filter on the role and the profile. If you progress, we'll share the Stage 2 brief two days ahead.
2. Product problem deep dive. Two hours in the Sydney office with the HoP and a Receive engineer, working a real Receive-shaped problem you've had for two days. Bring a written thesis and a supporting artefact (prototype, mockup or data sketch). Roughly 30 min walk-through, 60 min challenge, 30 min on how you worked. No unpaid take-home.
3. Final panel. Around 45 minutes with engineering leadership and the founder, scheduled separately and usually remote.
4. Offer typically within 72 hours of the final panel.

HOW TO APPLY

Send your resume and profile to ***email_hidden***.

Tell us two things:

1. Something you've shipped that you're proud of (code, design, data or product). Just tell us what it was, your part in it and why it mattered. Under NDA? Describe it at whatever level you can.
2. Why this role, and the first thing you'd want to build if you got it.

####

InDebted is an equal-opportunity employer. We hire on the strength of what you can do and welcome applicants of every background. Need an adjustment to the process? Tell us and we'll make it happen.