Revenue Accounting Manager

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: description (role), responsibilities (list), required qualifications (list), preferred experience (list), pay range, benefits (mention but no specifics). Also maybe "About Databricks" but that's not a required heading; we can include as "About the role"? Actually "About the role" is a heading we can use for the introductory paragraph. We'll need to parse. We must not repeat job title as heading. No Job ID. Remove boilerplate: cookie/navigation/legal/EEO etc. Remove "Our Commitment to Diversity and Inclusion", "Compliance", etc. Also remove "About Databricks" maybe not needed as it's not a required heading but could be considered "About the role"? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include those headings if content exists. We have content for About the role (intro paragraph). Responsibilities (list). Requirements (maybe combine Required and Preferred? The instruction says separate sections Requirements, Qualifications, Skills. We need to decide mapping. Usually Requirements = required qualifications, Qualifications = preferred? Skills = specific skills. We'll try to map. We have Required: bullet list of items (education, CPA, experience, ASC 606, operational accounting, leading close, internal controls, independent operation, advanced Excel, AI tools, documentation). Preferred: bullet list (usage-based SaaS, SQL, defining system requirements, automation, financial statement disclosures). Skills: maybe combine advanced Excel, AI tools, SQL, etc. But we can put skills under Skills section. We have Pay: pay range given. Benefits: mention benefits but no specifics; we should not create Benefits section unless posting actually states them. It says "Benefits At Databricks, we strive to provide comprehensive benefits and perks that meet the needs of all of our employees. For specific details on the benefits offered in your region click here." That's generic, not specific. According to rule: never create Benefits section unless posting actually states them. It does mention benefits but no specifics; maybe we should omit Benefits section because it's not specific. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits exist but not details. I'd interpret that as we should not include Benefits section because no specific benefits listed. Similarly Schedule not mentioned, so omit. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Pay. We need to preserve all substantive information; do not invent or summarize away detail. Must not omit any substantive info. So we need to include all required and preferred bullets, plus the responsibilities list, plus the intro paragraph, plus pay range. We must not include boilerplate like "Our Commitment to Diversity and Inclusion", "Compliance", "About Databricks" maybe we can include as part of About the role? But that is about company, not role. Might be considered not substantive for the role? It's about Databricks. Could be omitted as not directly about role? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. The "About Databricks" paragraph is substantive about company but not role. Might be considered not required but could be kept? However the headings list does not include "About the company". Could we put it under About the role? Might be stretching. Safer to omit it because not under allowed headings and not required. But we might lose some substantive info. However the instruction says "Prefer a few substantive sections over many thin ones." And we must not create sections without real specific content. The "About Databricks" is specific but not under allowed headings. Could we include as a

without heading? The instruction: Output ONLY the HTML fragment — no /, no markdown code fences. It didn't forbid extra paragraphs outside headings. We could include a

about Databricks as part of the fragment, but then we would have stray content not under a heading. The instruction about headings is for section headings; we can still have

elements outside headings? Probably okay but better to keep under a heading like "About the role". However that heading is for role description, not company. Might be okay to include company description under About the role as it's still about the role context. I'd include it. Thus structure:

About the role

Intro paragraph: Databricks is looking for a Revenue Accounting Manager ... (the first paragraph up to "This is an individual contributor position with significant ownership and cross-functional influence.") plus maybe the "Our revenue accounting environment is evolving rapidly..." paragraph? That's also part of role description. We'll include all prose before the bullet list "The Impact You Will Have". Actually the posting includes: "(GAQ427R221) Databricks is looking for a Revenue Accounting Manager to join our team. You will report to the Manager of Revenue Accounting and play a hands-on leadership role across the full revenue accounting close cycle, from evaluating complex contract terms and applying ASC 606, to leading UAT for new system logic, to preparing financial reporting deliverables for internal and external stakeholders. This is an individual contributor position with significant ownership and cross-functional influence. Our revenue accounting environment is evolving rapidly. New SKUs, new go-to-market motions, shifting policy requirements and system migrations are the norm. We need someone who thrives in ambiguity, adapts when priorities shift and takes ownership of complex problems. Our ideal candidate has a builder’s mindset: someone who digs into the details, challenges existing processes and leads improvements that make the close faster, more accurate and scalable." Then after that: "The Impact You Will Have" then bullet list of responsibilities. Thus we can treat everything before "The Impact You Will Have" as About the role prose. Then Responsibilities section: list of bullet points under "The Impact You Will Have". We'll convert each bullet to

