Senior Backend Engineer

About Wring

Wring helps companies pay less for AWS without changing a line of code. We pool our customers' spend to negotiate discounts none of them could get alone, find the credits programs they qualify for, and flag the waste sitting in their bill — all through read-only, billing-level access.

We don't charge a platform fee and we don't take a cut of what anyone saves. AWS pays us for the volume we bring and the billing complexity we absorb, which means we only do well when our customers keep saving and stay. It's a deliberately narrow business model, and it shapes how we build.

We're a small team. Everyone here talks to customers, and the distance between noticing a problem and shipping something about it is measured in days.

What you'll do

You'll own the systems that ingest and make sense of customer billing data. A single mid-sized AWS account produces millions of line items a month; our job is to turn that into a short, specific list of things worth doing — and to be right about it, because customers act on what we tell them.

That means working across data ingestion, the pricing models behind Reserved Instances and Savings Plans, and the recommendation logic that decides what to surface. You'll also help design how our 30-day commitment product actually works underneath, which is as much a modelling problem as an engineering one.

Who you'll work with

You'll join a small engineering team that owns its work end to end — no separate ops team to hand things to, and no product manager translating between you and the customer. You'll talk to the people whose bills you're shrinking.

What you'll bring

• Several years building backend systems in production, with real ownership of something that mattered when it broke
• Comfort working with large volumes of data where correctness matters more than throughput
• Enough AWS depth to reason about how its billing actually behaves — or the appetite to learn it quickly
• A habit of reducing problems before solving them, rather than building for a scale nobody asked for

Nice to have

• You've worked on billing, pricing or financial systems before
• You've used Cost Explorer or CUR data in anger and have opinions about both

How we hire

A 30-minute call to swap context, a conversation with the people you'd work with, and one practical exercise based on something we've actually had to solve — paid, and never a take-home that eats your weekend. Three steps, usually inside two weeks. We reply to every application either way.