Senior Software Engineer, Consumption Based Billing & Licensing

Asana Asana · Enterprise · Vancouver, BC · Product Engineering

Senior Software Engineer to join the Consumption Based Billing & Licensing (CBBL) team to build systems for licensing, entitlements, and usage-based billing for Asana's newest products. The role involves designing, building, and operating high-leverage backend systems, owning complex features end-to-end, and driving technical excellence.

What you'd actually do

  1. Design, build, and operate the high-leverage backend systems that power Asana's licensing and consumption-based billing infrastructure.
  2. Own complex features end-to-end, from initial problem framing and technical design through launch and global iteration.
  3. Architect and improve critical systems for access control, usage tracking, and automated license assignment to ensure a seamless admin experience.
  4. Partner closely with Product, Design, Data, Finance, and other engineering teams to turn ambiguous business needs into reliable, shipped solutions.
  5. Drive technical excellence across the codebase through strategic refactors, robust testing, and instrumentation that improves operational health.

Skills

Required

  • Strong experience building production-grade software with a focus on backend distributed systems, APIs, and complex data modeling.
  • Proven ability to take ambiguous architectural problems and translate them into clear, actionable technical plans.
  • Experience owning large-scale projects that involve multiple stakeholders and complex technical dependencies.
  • Strong debugging and operational instincts, especially when working on revenue-critical or customer-facing systems.
  • A collaborative communicator who enjoys working across functions to solve enterprise platform challenges.

Nice to have

  • Experience with billing, payments, entitlements, or SaaS monetization.
  • Familiarity with usage-based or consumption-based pricing models.
  • Experience building admin tools or customer-facing operational dashboards.
  • Background in platform, backend, or distributed systems work.
  • Experience improving reliability, correctness, or migration safety.

What the JD emphasized

  • revenue-critical
  • usage tracking
  • billing accuracy