Software Engineer, Billing & Revenue Platform

About this role

Glean seeks a lead engineer to design and own the billing and revenue platform powering consumption-based pricing for AI products. You'll drive metering, pricing logic, and billing dashboards while providing technical leadership across data pipelines, backend services, and frontend systems—ensuring every AI feature shipped is accurately billed and margin-positive.

What you'll do

• Design and implement usage metering, pricing logic, credits, and admin billing dashboards end-to-end
• Provide technical leadership and vision across billing systems spanning data pipelines, backend services, and web UX
• Partner with Finance, Pricing, RevOps, and Product to translate pricing strategy into robust technical designs
• Define guardrails for LLM and agent costs including limits, anomaly detection, and margin monitoring
• Create powerful abstractions that make it safe and easy for product teams to integrate with billing
• Drive evolution of consumption and Flex pricing infrastructure with high standards for correctness and reliability

What they're looking for

• Backend systems design and implementation
• Data pipelines and analytics engineering
• Pricing and billing platform architecture
• Full-stack development (backend, frontend, APIs)
• Consumption-based/usage metering systems
• Cross-functional collaboration and leadership
• High-scale system reliability and debugging
• Cost optimization and financial acumen

Benefits

• Work on critical infrastructure for an AI-powered enterprise platform
• Lead technical vision across a broad, impactful surface area
• Partner closely with Product, Finance, and Go-To-Market teams
• Shape how enterprises consume and pay for AI capabilities
• Opportunity to grow as a technical leader
• Remote-friendly work at an innovative, fast-growing company

Likely interview questions

• Walk us through a billing or pricing system you've built—how did you handle accuracy, auditability, and scaling?
• How would you design usage metering to support multiple consumption models (per-call, per-token, per-user) with minimal coupling to product code?