Product Manager

Brain Co.•San Francisco, CA

14d•Hybrid

About The Position

Brain Co.'s financial services products run inside large enterprises, asset managers, banks, specialty lenders, and corporate finance teams. This role owns what they become as a product line. You'll be the first product manager for the vertical, reporting to the vertical lead and working with AI deployment leads embedded at client sites, plus a dedicated engineering and design team. You'll set the roadmap, define the standards every deployment is held to, and decide which capabilities become part of the core product. That last decision is most of the job. You'll spend your time with the people doing the work, finding the structure underneath, and building the parts that hold across accounts. Financial services is a wide surface. You'll have a point of view on which parts we go after next, and the standing to act on it.

Requirements

7+ years building products, with a track record of owning an area end to end: discovery, launch, and the iteration after.
Real technical depth. You can reason about how a system is put together, read an API spec, and hold your own with engineers without needing a translator.
Experience shipping into complex, document-heavy environments where being wrong is expensive.
A high quality bar and a fast ramp. You sweat the details other people let slide, and pick up unfamiliar domains quickly.
Exceptional communication. You can explain a modeling trade-off to an engineer, then the same decision to a CFO.
Extreme comfort with ambiguity. You structure your own work and don't wait for a playbook.

Nice To Haves

You've built for financial services, accounting, audit, lending, credit, fund reporting, or the office of the CFO, and can talk to a practitioner in their own vocabulary.
You came into product from a finance seat: corporate finance, audit, accounting, FP&A, fund finance, banking, or underwriting.
You've worked forward-deployed, in solutions, or as a founding PM, accountable for a named account at real depth.
You've shipped production agents and have informed opinions on evals, accuracy, and when to trust model output.
You're a builder outside of work: side projects, real production code, a startup attempt.

Responsibilities

Turn deployments into product. Every engagement produces something that works for one institution. You decide what becomes a reusable capability and what stays specific to that account, and you hold that line under pressure.
Run discovery. On-site, with the end users doing the work: controllers, underwriters, analysts, operators.
Set the quality bar. Decide what great means for each product surface, then measure it: accuracy, adoption, hours returned, and whether people still use it in month six.
Build rather than specify. Prototype in design or in code. We'd take something working today over a PRD tomorrow.
Own the accuracy and control model. These are regulated institutions with almost no tolerance for a wrong number. You decide where an agent acts, where a human reviews, what gets cited back to source, and how the system fails safely.
Know the market inside out. Enough to argue for something no customer has asked for yet, and to defend it to the people who fund it.