Explore life at Finch for more.

What you’ll do

Finch’s product serves three groups, and each one has to succeed for us to keep growing:

• Operators: our case managers, who work alongside AI agents on every case. They need agents to handle more on their own, a fast way to verify that work, and a clear next action on every file.

• Law firms: attorneys who hand us their cases. They need to trust our work, see where every case stands without asking, and get clear guidance on what would make their firm more successful.

• Clients: injured people counting on their case moving forward. They need to know where things stand and what’s needed from them.

This role owns the operator experience, which sits at the center of the other two. It comes down to three questions:

• What can agents do on their own? Decide which work agents complete without human input, where they need sign-off, and how that line moves as they earn trust.

• How do we verify their work quickly? Design how operators check what agents have done, catch what’s wrong, and move forward without redoing it.

• What happens next? When a case manager opens a file, make it obvious what’s been done, what needs them, and what to do next.

You’ll report to Ben, our co-founder and CTO. You’ll spend real time with operators, set the direction and priorities, ship with our engineers, and measure success by operator speed, work quality, and how much agents handle on their own.

What will make you successful

You’ll likely thrive if you have

• Experience owning meaningful product work in a fast-moving, ambiguous environment, from discovery through execution and iteration.

• A track record of deeply understanding user journeys, operational workflows, and the decisions people need to make within them.

• Strong product judgment: you can turn complex workflows into clear experiences, priorities, and practical next steps.

• The ability to reason through how people and AI agents work together, making agent activity, suggested actions, escalations, and human responsibilities understandable.

• The ability to earn trust with engineers and cross-functional partners, align them around a product direction, and follow through on delivery.

• A habit of staying close to users after launch and judging success by whether they can understand what happened, take the right next action, and complete work efficiently and well.

It’s a plus if you have

• Experience building AI-powered products or workflows that combine automation with human decisions and handoffs.

• Experience with workflow-heavy, operational, or B2B products.

• Experience building products for users working in high-trust or high-stakes environments.

• Experience helping establish product practices at an early-stage or rapidly changing company.

• You prefer a role where the roadmap, process, and success metrics are already defined.

• You are looking for a narrow remit rather than ownership from user discovery through delivery and iteration.

• You need a fixed organizational structure and fully defined product-area ownership before you can do your best work.

What happens next

We aim to run a human, efficient process. That generally includes:

1. Intro: An initial conversation about your background, motivation, and the role.

2. Interview: A deeper dive with a leader on the team.

3. Case Interview: A practical exercise that gives you a sense of the problems we’re solving and of how you approach a product problem, make tradeoffs, and turn your thinking into a clear direction.

4. Onsite: A chance to meet the team and explore the work together.