Software Engineer, Monetization

TL;

DR — Why This Role Matters

We're hiring a Staff Engineer to define and own the technical foundation of how Scribe monetizes. That means pricing infrastructure, entitlements, provisioning, customer and org hierarchy, packaging, and the revenue operations systems that tie it all together.

You'll set the technical direction for mission‑critical infrastructure serving 5M+ users and 600K+ organizations, anchor the billing engineering team, and co‑own the monetization strategy from an engineering standpoint. The problems are company‑level. The ownership is real. And the platform you build will directly shape how Scribe prices and delivers its product for years.

Scribe has a working billing system and a growing enterprise business but the platform needs to evolve beyond what it is today. We're migrating infrastructure, hardening reconciliation, and expanding the definition of "billing" into pricing, entitlements, provisioning, and revenue operations. This role exists to design that next system, not maintain the current one.

The goal is to build systems that determine what customers pay and what they can access should be the most reliable, extensible, and well‑understood in the company.

The problems are genuinely hard. Scribe's pricing model is evolving from simple seat‑based subscriptions toward hybrid contracts combining seats, usage, and enterprise‑negotiated terms and the systems that support that need to be redesigned, not patched. Entitlements need to map cleanly to product access across a growing set of SKUs without becoming a maze of special cases. Billing state, product state, and financial reporting run across async systems that must stay consistent under partial failures and retries.

And we're doing some of this while migrating legacy infrastructure without disrupting the Finance close process. Correctness isn't a nice‑to‑have here it's the definition of done.

In this Staff IC role you will set technical direction and raise the bar for the engineers around you. You'll be the technical anchor for the billing team, elevating fellow engineers through code review, design feedback, and pairing. You'll work closely with Finance, Revenue Operations, Sales, and Product, not as a coordinator, but as the person who owns the technical strategy those conversations depend on.

• Own the technical vision and long‑term architecture of Scribe's monetization platform: billing, pricing infrastructure, entitlements, provisioning, packaging, and customer/org hierarchy

• Set the technical standard for the billing engineering team define engineering norms, lead high‑stakes design decisions, and raise the level of junior engineers through review and mentorship

• Drive the design of systems that allow Scribe to launch new pricing models, tiers, and products without re‑architecting from scratch

• Own the entitlements and access control layer — the boundary between billing state and product access

• Define and maintain the infrastructure Finance and Revenue Operations rely on: reconciliation pipelines, audit trails, reporting, and close processes

• Partner with Growth leads to keep monetization and growth systems coherent as they scale

• Collaborate with the Controller, Revenue Operations, Sales, and Product leadership to translate business requirements into durable system design

• Identify and eliminate architectural gaps that create financial risk, operational complexity, or product constraints

• Shape the technical direction for how self‑serve subscriptions, enterprise invoicing, and sales‑assisted purchasing coexist at scale

• Contribute to hiring, onboarding, and engineering culture on the monetization team

• You have 10+ years of software engineering experience, with deep time in monetization, billing, or revenue‑critical systems

• You have owned the technical strategy for a monetization platform not just executed on one someone else designed

• You've worked on systems where "incorrect" has a dollar sign attached revenue pipelines, financial reporting, or billing infrastructure in production

• You can reason across the full monetization stack: pricing models, subscription lifecycle, entitlements,…