Lead Product Manager - Ledger Subscriber Ecosystem
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we need to decide which sections have content.
We have:
- Intro: "Innovate with purpose At BILL, we believe..." This is about company, maybe "About the role"? Actually "About the role" would be description of role. The intro is more about company and mission; could be considered "About the role"? Might be better as "About the role" includes description of role and team. The posting includes "Make Your Impact Within a Rapidly Growing Fintech Company Join BILL as a Staff Product Manager..." That's role description. So we can put that under About the role
with paragraphs.
- Responsibilities: clearly present bullet list. Use - .
- Requirements: The posting has "We'd Love To Chat If You Have" list of required experience. That's requirements. Could be under
Requirements
.
- Desired Qualifications: separate list; could be under Qualifications
or Desired Qualifications
. The instruction list includes Qualifications as a possible heading. We'll use Qualifications
for desired qualifications.
- Skills: Not explicitly listed separate; but could be part of requirements. We may omit Skills if no specific list.
- Benefits: The posting mentions benefits: "competitive benefits package that includes: medical, dental, vision, life and disability insurance, 401(k) retirement plan, flexible spending & health savings account, paid holidays, paid time off, and other company benefits." Also later "What’s in it for you?" list of benefits. So we have benefits content. Use Benefits
with .
- Pay: Salary ranges for San Jose and Draper UT. So we have Pay section. Use Pay
with paragraphs maybe two ranges.
- Schedule: Not mentioned (remote-first, office spaces). Could be considered schedule? Not explicit. Probably omit Schedule.
- Also note visa sponsorship note etc. Might be considered metadata; we can fold into a short under About the role or maybe separate? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Visa sponsorship note is minor metadata; we can include a short
maybe under About the role or separate? Probably include a short
after responsibilities? But better to include a short
under About the role or at end? We'll include a short
after the responsibilities maybe? But we need to preserve ALL substantive information; visa sponsorship is substantive? It's a requirement: "Please note that this position is not eligible for visa sponsorship. Applicants must have authorization to work in the United States without requiring visa sponsorship now or in the future." That's a requirement; we could include it under Requirements as a bullet. But it's not a list; we can include as a
under Requirements.
Also note "The estimated salary range for this role is noted below for our San Jose based role." etc. That's pay.
Also note "The role is also eligible for a competitive benefits package..." repeated; we can combine.
We must not include boilerplate like EEO, equal-opportunity, scam-warning, etc. At the end there is EEO statement, Candidate Integrity Policy, Applicant Privacy Notice. Remove those.
We must not invent or summarize away detail. Keep all substantive info.
Let's extract content.
Intro / About the role:
Paragraphs:
"Innovate with purpose At BILL, we believe in empowering the businesses that drive our economy. By replacing outdated financial processes with innovative tools, we help businesses—from startups to established brands—make smarter decisions and gain control of their operations. And we don’t stop there: we’re creating the future of financial automation so businesses can spend more time on what matters. Working here means you become part of a vision-driven team that’s ready to tackle challenges and build cutting-edge solutions. We value purpose, drive, and curiosity—and we thrive in a fast-paced, ever-changing environment. We're remote-first, with office spaces in San Jose, CA and Draper, UT — and opportunities to connect in person when it counts. BILLders collaborate to deliver real impact for businesses that need more time in their busy weeks. BILL builds high performing teams and we seek to hire the best talent for every role. We're committed to building a workplace that fosters inclusion and diverse perspectives, valuing each person’s unique skills and experiences. We’d love to hear from you—you might be just what we’re looking for, whether in this role or another. ✨ Let’s give businesses more time for what matters."
Then role specific:
"Make Your Impact Within a Rapidly Growing Fintech Company Join BILL as a Staff Product Manager on our Payments and Financial Services team and own the product that determines how the company understands, reconciles, and acts on its financial data. BILL's FinSuite Platform team owns the core money-movement infrastructure that processes over $31.9B across 12 million payments per month, and Project TrueNorth is at the center of it: a unified financial ledger built to serve as the single source of truth for every dollar BILL moves across ACH, card, RTP, wallet, and international rails. The ingestion layer is live and in production. Now we need someone to build the other half of it. In this role, you will own the Ledger Subscriber Ecosystem: the reports, dashboards, data products, portals, APIs, and workflows that turn the TrueNorth ledger from an internal system of record into the operating backbone for Treasury, Accounting, FP&A, Tax, Audit, Payment Ops, and every other finance function at BILL. This is not a consumer-facing role. Your customers are internal: the teams that run month-end close, produce regulatory reports, manage cash positioning, and prevent losses. You will define the 3-year subscriber platform strategy, drive workflow change across multiple senior finance stakeholder groups, ship iterative subscriber capabilities, and own outcome metrics that matter: reconciliation days reduced, manual recon hours eliminated, and the percentage of BILL's TPV operating on-ledger. Your work will directly shape BILL's audit posture, operational efficiency, and the speed at which finance teams can move."
We can combine into About the role section.
Responsibilities list:
- Define and own the 3-year vision, strategy, and roadmap for the Ledger Subscriber Ecosystem, translating Project TrueNorth priorities into a sequenced delivery plan across subscriber utilities, data products, reconciliation tools, and adoption milestones.
- Build and ship subscriber platform capabilities including L1/L2 reconciliation reports, exception and aging queues, cash positioning views, revenue and expense journal feeds into ERP and revenue systems, and ledger-backed data products for analytics and forecasting teams.
- Drive adoption of ledger-based workflows across Treasury, Accounting, and Payment Operations, replacing spreadsheets, manual reconciliations, and bespoke reporting with reliable, auditable platform tools.
- Act as the single-threaded owner for the subscriber ecosystem across Product, Engineering, Data Platform, Treasury, Accounting, FP&A, Tax, Audit, Legal, Payment Ops, Compliance, and CXO, running discovery with subscriber teams and converting findings into clear problem statements, specs, and PRDs.
- Represent subscriber needs in ledger architecture decisions, partnering with the Ledger Data Producer PM, engineers, and architects to ensure ledger schemas, events, and controls anticipate downstream use cases for reconciliation, reporting, compliance, and analytics.
- Set and own measurable outcome metrics for the subscriber ecosystem, including percentage of TPV and products operating on-ledger, reduction in reconciliation days, time to produce regulatory customer balance reports, and audit finding reduction.
- Communicate trade-offs, progress, and risks clearly to executives and senior stakeholders through written narratives, design reviews, and status updates, and mentor other PMs as a thought partner on ledger strategy and financial data.
Requirements list (from "We'd Love To Chat If You Have"):
- 8 or more years in Product Management, with at least 4 years in fintech, payments, financial systems, or enterprise SaaS focused on financial data, reconciliation, ledgering, or treasury.
- Direct experience building products for internal finance or operations users, specifically Treasury, Accounting, FP&A, or Payment Ops, where the deliverable was a workflow, data product, reporting surface, or API rather than a consumer-facing feature.
- Deep understanding of financial data flows and processes: ledgering and sub-ledgers, bank and GL reconciliation, month-end close, revenue recognition, or treasury and cash management.
- A track record of platform delivery where you owned the vision, wrote PRDs that engineering shipped from, drove end-to-end execution, and tracked outcomes with real metrics you set and baselined yourself.
- Proven ability to lead cross-functional programs that include Finance, Risk, Compliance, or Legal stakeholders, influencing senior leaders and driving workflow change without formal authority.
- Clear, structured written and verbal communication skills, with the ability to explain complex financial and technical topics in plain terms and write executive narratives that surface trade-offs and risks explicitly.
- Please note that this position is not eligible for visa sponsorship. Applicants must have authorization to work in the United States without requiring visa sponsorship now or in the future.
We could include visa note as a separate paragraph under Requirements.
Desired Qualifications list:
- Experience building on top of financial ledger systems, GL and sub-ledger platforms, or double-entry accounting infrastructure, including familiarity with vendors such as Fragment or Modern Treasury, or exposure to event-driven data architectures like Kafka or Flink in a financial systems context.
- Background in treasury, accounting, or FP&A, whether through a prior role or a close multi-year partnership, along with working familiarity with SOX controls, audit requirements, or regulatory reporting.
- Prior experience in B2B payments, BaaS, card platforms, or working capital products, particularly where processor settlement reports from Stripe, Chase, Adyen, or Marqeta were used for revenue recognition, cost of sales, or cash positioning.
Benefits: list from "competitive benefits package" and "What’s in it for you?" We'll combine.
Benefits items:
- medical, dental, vision, life and disability insurance
- 401(k) retirement plan
- flexible spending & health savings account
- paid holidays
- paid time off
- other company benefits
- 100% paid employee health, dental, and vision plans (choose HMO, PPO, or HDHP)
- HSA & FSA accounts
- Life Insurance, Long & Short-term disability coverage
- Employee Assistance Program (EAP)
- 11+ Observed holidays and wellness days and flexible time off
- Employee Stock Purchase Program with employee discounts
- Wellness & Fitness initiatives
- Employee recognition and referral programs
- And much more
We can deduplicate but keep all.
Pay: Salary ranges:
- San Jose pay range $172,200—$206,600 USD
- Draper UT pay range $146,400—$175,600 USD
- Also note eligibility for bonus and equity plan.
We can include that.
Schedule: Not explicit; remote-first, office spaces. Could be considered schedule? Not required. We'll omit.
Now produce HTML fragment with
headings and appropriate
and
.
We must not include or . Just fragment.
Let's craft.
We'll start with About the role: maybe two paragraphs: first company intro, then role description. Could combine into one but better separate.
Requirements
. - Desired Qualifications: separate list; could be underQualifications
orDesired Qualifications
. The instruction list includes Qualifications as a possible heading. We'll useQualifications
for desired qualifications. - Skills: Not explicitly listed separate; but could be part of requirements. We may omit Skills if no specific list. - Benefits: The posting mentions benefits: "competitive benefits package that includes: medical, dental, vision, life and disability insurance, 401(k) retirement plan, flexible spending & health savings account, paid holidays, paid time off, and other company benefits." Also later "What’s in it for you?" list of benefits. So we have benefits content. UseBenefits
with- .
- Pay: Salary ranges for San Jose and Draper UT. So we have Pay section. Use
Pay
with paragraphs maybe two ranges. - Schedule: Not mentioned (remote-first, office spaces). Could be considered schedule? Not explicit. Probably omit Schedule. - Also note visa sponsorship note etc. Might be considered metadata; we can fold into a shortunder About the role or maybe separate? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Visa sponsorship note is minor metadata; we can include a short
maybe under About the role or separate? Probably include a short
after responsibilities? But better to include a short
under About the role or at end? We'll include a short
after the responsibilities maybe? But we need to preserve ALL substantive information; visa sponsorship is substantive? It's a requirement: "Please note that this position is not eligible for visa sponsorship. Applicants must have authorization to work in the United States without requiring visa sponsorship now or in the future." That's a requirement; we could include it under Requirements as a bullet. But it's not a list; we can include as a
under Requirements. Also note "The estimated salary range for this role is noted below for our San Jose based role." etc. That's pay. Also note "The role is also eligible for a competitive benefits package..." repeated; we can combine. We must not include boilerplate like EEO, equal-opportunity, scam-warning, etc. At the end there is EEO statement, Candidate Integrity Policy, Applicant Privacy Notice. Remove those. We must not invent or summarize away detail. Keep all substantive info. Let's extract content. Intro / About the role: Paragraphs: "Innovate with purpose At BILL, we believe in empowering the businesses that drive our economy. By replacing outdated financial processes with innovative tools, we help businesses—from startups to established brands—make smarter decisions and gain control of their operations. And we don’t stop there: we’re creating the future of financial automation so businesses can spend more time on what matters. Working here means you become part of a vision-driven team that’s ready to tackle challenges and build cutting-edge solutions. We value purpose, drive, and curiosity—and we thrive in a fast-paced, ever-changing environment. We're remote-first, with office spaces in San Jose, CA and Draper, UT — and opportunities to connect in person when it counts. BILLders collaborate to deliver real impact for businesses that need more time in their busy weeks. BILL builds high performing teams and we seek to hire the best talent for every role. We're committed to building a workplace that fosters inclusion and diverse perspectives, valuing each person’s unique skills and experiences. We’d love to hear from you—you might be just what we’re looking for, whether in this role or another. ✨ Let’s give businesses more time for what matters." Then role specific: "Make Your Impact Within a Rapidly Growing Fintech Company Join BILL as a Staff Product Manager on our Payments and Financial Services team and own the product that determines how the company understands, reconciles, and acts on its financial data. BILL's FinSuite Platform team owns the core money-movement infrastructure that processes over $31.9B across 12 million payments per month, and Project TrueNorth is at the center of it: a unified financial ledger built to serve as the single source of truth for every dollar BILL moves across ACH, card, RTP, wallet, and international rails. The ingestion layer is live and in production. Now we need someone to build the other half of it. In this role, you will own the Ledger Subscriber Ecosystem: the reports, dashboards, data products, portals, APIs, and workflows that turn the TrueNorth ledger from an internal system of record into the operating backbone for Treasury, Accounting, FP&A, Tax, Audit, Payment Ops, and every other finance function at BILL. This is not a consumer-facing role. Your customers are internal: the teams that run month-end close, produce regulatory reports, manage cash positioning, and prevent losses. You will define the 3-year subscriber platform strategy, drive workflow change across multiple senior finance stakeholder groups, ship iterative subscriber capabilities, and own outcome metrics that matter: reconciliation days reduced, manual recon hours eliminated, and the percentage of BILL's TPV operating on-ledger. Your work will directly shape BILL's audit posture, operational efficiency, and the speed at which finance teams can move." We can combine into About the role section. Responsibilities list: - Define and own the 3-year vision, strategy, and roadmap for the Ledger Subscriber Ecosystem, translating Project TrueNorth priorities into a sequenced delivery plan across subscriber utilities, data products, reconciliation tools, and adoption milestones. - Build and ship subscriber platform capabilities including L1/L2 reconciliation reports, exception and aging queues, cash positioning views, revenue and expense journal feeds into ERP and revenue systems, and ledger-backed data products for analytics and forecasting teams. - Drive adoption of ledger-based workflows across Treasury, Accounting, and Payment Operations, replacing spreadsheets, manual reconciliations, and bespoke reporting with reliable, auditable platform tools. - Act as the single-threaded owner for the subscriber ecosystem across Product, Engineering, Data Platform, Treasury, Accounting, FP&A, Tax, Audit, Legal, Payment Ops, Compliance, and CXO, running discovery with subscriber teams and converting findings into clear problem statements, specs, and PRDs. - Represent subscriber needs in ledger architecture decisions, partnering with the Ledger Data Producer PM, engineers, and architects to ensure ledger schemas, events, and controls anticipate downstream use cases for reconciliation, reporting, compliance, and analytics. - Set and own measurable outcome metrics for the subscriber ecosystem, including percentage of TPV and products operating on-ledger, reduction in reconciliation days, time to produce regulatory customer balance reports, and audit finding reduction. - Communicate trade-offs, progress, and risks clearly to executives and senior stakeholders through written narratives, design reviews, and status updates, and mentor other PMs as a thought partner on ledger strategy and financial data. Requirements list (from "We'd Love To Chat If You Have"): - 8 or more years in Product Management, with at least 4 years in fintech, payments, financial systems, or enterprise SaaS focused on financial data, reconciliation, ledgering, or treasury. - Direct experience building products for internal finance or operations users, specifically Treasury, Accounting, FP&A, or Payment Ops, where the deliverable was a workflow, data product, reporting surface, or API rather than a consumer-facing feature. - Deep understanding of financial data flows and processes: ledgering and sub-ledgers, bank and GL reconciliation, month-end close, revenue recognition, or treasury and cash management. - A track record of platform delivery where you owned the vision, wrote PRDs that engineering shipped from, drove end-to-end execution, and tracked outcomes with real metrics you set and baselined yourself. - Proven ability to lead cross-functional programs that include Finance, Risk, Compliance, or Legal stakeholders, influencing senior leaders and driving workflow change without formal authority. - Clear, structured written and verbal communication skills, with the ability to explain complex financial and technical topics in plain terms and write executive narratives that surface trade-offs and risks explicitly. - Please note that this position is not eligible for visa sponsorship. Applicants must have authorization to work in the United States without requiring visa sponsorship now or in the future. We could include visa note as a separate paragraph under Requirements. Desired Qualifications list: - Experience building on top of financial ledger systems, GL and sub-ledger platforms, or double-entry accounting infrastructure, including familiarity with vendors such as Fragment or Modern Treasury, or exposure to event-driven data architectures like Kafka or Flink in a financial systems context. - Background in treasury, accounting, or FP&A, whether through a prior role or a close multi-year partnership, along with working familiarity with SOX controls, audit requirements, or regulatory reporting. - Prior experience in B2B payments, BaaS, card platforms, or working capital products, particularly where processor settlement reports from Stripe, Chase, Adyen, or Marqeta were used for revenue recognition, cost of sales, or cash positioning. Benefits: list from "competitive benefits package" and "What’s in it for you?" We'll combine. Benefits items: - medical, dental, vision, life and disability insurance - 401(k) retirement plan - flexible spending & health savings account - paid holidays - paid time off - other company benefits - 100% paid employee health, dental, and vision plans (choose HMO, PPO, or HDHP) - HSA & FSA accounts - Life Insurance, Long & Short-term disability coverage - Employee Assistance Program (EAP) - 11+ Observed holidays and wellness days and flexible time off - Employee Stock Purchase Program with employee discounts - Wellness & Fitness initiatives - Employee recognition and referral programs - And much more We can deduplicate but keep all. Pay: Salary ranges: - San Jose pay range $172,200—$206,600 USD - Draper UT pay range $146,400—$175,600 USD - Also note eligibility for bonus and equity plan. We can include that. Schedule: Not explicit; remote-first, office spaces. Could be considered schedule? Not required. We'll omit. Now produce HTML fragment with
headings and appropriate
and
- .
We must not include or . Just fragment.
Let's craft.
We'll start with About the role: maybe two paragraphs: first company intro, then role description. Could combine into one
but better separate.