Skip to main content

Orb

Software Engineer, Real Time Analytics - San Francisco HQ

HQ-San Francisco (Remote)$165k–$225kfulltimemidAdded today

About this role

Join Orb's real-time analytics team to build the runtime layer that powers billing state for usage-based businesses. You'll own entitlements, spend controls, and usage analytics end-to-end—designing systems and APIs that let customers make informed billing decisions at scale with guaranteed latency.

What you'll do

  • Own product surfaces end-to-end from customer discovery through API design, implementation, and rollout
  • Design and ship alerting and analytics that meet contractual latency SLAs while remaining flexible and granular
  • Build credit balances, allocations, usage alerts, and rate limits that enforce against real billing state in real time
  • Shape foundational roadmap, primitives, and interfaces that other teams depend on
  • Collaborate directly with enterprise and AI customers to translate pain points into features
  • Balance systems engineering (performance, reliability) with product-focused API and UX design

What they're looking for

  • End-to-end product ownership and systems design
  • Real-time and low-latency systems engineering
  • API and data model design
  • Python backend development
  • SQL and analytics databases (PostgreSQL, Druid, Clickhouse)
  • Kafka and event streaming platforms
  • Customer empathy and product instincts
  • Attention to detail in API design and UX
Apply on the employer's site

Opens the official application on the employer’s site. No login required.

Orb

Orb builds reliable billing software designed to meet customer needs at scale. The company is hiring Software Engineers for core product and infrastructure teams to develop resilient systems, improve observability, and support growth.

View all jobs at Orb

Likely interview questions

  • Walk us through a time you owned a product or system end-to-end—what was the biggest challenge in balancing technical constraints with customer needs?
  • How would you approach designing an API for real-time entitlement checks that needs to meet strict latency SLAs while staying flexible for different billing models?
Unlock all 7 questions free — and practice them live →