Backend Engineer

Cloudzero

Boston, MA

Full Time

Mid Level

18 days ago

Job Description

About the Role

Every new AI service, cloud provider, and SaaS tool generates billing data in its own special snowflake format. Someone needs to wrangle this into something useful. That someone is you. You'll build the adapters that ingest cost data from OpenAI, Anthropic, and dozens of other vendors. Think of it as ETL for the modern era, where the "E" stands for "expensive cloud bills." You'll work with real data scale from some of the best engineering teams in the world. It's a small team, so your ability to have an impact on what we build and how quickly we make it will be unparalleled. You'll also be working at the nexus of the most exciting area in technology right now: the full suite of AI products that are out there on the market, helping engineering teams (our customers) learn how to build profitability on them.

Key Responsibilities

Build resilient billing adapters that stay functional, even when vendors break their APIs
Transform inconsistent vendor data into our internal format, without losing accuracy or your sanity
Integrate with REST APIs that range from elegant to “why does this return XML?”
Write clean, maintainable Python that your future self will thank you for at 2 a.m.
Debug and maintain production data pipelines processing millions in daily cloud spend
Review and collaborate on high-quality code with a seasoned engineering team

Requirements

Experience with billing systems or FinOps
Knowledge of cloud provider APIs
ETL/data pipeline background
SaaS platform development
Battle scars from production incidents
2+ years in Python - You know the difference between a list and a generator
SQL fluency - Joins are second nature, and you wield CTEs with confidence
REST API integration - You've wrestled with rate limits, pagination, and inconsistent schemas
AWS knowledge - Especially Lambda, S3, and the billing intricacies they bring
Data transformation - You know how fragile things get when schemas change
Git proficiency - You write commit messages your teammates (and future you) understand
Testing mindset - Unit tests are part of your workflow, not an afterthought
Problem-solver - You debug with a method, not just hope
Clear communicator - You can explain technical decisions to non-technical teammates
Independent contributor - You can own a project end-to-end
Adaptable - New vendor APIs don't rattle you
Team-oriented - You see code reviews as opportunities, not battlegrounds