Staff Engineer - Monetization

<div class="content-intro"><p>Fastly helps people stay better connected with the things they love. Fastly’s edge cloud platform enables customers to create great digital experiences quickly, securely, and reliably by processing, serving, and securing our customers’ applications as close to their end-users as possible — at the edge of the Internet. The platform is designed to take advantage of the modern internet, to be programmable, and to support agile software development. Fastly’s customers include many of the world’s most prominent companies, including GitHub, Yelp, Paramount, and JetBlue.</p> <p>We're building a more trustworthy Internet. Come join us.</p></div><p><strong><strong>Staff Backend Software Engineer, Monetization</strong></strong></p> <p><strong><strong>Staff Backend Software Engineer</strong></strong></p> <p><strong><strong>About the Role: Staff Backend Software Engineer - Monetization Platform Team</strong></strong></p> <p><strong>Fastly helps people stay better connected with the things they love. Fastly's edge cloud platform enables customers to create great digital experiences quickly, securely, and reliably by processing, serving, and securing their applications as close to their end-users as possible - at the edge of the Internet.</strong></p> <p>&nbsp;</p> <p><strong>The Monetization Platform team owns the systems that translate what customers do on the network into the commercial relationship they have with Fastly: billing infrastructure, usage APIs, usage reporting, and orderability. Customers rely on our usage data to understand their spend, forecast costs, and make purchasing decisions. Product teams build pricing models on top of it. It's a large responsibility, and a large opportunity to shape the financial infrastructure Fastly's next chapter is built on.</strong></p> <p>&nbsp;</p> <p><strong>As a Staff Software Engineer you will lead the design and development of highly-available, scalable systems as the platform expands to support new product lines, more complex pricing models, and a usage surface that keeps growing.</strong></p> <p>&nbsp;</p> <p><strong><strong>What You'll Do:</strong></strong></p> <ul> <li> <p><strong>Design, ship, and own billing infrastructure, usage APIs, and backend services, from technical proposal and design docs through implementation, testing, production rollout, and on-call support.</strong></p> </li> <li> <p><strong>Use AI coding agents as part of your daily workflow.</strong></p> </li> <li> <p><strong>Take ambiguous or broadly-scoped problems and turn them into well-defined technical plans that the team can execute on.</strong></p> </li> <li> <p><strong>Partner with a diverse set of stakeholders across engineering, product, business systems, and billing to align on requirements and deliver impactful solutions.</strong></p> </li> <li> <p><strong>Develop design and architecture documents as a way of collaborating across groups in the design of new systems and APIs.</strong></p> </li> <li> <p><strong>Evolve the tools and pipelines that power billing, usage reporting, and orderability for Fastly's growing product catalog.</strong></p> </li> <li> <p><strong>Consider stability, performance, and scalability in your designs and in the guidance you provide to the team.</strong></p> </li> <li> <p><strong>Mentor and grow other engineers on the team through code review, pairing, and technical leadership.</strong></p> </li> <li> <p><strong>Participate in an on-call rotation.</strong></p> </li> </ul> <p>&nbsp;</p> <p><strong><strong>What We're Looking For:&nbsp;</strong></strong></p> <ul> <li> <p><strong>Hands-on experience designing and operating highly available, reliable data pipelines and distributed systems that process large volumes of data at scale - most Staff level engineers at Fastly have at least 7 years of related experience.</strong></p> </li> <li> <p><strong>5+ years building systems that collect, aggregate, and derive insights from large datasets. You've shipped a forecasting or reporting feature that real stakeholders depended on and you've had to explain why the numbers were wrong.</strong></p> </li> <li> <p><strong>You dri