. Then Requirements section: Required bullet list. Then Qualifications section: Preferred bullet list? Or maybe Qualifications = Preferred? We'll put Preferred under Qualifications. Then Skills section: maybe combine specific skills like Advanced Excel, AI tools, SQL, etc. But we already have those in Required and Preferred. To avoid duplication, we could create Skills section for things like Advanced Excel, AI tools, SQL, etc. However we must preserve all info; if we move them to Skills we still need to keep them somewhere else? We could keep them in Required and Qualifications and also have Skills but that would duplicate. Better to not create Skills if it would duplicate or be thin. The instruction: Prefer a few substantive sections over many thin ones. So maybe we skip Skills section and put skills under Requirements or Qualifications. But the headings list includes Skills as optional; we can omit if not needed. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Pay. Check if we need to include "Schedule": none. Now we need to format lists with

• . We must not include any boilerplate like "Our Commitment to Diversity and Inclusion", "Compliance", "About Databricks" (if we omitted). Also remove "Pay Range Transparency" heading? We'll just include Pay section with the range. We need to preserve the pay range text: "Zone 1 Pay Range $144,700—$199,000 USD". Also the preceding sentences about pay range transparency etc. Should we include all that? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should include the explanatory sentences about pay range transparency as part of Pay section. However those sentences are somewhat generic but still substantive. We'll include them as

  under Pay. Similarly for Benefits we omitted because not specific. Now ensure we don't include any headings like "About Databricks". We'll not include that. Now produce HTML fragment. Let's craft:

  About the role

  Databricks is looking for a Revenue Accounting Manager to join our team. You will report to the Manager of Revenue Accounting and play a hands-on leadership role across the full revenue accounting close cycle, from evaluating complex contract terms and applying ASC 606, to leading UAT for new system logic, to preparing financial reporting deliverables for internal and external stakeholders. This is an individual contributor position with significant ownership and cross-functional influence. Our revenue accounting environment is evolving rapidly. New SKUs, new go-to-market motions, shifting policy requirements and system migrations are the norm. We need someone who thrives in ambiguity, adapts when priorities shift and takes ownership of complex problems. Our ideal candidate has a builder’s mindset: someone who digs into the details, challenges existing processes and leads improvements that make the close faster, more accurate and scalable.

  Responsibilities

  • Lead the close, end to end. Own and review monthly close activities, including usage reviews, journal entries, revenue estimates, flux analyses, account reconciliations and management reporting.
  • Identify opportunities to improve quality and compress the close timeline.
  • Apply ASC 606 with sound judgment. Evaluate complex and non-standard customer arrangements, document accounting conclusions and ensure consistent application of revenue recognition policies as our product portfolio evolves.
  • Dig into the details. Pull, validate and troubleshoot data directly across contracts, billing systems, revenue systems and the general ledger. Trace discrepancies to the source and drive them through resolution.
  • Own key revenue accounts. Manage revenue subledger-to-GL reconciliations for deferred revenue, contract assets and unbilled accounts receivable. Ensure balances are accurate, complete and supported.
  • Turn data into insights. Analyze large datasets and explain key drivers affecting revenue, unbilled revenue, deferred revenue and other financial metrics. Provide clear recommendations to management.
  • Lead system and process improvements. Define business requirements, lead UAT, assess accounting impacts and partner with Engineering and Finance Data Services to implement scalable solutions across revenue, billing and ERP systems.
  • Automate relentlessly. Identify manual, repetitive processes and take ownership of building or championing automation through SQL, scripts, AI tools, workflow improvements or systematic solutions.
  • Leverage AI to work smarter. Use AI tools and large language models to accelerate contract analysis, memo preparation, data reviews, reconciliations and process improvements.
  • Strengthen internal controls. Execute and improve SOX controls, maintain clear documentation and ensure revenue processes comply with company policies.
  • Support financial reporting. Prepare key metrics, financial statement disclosures, supporting schedules and ad hoc analyses for management.
  • Support the audit with confidence. Prepare organized workpapers, respond to auditor requests, participate in walkthroughs and clearly explain the underlying transactions and accounting conclusions.
  • Solve problems at the root. Lead investigations into revenue, process and system issues. Document conclusions and implement long-term solutions that reduce risk and prevent recurrence.
  • Collaborate across functions. Build strong partnerships with Revenue Operations, Revenue Assurance, Deal Desk, Billing, Legal, Sales Operations, FP&A, Finance Data Services and Audit to address revenue-impacting matters.
  • Raise the quality bar. Provide guidance to team members and improve the quality of close deliverables, documentation, controls and processes without direct people-management responsibilities.

  Requirements

  • Bachelor’s degree with an emphasis in Accounting or Finance
  • CPA or equivalent professional certification
  • 10+ years of combined experience in public accounting, corporate revenue accounting, quote-to-cash or related financial operations
  • Strong understanding of ASC 606 and complex revenue recognition principles, with the ability to independently evaluate non-standard arrangements
  • Operational accounting experience at a rapidly growing company, including familiarity with quote-to-cash processes such as order