Product Lead at InDebted

About the Role

We are building a Product team fit for a new way of working.

InDebted is the collections infrastructure company, with a suite of products designed to work as one system, including AI agents that write to customers, check every message for compliance and increasingly speak with them by voice. We're building the most intelligent collections platform in the market, leading the industry toward autonomous collections. Doing that in a regulated industry, with people who are often under real pressure, takes judgement, and that judgement is the part of the job we're hiring for.

The way product teams work has changed incredibly over the last year, and it will keep changing. Teams are smaller and AI does a growing share of the building. We've gone all in on it across R&D, and we're reshaping the Product team at InDebted to fit.

What You'll Do

The work, from strategy to what ships.

• Work with the Head of Product and the Founder to develop the product strategy and roadmap, aligned to the company goals
• Define what the pod builds and how you'll know it's done. Sometimes that's a document; often it's a working prototype you've built with Claude Code that morning
• Run discovery: client and consumer interviews, competitive analysis, data analysis
• Partner with engineering on delivery, and drive the sequencing so the highest-impact work ships first
• Own the user experience, for the clients who configure our products and the customers who use them
• Find the manual work in how we build product and how our clients use it, and use AI to remove it. That's part of the job, every week
• Collaborate with stakeholders across Sales, Client Success, Operations and Marketing
• Be the voice of the product, internally and with clients
• Lead go-to-market planning and launch readiness

Who You Are

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

• AI-native. Claude Code, or something like it, is how you work every day. You go from idea to working artefact in hours, and you know what the tools are good at and where they still need you. This matters more to us than any particular product background
• A builder. You've shipped working things yourself, whether you came to it through engineering, design or data, and you're comfortable in a repo. Given an idea, you'd rather have a rough working version by the afternoon than a spec by the end of the sprint
• Proven track record of shipping products that moved business metrics
• Strong analytical skills. When you have a question about the data, you answer it yourself
• Excellent written and verbal communication; comfortable in the room with senior leaders, ours and our clients'

What Success Looks Like

How we'll know it worked.

• The numbers move. Self-serve resolution up, recovery up without a rise in complaints, cost to collect down. Each one traceable to work you led.
• The loop is fast. Idea to shipped in days. Prototype before spec. Something a client asked for last month is live this month, and AI does a measurable, growing share of the work.
• The pod feels it. Engineers say their pod moves faster with you in it, and it ships without waiting on you. When you kill work or make a contested call, the trade-offs are clear enough that nobody needs to escalate.

What This Role Is Not

So you can tell quickly whether it's for you.

Traditional product management. If you love roadmap documents and meticulously crafted PRDs, or your job has been translating between business and engineering, this will frustrate you. That work still exists here, but it's a small part of the role. It's also not a role where AI is optional. Using AI tools day to day is central to how we build.

Hiring Process

Three stages, built around the work.

• Stage 1: Intro. 30-minute call with the Head of Product. We talk about you and the role, and both of us work out whether it fits. If you progress, we share the Stage 2 brief two days before your in-office visit.
• Stage 2: In the office. Two parts, in one visit to the Sydney office. First, a situational interview: we'll walk through real situations you've handled and how you'd handle ours. Then a Product Problem deep dive with the Head of Product and an engineer, on a real problem from our current roadmap. We want to see you work through it with us in the room: how sharp the thinking is, how you get there, the partnership with engineering, how you handle pushback.
• Stage 3: Final chat. A conversation with the CTO and the Founder, scheduled separately and usually remote. Their job is to see the spark we've seen in the earlier rounds. Offer typically within 72 hours.