Revenue Transformation Analyst

Who We Are Notion is the collaborative AI workspace where teams and agents think together. We're building one place where your knowledge, projects, meetings, and AI tools live side by side, so work is faster, clearer, and less fragmented. Millions of individuals, small teams, and large companies run their work on Notion. Notinos (our employees) are customer zero in bringing this future of work to life. We care about craft, building things that last, and the belief that great work is still fundamentally human. Our goal isn’t to ship the next feature. Each and every team of Notinos is working to set the standard for how humans work together in the AI era. From building a business’s system of record to making and managing AI agents to automating away the busy work, we care deeply about giving our customers more time for their life’s work. About the Role: Notion is hiring a Revenue Transformation Analyst to help scale our revenue accounting operations as the business grows and our systems and processes evolve. This role is ideal for someone with a strong foundation in revenue accounting, a practical understanding of month-end close and ASC 606, and a track record of improving the processes around them. Rather than owning recurring close activities, you’ll partner with Revenue Accounting and Systems Engineering to redesign the workflows, controls, and tooling that make close faster, more predictable, and easier to scale. This role is based in San Francisco. We work from our offices on Mondays, Tuesdays and Thursdays (our Anchor Days) because we do our best thinking and building together in person. We’re looking for someone who’s excited to work alongside the team during those days. What You'll Achieve: - Big bet: Make revenue close measurably more predictable by reducing manual effort and operational risk in the workflows Revenue Accounting relies on most. - By day 90: Diagnose and map 1–2 highest-friction revenue close workflows (recons, tie-outs, variance analysis, documentation), align on “better,” and ship an initial improvement with clear adoption and evidence expectations. - By day 90 (AI leverage): Implement a controlled AI-assisted workflow for repeatable analysis and documentation (e.g., variance investigation scaffolds, documentation drafts, checklist QA) with review steps, controls, and audit-ready artifacts. - By end of year 1: Deliver 2–3 durable process/tooling improvements that materially reduce recurring close effort and error risk, with clear ownership and “new way” documentation that holds up through multiple closes. - By end of year 1: Raise the bar on operational rigor (requirements, acceptance criteria, testing, control narratives) so changes move from idea → delivery → adoption without heroics. Skills You'll Need to Bring: - 3–5 years of progressive revenue accounting experience, ideally at both a Big Four accounting firm and a SaaS company. - Fluency in ASC 606 and month-end close mechanics — you can spot issues, ask the right questions, and propose pragmatic fixes that hold up under scrutiny. - Track record improving finance/accounting operations (recons, tie-outs, variance analysis, documentation, control narratives) end-to-end — from messy current state to shipped change and sustained adoption. - Strong project management, execution, and organization: clear project plans, crisp written updates, and the ability to move work predictably from idea → requirements → delivery → rollout. - Comfort partnering with technical teams (BizTech/Engineering): translating accounting needs into requirements, acceptance criteria, and testing approaches; validating outputs; and tightening the loop when reality doesn’t match the spec. - Practical, thoughtful use of AI to improve quality and speed in repeatable work — with QA, documentation, and guardrails that make the workflow audit-ready. Nice to have: - Exposure to usage-based or consumption pricing and the billing / revenue recognition complexity it creates. - Experience leading complex, cross-functional projects beyond standard audit work. - Experience in a revenue operations, revenue accounting transformation, or accounting systems role. Notion is committed to providing highly competitive cash compensation, equity, and benefits. The compensation offered for this role will be based on multiple factors such as location, the role’s scope and complexity, and the candidate’s experience and expertise, and may vary from the range provided below. For roles based in San Francisco, the estimated base salary range for this role is $130,000 - $145,000 per year. By clicking “Submit Application”, I understand and agree that Notion and its affiliates and subsidiaries will collect and process my information in accordance with Notion’s Global Recruiting Privacy Policy. #LI-Onsite A Note on AI You don’t need deep AI expertise for every role, but we do expect every Notino to be intellectually curious, drawn to tinkering and discovery, and excited

Fluency in ASC 606 and month-end close mechanics. Track record improving finance/accounting operations (reconciliations, tie-outs, variance analysis, documentation, control narratives) end-to-end. Strong project management, execution, and organization skills. Ability to partner with technical teams (BizTech/Engineering) to translate accounting needs into requirements, acceptance criteria, and testing approaches; validating outputs. Practical, thoughtful use of AI to improve quality and speed in repeatable work with QA, documentation, and guardrails for audit readiness.

Diagnose and map 1–2 highest-friction revenue close workflows (reconciliations, tie-outs, variance analysis, documentation), align on improvements, and ship initial changes with adoption and evidence. Implement a controlled AI-assisted workflow for repeatable analysis and documentation (variance investigation scaffolds, documentation drafts, checklist QA) with review steps, controls, and audit-ready artifacts. Deliver durable process/tooling improvements that reduce recurring close effort and error risk, with clear ownership and documentation. Elevate operational rigor (requirements, acceptance criteria, testing, control narratives) to move changes from idea to delivery to adoption without heroics.