Deepgram · London
Sales & BusinessFinanceRemoteFullTimeposted 2w ago
Deepgram is the leading platform underpinning the emerging trillion-dollar Voice AI economy, providing real-time APIs for speech-to-text (STT), text-to-speech (TTS), and building production-grade voice agents at scale. More than 200,000 developers and 1,300+ organizations build voice offerings that are ‘Powered by Deepgram’, including Twilio, Cloudflare, Sierra, Decagon, Vapi, Daily, Cresta, Granola, and Jack in the Box. Deepgram’s voice-native foundation models are accessed through cloud APIs or as self-hosted and on-premises software, with unmatched accuracy, low latency, and cost efficiency. Backed by a recent Series C led by leading global investors and strategic partners, Deepgram has processed over 50,000 years of audio and transcribed more than 1 trillion words. There is no organization in the world that understands voice better than Deepgram.
At Deepgram, we expect an AI-first mindset—AI use and comfort aren’t optional, they’re core to how we operate, innovate, and measure performance.
Every team member who works at Deepgram is expected to actively use and experiment with advanced AI tools, and even build your own into your everyday work. We measure how effectively AI is applied to deliver results, and consistent, creative use of the latest AI capabilities is key to success here. Candidates should be comfortable adopting new models and modes quickly, integrating AI into their workflows, and continuously pushing the boundaries of what these technologies can do.
Additionally, we move at the pace of AI. Change is rapid, and you can expect your day-to-day work to evolve just as quickly. This may not be the right role if you’re not excited to experiment, adapt, think on your feet, and learn constantly, or if you’re seeking something highly prescriptive with a traditional 9-to-5.
We’re hiring a Revenue Accounting Manager to own the revenue close and the monthly application of ASC 606 as Deepgram scales through its first external audit. You’ll report to the Director, Revenue Accounting and manage our revenue accountant.
Customers commit to a dollar amount up front, usually over a twelve to twenty-four month term, and draw it down on API usage. Alongside that we run a self-serve consumption business, plus arrangements involving credits, overage, trained models, concurrency, and more.
We’re working through our 606 positions now, which means the person in this seat helps shape them rather than inheriting them. We’re looking for someone who can carry a position from the guidance through to a schedule an auditor can test, a process that holds up every month once volume inevitably doubles, and an explanation other teams can follow when they want to know why we’re asking. Plenty of people have depth in one of those, but fewer carry all three end to end. You’ll own the close and the schedules underneath it, and build the rest alongside the Director, Revenue Accounting and the Director, Technical Accounting. Controls get designed in partnership rather than handed down, and because the process, reporting, and automation we need are mid-flight, you’ll spend real time with CS, Sales, and Engineering.
The person who does well here would rather build the schedule than take one as given, and stays curious about what’s happening in the business behind the number, because the answer usually comes from a conversation with Sales, CS, or Engineering rather than from the ledger.
Run the monthly revenue close. Enterprise committed usage, self-serve consumption, and direct entries, reconciled and tied out on the same date every month. Self-serve comes in through the payments stack, and building that into the close cleanly is part of the work.
Own contract liability and deferred revenue. By customer and by contract, tying to the GL and rebuildable from source rather than rolled forward on faith.
Apply the 606 policy suite every month. Material rights on credit rollover, breakage on unused commitments, standalone selling price and discount allocation across platform usage, support, trained models, and concurrency, and contract modifications on upsells, renewals, and co-terms. You’ll build the analysis and the schedules the technical positions rest on, working through them with the Directors as the positions get set.
Explain what moved and why. Monthly and quarterly flux on revenue and deferred revenue, the metrics that come out of the close, and the analysis behind them. This is what the executive team and the board see when they ask how revenue is tracking, what Deal Desk and CS come back to when a deal doesn’t look the way they expected, and what auditors test against.
Be a real manager to our revenue accountant. You’re their first call when something doesn’t tie, and the person who makes sure they’re getting better at the work rather than just getting through it. That relationship is also the backbone of a preparer and reviewer split with segregation of duties and a management review control an auditor can test.
Own the usage-to-billing-to-GL reconciliation. Write the accounting spec that says what has to tie, at what grain, within what tolerance, and what happens when it doesn’t, then hold the tooling Engineering builds to it. The goal is fewer exceptions to work by hand, not more hands to work them.
Be the auditors’ day-to-day contact on revenue, and build the controls that outlast the audit. PBC packages, walkthroughs, and the back and forth on your areas. Then the control design that comes out of it, built with the Directors, starting from the revenue assertions and working back to owner, frequency, and evidence, designed now so there’s enough operating history to rely on when SOX arrives.
Get involved before the ink dries. Deal Desk, Sales, CS, and Legal on order form terms, credits, and overage mechanics. The cheapest revenue problem to fix is the one caught before signature.
Take the revenue workstream in the platform migration. Requirements from the revenue side, close process design, data migration and cutover reconciliations, parallel run validation, built alongside the Director, Revenue Accounting. You’d be joining while this is live.
Rebuild the close around AI. Term extraction and classification, reconciliation matching, anomaly detection, schedule and rollforward generation, first-draft variance narratives, PBC assembly. Build tooling the team runs without you in the room.
Seven or more years in accounting with most of it in revenue, including owning a monthly or quarterly close start to finish and reviewing another accountant’s work.
You make the person you manage better. Review that raises the bar rather than just catching errors, and feedback someone can act on. We care about people getting better here, which applies to the accountant you’ll manage and to you, since this is a function that will keep growing and the person building it grows with it.
Hands-on ASC 606 in a consumption or drawdown model. Prepaid commitments burned down over a term, credits, overage, and the balance left at renewal. We’ve weighted this heavily because almost none of it looks like ratable subscription work, and you’d be applying it in your first month.
Depth in the topics that will define our audit. Material rights, breakage and forfeiture estimation, standalone selling price and allocation, variable consideration, contract modifications, contract liabilities, and gross versus net. Enough that you could build the position and the schedule from a blank page.
You can do the data work yourself. SQL, Python, or a spreadsheet methodology you can walk someone through end to end, including how you’d handle an unmatched residual and what tolerance you’d accept. A lot of what you’ll reconcile lives in systems that don’t share a key.
A working AI practice. You use LLMs on revenue work regularly, and you’ve got views on where they’re trustworthy in a close, term extraction, reconciliation matching, anomaly flagging, schedule generation, first drafts, and where they aren’t, the material right conclusion, the breakage estimate, the modification call. Ideally at least one thing you’ve built is being used by someone other than you.
Systems fluency. A billing and revenue platform such as Ordway, Zuora, Maxio, RevPro, NetSuite ARM, or Rillet, a payments stack, a CRM, and a GL, with views you formed through using them rather than from vendor decks.
You write clearly for people who don’t do this work. Explaining why revenue moved to someone outside accounting, and writing a position an auditor doesn’t come back on.
Active CPA preferred, and a Big 4 or national firm foundation is a plus.
High integrity, high ownership, low ego.
Experience preparing for or running a company’s first external audit, on the revenue accounts specifically.
Experience standing up revenue controls, whether that’s a RACM through to ICFR or SOX revenue cycles at a newly public company.
Experience implementing or migrating a billing and revenue platform.
Both an enterprise and a self-serve revenue motion under one roof.
A breakage or forfeiture estimate you built from scratch, including sourcing the historical data behind it.
AI infrastructure, developer platform, or API-metered revenue experience.
Exposure to multi-entity or international revenue and the related intercompany mechanics.
Notice: We're aware of individuals impersonating Deepgram recruiters. All legitimate Deepgram recruiting communication comes from an @deepgram.com email address. If you've received a message claiming to be Deepgram, please forward it to careers@deepgram.com.