Staff Engineer (Monetization)

Join Fastly as a Staff Engineer (Monetization) and lead the design and development of highly-available, scalable systems. You will own the billing infrastructure, usage APIs, and backend services, and collaborate with diverse stakeholders across engineering, product, business systems, and billing. You will also mentor and grow other engineers on the team and participate in an on-call rotation. Fastly offers a range of benefits, including generous parental leave, health and wellness coverage, retirement plans, and opportunities for learning and growth.

• Lead the design and development of highly-available, scalable systems to support new product lines and complex pricing models.
• Design, ship, and own billing infrastructure, usage APIs, and backend services, from technical proposal to production rollout.
• Mentor and grow other engineers on the team through code review, pairing, and technical leadership.
• Testing and observability as subtraction, not addition. You can name a metric you added that paid off - and one you'd delete now
• Relational and non-relational storage systems (MySQL, BigTable, BigQuery, Dynamo, Cassandra) experience
• Pub/sub style message queues (NSQ, Kafka, Google Pub/Sub, Kinesis) experience
• 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
• 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
• Coding agents as a daily driver, not reluctantly. This team uses them heavily
• You drive projects, not just tasks. You've owned a multi-week effort end-to-end: design doc through post-launch
• You design for the people downstream of your data. The engineer whose service silently ingested bad records for a week, the customer who got an incorrect bill, the on-call engineer who had no idea what broke because there were no metrics on the pipeline. You've been the reason someone's numbers were wrong, and you've carried that into how you build now
• Cloud Technologies
• Go development
• Experience with billing or finance systems (e.g. recurring billing engines, ratings engines, financial forecasting tools) and their data requirements
• Expert on RESTful API design: resource modeling, versioning, idempotency, error semantics, pagination, OpenAPI. You've made one of these calls wrong in production and remember what it cost to clean up