Software Engineer, Pricing Lifecycle

About the role

Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.

Key facts

What you'll do

Design core pricing lifecycle primitives so that the primitives are extensible and easy to use for product teams.

Evolve the product data model so that complexity is balanced with clarity for users and systems.

Collaborate with product, design, sales, and customer success so that strategy is shaped and value is delivered to customers.

Requirements

5+ years of experience in software engineering so that you can execute on demanding technical work.

Enthusiasm for working on a broad range of technical challenges across the stack so that you can adapt to shifting priorities.

Attention to detail in designing a product with deep user empathy across visual UX, API design, and every interface in between.

Eagerness to engage with customers directly so that the Orb product is shaped by real pain points and feedback.

Willingness to be based in the San Francisco Bay Area or to relocate with support from Orb so that team operations are not disrupted.

Practical notes

Remote roles are asked to join in person once per quarter to maintain collaboration.

The role sits within a small cross-functional team that owns billing, subscription management, and revenue recognition.

Typical interview steps

Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.

Good to know

The tech stack uses TypeScript, React, Tailwind CSS, Python, PostgreSQL, Apache Druid, ClickHouse, Kafka, Spark Streaming, and AWS.

Success depends on customer centricity, attention to detail, ownership, fast execution, and collaboration.

This role focuses on billing, pricing, and revenue workflows within a revenue design platform.

Questions to ask

Good questions to ask the employer in the interview: what does success look like in the first six months, how is the team structured, what is the current biggest challenge, and how are decisions made. Asking about growth paths and the review process is also well received. Employers expect questions, and good ones show preparation.

Career growth

Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.

About the company

Orb is redefining what billing software can be, turning one of the most complex parts of running a business into a strategic driver of growth. We're building the revenue design platform that helps teams automate billing, evolve pricing, and grow revenue with confidence.