Software Engineer, Real Time Analytics - San Francisco HQ at Orb
San Francisco, CA
$165,000–$225,000
Jul 19, 2026
San Francisco, CA
Jul 21, 2026
What this job asks for AI summary
A backend-leaning product engineering role focused on building real-time billing state infrastructure — specifically the systems that track consumption, enforce entitlements, and trigger spend controls for enterprise and AI customers. The work spans API design, alerting, credit balance primitives, and usage analytics, all computed against live pricing and billing data. Suits engineers comfortable owning a product surface end to end, from customer conversations through implementation.
Mid level · 3+ years · Remote · Full-time
Posted 6 times — it's one opening, so apply once.
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Roughly 14,700 people nationally plausibly meet what this posting asks for (software developers). range 4,300–22,000
Applicant volume Moderate — A normal amount of company. The rare requirements below are what will separate a shortlisted application from the rest.
Rare in this occupation — lead with these, and say what you built with them.
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $138,970 (middle half $107,524–$175,762).
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.
Why we read it this way (6)
The job title is simply 'Software Engineer' (no level modifier), so advertised seniority is Unspecified. The requirements gate on 3+ years of experience and end-to-end product ownership, which supports a Mid-level classification; the scope and ambiguity language is aspirational rather than evidence of Staff/Principal.
API design and data modeling are called out with firm language in the 'About you' requirements section ('Comfortable designing APIs and data models that other teams and customers depend on') and are treated as hard gates. Systems depth for real-time/low-latency reasoning is similarly required but names no specific technology, so it is omitted per the generic-concept rule.
All technologies (TypeScript, React, Tailwind CSS, Python, PostgreSQL, Apache Druid, ClickHouse, Kafka, Spark Streaming, AWS) appear exclusively under the 'Orb's Tech Stack' narrative section, which explicitly states 'you do not need experience with these specific tools.' They are captured as preferred stack context, not hard gates.
No compensation figures are disclosed in the posting.
Ignored 1 non-technology phrase(s) as skills (responsibilities/concepts, not named tools): API design.
Caller marked this a fully-remote role — scored against the national candidate pool.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.