Product Manager
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to extract content from posting.
First, "About BigTime" is description of company; not needed? It's not a section heading but could be part of About the role? The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should create sections with those headings if content exists.
We need to avoid repeating job title as heading. The posting includes "About The Role" heading. We'll map that to "About the role". Content under that: description of Financial Core pod, what they own, etc. We'll put that in
maybe with some
for lists.
Then "What You Will Own" and "What You Will Do" could be under Responsibilities? Probably responsibilities. Also "What We Are Looking For" includes requirements, qualifications, skills. We'll need to parse.
We also have salary info: "The expected salary for this position ranges from $125,000 to $150,000 annually." That's Pay section.
Benefits: mention "competitive benefits package" and "additional types of compensation such as bonuses." Also maybe mention "In addition to base salary and a competitive benefits package". So we can include Benefits section.
Schedule: not mentioned. So we omit Schedule.
We must not include boilerplate like EEO, legal, etc. Remove those.
We must preserve all substantive information; do not invent or summarize away detail. Must not create sections with filler.
We need to ensure we don't include placeholders like "commensurate with experience". Not present.
We need to output only HTML fragment.
Let's structure:
About the role
... content from About The Role and maybe What You Will Own/Do? Actually About The Role includes description of pod and what they own. Then "What You Will Own" and "What You Will Do" are more detailed responsibilities. Could combine under About the role or split into Responsibilities. Probably better: About the role = overview; Responsibilities = What You Will Do; Requirements/Qualifications/Skills = What We Are Looking For.
Thus:
About the role: description of Financial Core pod, what they own (project accounting subledger, etc.) maybe summarised but we must preserve detail, not summarize away. We need to keep all substantive info; we can't omit details. But we can keep them in prose; we can include bullet lists for details.
Let's extract details:
About The Role paragraph:
"The Financial Core pod owns the accounting engine underneath the platform: the project accounting subledger, the cost model, revenue recognition, WIP and unbilled balances, period close, and the integrations that tie all of it back to a firm's general ledger. This is the surface a controller reconciles against and an auditor has to accept. When it is right, a firm can confidently run its finances with us. When it is wrong, finance stays in spreadsheets and deals stall in evaluation. The pod carries real demand from day one, and the person leading it will be making calls that shape the platform for years. You will own the roadmap, the specification quality, and the outcome for that surface, working alongside an engineering lead, a designer, and a team of engineers who sit with you. This is also an underlying foundational layer for our next generation, AI-native platform. You will have the opportunity to build something brand new, while leveraging the expertise, data, customer knowledge and codebase from our existing platform."
That's the About the role content.
Now "What You Will Own" list:
- The project accounting subledger. Trial balance, subledger detail, aging, GL reconciliation, and the controls around period open, soft close, and hard close.
- Revenue recognition. ASC 606 support covering performance obligations, transaction price allocation, and recognition by method, including percent complete on cost, hours, or progress, along with milestone, ratable, and on-invoice.
- The cost model. Employee cost, contractor cost, vendor and pass-through spend, and the margin visibility that sits on top of all of it.
- WIP, unbilled, and deferred balances treated as reportable, reconcilable objects rather than numbers derived at report time.
- GL and ERP integrations. Starting with QuickBooks and extending to the major mid-market and enterprise accounting systems, with bidirectional reconciliation and error handling a finance team can trust.
- AI-native finance workflows. Agents that run the recognition cycle, drive the close checklist, reconcile subledger to GL, and explain every exception in language an accountant accepts.
We can turn each bullet into
- maybe with sub-bullets? But we can keep as prose inside li.
Now "What You Will Do":
- Write specifications precise enough that an engineer can build from them and a controller would recognize them as correct. Your written work is the artifact the pod aligns on.
- Spend real time with controllers, CFOs, revenue accountants, and accounting managers at services firms, then turn what you hear into requirements with defensible priority.
- Track regulatory and accounting-standard changes on an ongoing basis, and represent their downstream compliance impact in roadmap decisions.
- Make the prioritization calls for your surface and defend them with evidence rather than volume.
- Partner daily with engineering and design inside and across pods. Trade-offs get settled in the room, not through an approval chain.
- Define acceptance criteria, including for agent behavior, and hold the quality line before anything ships to a customer close cycle.
- Work closely with Sales, Customer Experience, and Finance so the roadmap reflects what wins deals and what keeps customers.
- Own the financial contract other pods build against, and review any feature across the platform that creates or changes financial data.
Now "What We Are Looking For" includes several sub-sections: Product Management Foundation, Finance and Accounting Background, Helpful, Not Required.
We need to map to Requirements, Qualifications, Skills sections. The instruction: use headings Requirements, Qualifications, Skills. We need to decide what goes where. Typically Requirements = mandatory qualifications; Qualifications = maybe preferred? Skills = skills. But we can just put all content under Requirements? However we need to follow instruction: use those headings only if we have real specific content. We can split:
- Requirements: Product Management Foundation (6+ years PM etc.) and Finance and Accounting Background (any one of these gets you a conversation). Those are mandatory.
- Qualifications: maybe the "Helpful, Not Required" background items? Those are qualifications (preferred). Or we could treat them as Qualifications.
- Skills: maybe the specific skills like strong written communication, comfort with ambiguity, technical fluency, AI-native work, etc. Those are skills.
Let's parse:
Product Management Foundation bullet list:
- 6+ years of product management for the PM level, or 4+ years for the Senior PM level, on a B2B SaaS product with genuine domain depth.
- A track record of shipping complex, backend-heavy capability that customers adopted, not just features that launched.
- Strong written communication. You can hold a position in a document and change your mind in public when the evidence moves.
- Comfort operating with ambiguity and a bias toward getting to a decision quickly.
- Experience working directly with engineering on data models and system design, and enough technical fluency to be useful in that conversation.
- You work AI-native. AI is part of how you do the job, not a topic you have opinions about. That means pulling signals from several data sources at once, standing up a working prototype yourself instead of waiting on a design cycle, and using AI to draft and maintain PRDs, specs, competitive analysis, and customer research synthesis. Come ready to show us what you have built this way.
Finance and Accounting Background bullet list:
- You do not need to have been an accountant, but you do need to understand how firms actually close their books. Any one of these gets you a conversation:
- ERP or accounting platform implementation, solution consulting, or solution architecture, where you configured a chart of accounts, revenue recognition, or the close process for real clients.
- NetSuite, Sage Intacct, Microsoft Dynamics, Workday Financials, Deltek, Unanet, and QuickBooks all count.
- Product management on a financial product, such as a subledger, revenue recognition engine, billing system, close platform, or reconciliation tooling.
- Hands-on accounting or finance operations experience, as a staff accountant, revenue accountant, controller, or in FP&A, with a working command of the general ledger and a move into software already behind you or clearly underway.
- A CPA, CMA, or accounting degree is relevant and we will weigh it, though none of them is required.
- The job requires that you understand what belongs in a subledger versus the GL, how percent-complete recognition behaves when the estimate changes, what a period close involves week to week, and why an auditor cares about the difference between an adjusting entry and an edit.
- If you are most of the way there, apply. We would rather teach the remainder than hire someone who has to learn all of it.
- Deep domain background is critical here. If you have run financial system implementations for years and have less time in a formal product role, we want to see your application.
Helpful, Not Required bullet list:
- Background in professional services, consulting, agency, or architecture and engineering firms.
- Experience With Multi-entity, Multi-currency, Intercompany, Or Transfer Pricing.
- Work on AI or agent-driven features inside an audited or regulated workflow.
- You have shipped your own pull requests, or worked with engineering through spec-driven and agentic development where the specification feeds the build directly.
- Having migrated customers off a legacy financial system.
- Experience with SOC 1 or 2
Now Benefits: "In addition to base salary and a competitive benefits package, this position may be eligible for additional types of compensation such as bonuses."
Pay: salary range $125k-$150k.
Schedule: none.
Now we need to output HTML fragment with sections.
We'll produce:
About the role
... (the paragraph)
Responsibilities
- ... (What You Will Own items? Actually responsibilities include both What You Will Own and What You Will Do. Could combine but maybe separate: Ownership and Do. But we can put all under Responsibilities as list items.
... etc.
We need to ensure we don't lose any detail. We'll break into two subsections? Not allowed; only headings given. We'll just put all responsibilities in a list.
We need to keep the detail: each bullet includes multiple sentences; we can keep as - with multiple sentences.
Now Requirements: we put Product Management Foundation and Finance and Accounting Background as list items? Might be long; we can keep as
- each bullet.
Qualifications: Helpful, Not Required as list.
Skills: maybe the specific skills like strong written communication, comfort with ambiguity, technical fluency, AI-native work. But those are already in Product Management Foundation. Could treat them as Skills. However we already used them in Requirements. To avoid duplication, we need to decide distribution.
Better: Requirements = the mandatory experience (years, track record). Qualifications = the finance/accounting background. Skills = the abilities (written communication, ambiguity, technical fluency, AI-native, etc.). Helpful, Not Required = maybe also Qualifications? But we already used Qualifications for finance background. Could treat Helpful as Qualifications as well (preferred). But we need to avoid duplication.
Let's map:
- Requirements: Product Management Foundation (the years, track record). Actually also the finance/accounting background is a requirement (any one gets you a conversation). So maybe both are Requirements.
- Qualifications: Helpful, Not Required (preferred background).
-
for prose. We need to extract content from posting. First, "About BigTime" is description of company; not needed? It's not a section heading but could be part of About the role? The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should create sections with those headings if content exists. We need to avoid repeating job title as heading. The posting includes "About The Role" heading. We'll map that to "About the role". Content under that: description of Financial Core pod, what they own, etc. We'll put that in
maybe with some
- for lists.
Then "What You Will Own" and "What You Will Do" could be under Responsibilities? Probably responsibilities. Also "What We Are Looking For" includes requirements, qualifications, skills. We'll need to parse.
We also have salary info: "The expected salary for this position ranges from $125,000 to $150,000 annually." That's Pay section.
Benefits: mention "competitive benefits package" and "additional types of compensation such as bonuses." Also maybe mention "In addition to base salary and a competitive benefits package". So we can include Benefits section.
Schedule: not mentioned. So we omit Schedule.
We must not include boilerplate like EEO, legal, etc. Remove those.
We must preserve all substantive information; do not invent or summarize away detail. Must not create sections with filler.
We need to ensure we don't include placeholders like "commensurate with experience". Not present.
We need to output only HTML fragment.
Let's structure:
- maybe with sub-bullets? But we can keep as prose inside li.
Now "What You Will Do":
- Write specifications precise enough that an engineer can build from them and a controller would recognize them as correct. Your written work is the artifact the pod aligns on.
- Spend real time with controllers, CFOs, revenue accountants, and accounting managers at services firms, then turn what you hear into requirements with defensible priority.
- Track regulatory and accounting-standard changes on an ongoing basis, and represent their downstream compliance impact in roadmap decisions.
- Make the prioritization calls for your surface and defend them with evidence rather than volume.
- Partner daily with engineering and design inside and across pods. Trade-offs get settled in the room, not through an approval chain.
- Define acceptance criteria, including for agent behavior, and hold the quality line before anything ships to a customer close cycle.
- Work closely with Sales, Customer Experience, and Finance so the roadmap reflects what wins deals and what keeps customers.
- Own the financial contract other pods build against, and review any feature across the platform that creates or changes financial data.
Now "What We Are Looking For" includes several sub-sections: Product Management Foundation, Finance and Accounting Background, Helpful, Not Required.
We need to map to Requirements, Qualifications, Skills sections. The instruction: use headings Requirements, Qualifications, Skills. We need to decide what goes where. Typically Requirements = mandatory qualifications; Qualifications = maybe preferred? Skills = skills. But we can just put all content under Requirements? However we need to follow instruction: use those headings only if we have real specific content. We can split:
- Requirements: Product Management Foundation (6+ years PM etc.) and Finance and Accounting Background (any one of these gets you a conversation). Those are mandatory.
- Qualifications: maybe the "Helpful, Not Required" background items? Those are qualifications (preferred). Or we could treat them as Qualifications.
- Skills: maybe the specific skills like strong written communication, comfort with ambiguity, technical fluency, AI-native work, etc. Those are skills.
Let's parse:
Product Management Foundation bullet list:
- 6+ years of product management for the PM level, or 4+ years for the Senior PM level, on a B2B SaaS product with genuine domain depth.
- A track record of shipping complex, backend-heavy capability that customers adopted, not just features that launched.
- Strong written communication. You can hold a position in a document and change your mind in public when the evidence moves.
- Comfort operating with ambiguity and a bias toward getting to a decision quickly.
- Experience working directly with engineering on data models and system design, and enough technical fluency to be useful in that conversation.
- You work AI-native. AI is part of how you do the job, not a topic you have opinions about. That means pulling signals from several data sources at once, standing up a working prototype yourself instead of waiting on a design cycle, and using AI to draft and maintain PRDs, specs, competitive analysis, and customer research synthesis. Come ready to show us what you have built this way.
Finance and Accounting Background bullet list:
- You do not need to have been an accountant, but you do need to understand how firms actually close their books. Any one of these gets you a conversation:
- ERP or accounting platform implementation, solution consulting, or solution architecture, where you configured a chart of accounts, revenue recognition, or the close process for real clients.
- NetSuite, Sage Intacct, Microsoft Dynamics, Workday Financials, Deltek, Unanet, and QuickBooks all count.
- Product management on a financial product, such as a subledger, revenue recognition engine, billing system, close platform, or reconciliation tooling.
- Hands-on accounting or finance operations experience, as a staff accountant, revenue accountant, controller, or in FP&A, with a working command of the general ledger and a move into software already behind you or clearly underway.
- A CPA, CMA, or accounting degree is relevant and we will weigh it, though none of them is required.
- The job requires that you understand what belongs in a subledger versus the GL, how percent-complete recognition behaves when the estimate changes, what a period close involves week to week, and why an auditor cares about the difference between an adjusting entry and an edit.
- If you are most of the way there, apply. We would rather teach the remainder than hire someone who has to learn all of it.
- Deep domain background is critical here. If you have run financial system implementations for years and have less time in a formal product role, we want to see your application.
Helpful, Not Required bullet list:
- Background in professional services, consulting, agency, or architecture and engineering firms.
- Experience With Multi-entity, Multi-currency, Intercompany, Or Transfer Pricing.
- Work on AI or agent-driven features inside an audited or regulated workflow.
- You have shipped your own pull requests, or worked with engineering through spec-driven and agentic development where the specification feeds the build directly.
- Having migrated customers off a legacy financial system.
- Experience with SOC 1 or 2
Now Benefits: "In addition to base salary and a competitive benefits package, this position may be eligible for additional types of compensation such as bonuses."
Pay: salary range $125k-$150k.
Schedule: none.
Now we need to output HTML fragment with sections.
We'll produce:
About the role
... (the paragraph)
Responsibilities
- ... (What You Will Own items? Actually responsibilities include both What You Will Own and What You Will Do. Could combine but maybe separate: Ownership and Do. But we can put all under Responsibilities as list items. ... etc. We need to ensure we don't lose any detail. We'll break into two subsections? Not allowed; only headings given. We'll just put all responsibilities in a list. We need to keep the detail: each bullet includes multiple sentences; we can keep as
- with multiple sentences.
Now Requirements: we put Product Management Foundation and Finance and Accounting Background as list items? Might be long; we can keep as
- each bullet. Qualifications: Helpful, Not Required as list. Skills: maybe the specific skills like strong written communication, comfort with ambiguity, technical fluency, AI-native work. But those are already in Product Management Foundation. Could treat them as Skills. However we already used them in Requirements. To avoid duplication, we need to decide distribution. Better: Requirements = the mandatory experience (years, track record). Qualifications = the finance/accounting background. Skills = the abilities (written communication, ambiguity, technical fluency, AI-native, etc.). Helpful, Not Required = maybe also Qualifications? But we already used Qualifications for finance background. Could treat Helpful as Qualifications as well (preferred). But we need to avoid duplication. Let's map: - Requirements: Product Management Foundation (the years, track record). Actually also the finance/accounting background is a requirement (any one gets you a conversation). So maybe both are Requirements. - Qualifications: Helpful, Not Required (preferred background). -
About the role
... content from About The Role and maybe What You Will Own/Do? Actually About The Role includes description of pod and what they own. Then "What You Will Own" and "What You Will Do" are more detailed responsibilities. Could combine under About the role or split into Responsibilities. Probably better: About the role = overview; Responsibilities = What You Will Do; Requirements/Qualifications/Skills = What We Are Looking For. Thus: About the role: description of Financial Core pod, what they own (project accounting subledger, etc.) maybe summarised but we must preserve detail, not summarize away. We need to keep all substantive info; we can't omit details. But we can keep them in prose; we can include bullet lists for details. Let's extract details: About The Role paragraph: "The Financial Core pod owns the accounting engine underneath the platform: the project accounting subledger, the cost model, revenue recognition, WIP and unbilled balances, period close, and the integrations that tie all of it back to a firm's general ledger. This is the surface a controller reconciles against and an auditor has to accept. When it is right, a firm can confidently run its finances with us. When it is wrong, finance stays in spreadsheets and deals stall in evaluation. The pod carries real demand from day one, and the person leading it will be making calls that shape the platform for years. You will own the roadmap, the specification quality, and the outcome for that surface, working alongside an engineering lead, a designer, and a team of engineers who sit with you. This is also an underlying foundational layer for our next generation, AI-native platform. You will have the opportunity to build something brand new, while leveraging the expertise, data, customer knowledge and codebase from our existing platform." That's the About the role content. Now "What You Will Own" list: - The project accounting subledger. Trial balance, subledger detail, aging, GL reconciliation, and the controls around period open, soft close, and hard close. - Revenue recognition. ASC 606 support covering performance obligations, transaction price allocation, and recognition by method, including percent complete on cost, hours, or progress, along with milestone, ratable, and on-invoice. - The cost model. Employee cost, contractor cost, vendor and pass-through spend, and the margin visibility that sits on top of all of it. - WIP, unbilled, and deferred balances treated as reportable, reconcilable objects rather than numbers derived at report time. - GL and ERP integrations. Starting with QuickBooks and extending to the major mid-market and enterprise accounting systems, with bidirectional reconciliation and error handling a finance team can trust. - AI-native finance workflows. Agents that run the recognition cycle, drive the close checklist, reconcile subledger to GL, and explain every exception in language an accountant accepts. We can turn each bullet into