Senior Product Manager / Owner (EQUITY ON THE TABLE)

Job Description

About the Client

\n

They build financial infrastructure for credit markets. The platform helps banks, asset managers, private credit firms, and other institutional participants turn credit documents, amendments, notices, and loan operations workflows into structured, traceable, auditable data and execution.

\n

\n

Syndicated lending remains document heavy and risk sensitive. Clients need faster execution, better data quality, clearer lineage, and stronger controls across booking, servicing, and downstream systems. They work in that gap.

\n

\n

About the Role

\n

The Product Manager owns the roadmap across the product suite. You turn client needs and market input into requirements engineering can build from, set priorities, and answer for whether shipped work improves outcomes for clients. Engineering and delivery leads run execution. This role decides what gets built and why.

\n

\n

The work moves between loan operations, engineering, executives, and clients. Strong candidates are comfortable in each of those conversations.

\n

\n

What You Will Own

\n

1. The roadmap. Set priorities, sequence releases, and defend both to leadership and clients.

\n

2. Discovery. Sit with banks and institutional clients, understand their workflows, and turn what you hear into problems worth solving.

\n

3. Requirements. Write scope, acceptance criteria, and the operational context behind them so engineering builds the right thing once.

\n

4. Outcomes. Define success for each release and track whether shipped work improves execution speed, data quality, and controls.

\n

5. Tradeoffs. Call what ships, what waits, and what gets cut, and explain why.

\n

6. The record. Keep Jira and Confluence current on requirements, decisions, and scope.

\n

7. Client engagements. Bring domain context and clear answers on product direction.

\n

8. AI tools. Use them to speed up research, requirements drafting, and analysis.

\n

\n

What Success Looks Like

\n

1. First 30 days: you know the products, the clients, the backlog, and the open decisions. You can explain what each product does and who it serves.

\n

2. By 90 days: the roadmap is current and defensible. Requirements reaching engineering are settled before build starts rather than during it.

\n

3. By six months: releases map to client outcomes and leadership trusts the roadmap.

\n

\n

Required Experience

\n

1. 8+ years of product management in software, fintech, banking, or financial services technology.

\n

2. Direct experience in credit, lending, loan operations, or capital markets rather than broad fintech exposure alone.

\n

3. Familiarity with the loan lifecycle, from credit approval and documentation through closing, booking, servicing, amendments, and notices.

\n

4. A record of shipping enterprise software you owned: the roadmap, the requirements, the priority calls, and the results after release.

\n

5. Experience with institutional clients or bank stakeholders where controls matter.

\n

6. Strong writing. Requirements, roadmaps, and decisions in this role live in writing.

\n

7. Proficiency with Jira and Confluence.

\n

8. Bachelor's degree in finance, business, law, computer science, or a related field. Equivalent experience considered.

\n

\n

Preferred Qualifications

\n

1. Syndicated lending, private credit, leveraged finance, or loan servicing exposure.

\n

2. Working knowledge of loan accounting systems or comparable servicing and booking platforms.

\n

3. Experience with integrations, APIs, data workflows, or document intelligence platforms.

\n

4. Familiarity with risk, audit, UAT, and production readiness in regulated environments.

\n

5. MBA, legal, or accounting background.

\n

6. Active use of AI tools in product work.

\n

\n

How We Evaluate Fit

\n

1. You can walk through a product you owned: the problem, the roadmap, the calls you made, and what happened after release.

\n

2. You can explain a lending workflow in specific operational terms.

\n

3. You can show requirements you wrote and how engineering used them.

\n

4. You can make a priority call under constraint and defend it.

\n

5. You write clearly. Unclear writing creates unclear products.

\n

\n

Candidate Profile

\n

The strongest candidates come from fintech, bank technology, institutional lending operations, or financial services software, and have owned a product rather than advised on one. They stay close to clients, the documents, and the practical realities of credit market operations.