About the Role

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.

What You Will Own

• 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.

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.

What We Are Looking For

Product Management Foundation

• 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

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. This is the most common path into this role and we weigh it heavily.
• 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

• 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

The expected salary for this position ranges from $125,000 to $150,000 annually. The actual salary will be determined on an individualized basis, taking into account a wide range of factors including, but not limited to, relevant skills, experience, education, and, where applicable, licenses or certifications held. In addition to base salary and a competitive benefits package, this position may be eligible for additional types of compensation such as bonuses.