Product Manager

BigTime Software•Chicago, IL

5d•$125,000 - $150,000

About The Position

BigTime is building the next generation of its PSA platform, organized into cross-functional pods that own a product surface end to end. This role leads one of the heaviest of them, the Financial Core pod, which owns the accounting engine underneath the platform. This includes 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 role will own the roadmap, specification quality, and outcome for this surface, working alongside an engineering lead, a designer, and a team of engineers. This is also an underlying foundational layer for their next generation, AI-native platform, offering the opportunity to build something brand new while leveraging existing expertise, data, customer knowledge, and codebase.

Requirements

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.
Understand how firms actually close their books.
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.

Nice To Haves

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

Responsibilities

Own the roadmap, the specification quality, and the outcome for the Financial Core surface.
Write specifications precise enough that an engineer can build from them and a controller would recognize them as correct.
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.
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.