Software Engineer, Infrastructure

About the role

The infrastructure team protects revenue by keeping systems operational. Teams depend on this work to prevent lost revenue from downtime. You will own the mechanisms that keep critical systems available, reliable, and performant under pressure. This role requires deep analysis of failure modes and proactive prevention of incidents that interrupt customer workflows. You will partner closely with product and platform teams to ensure streaming platforms and datastores meet strict uptime targets. Clear communication will translate technical safeguards into shared understanding across the organization. You will design and maintain recovery mechanisms that minimize disruption during outages or edge cases. Your work will directly support the company mission of redefining billing software as a strategic growth driver.

Key facts

What you'll do

Recovery mechanisms, tenant isolation, and load spike handling maintain uptime for streaming platforms and datastores to protect revenue.

Observability and operability measures inform infrastructure decisions to stabilize product operations and system performance.

Scaling initiatives handle large customer growth across cloud environments and datastores to avoid service disruption.

Kafka, Spark Streaming, PostgreSQL, Apache Druid, Clickhouse, and AWS deliver reliable product features when partnered with other engineering teams.

Typescript, React, Tailwind CSS, Python, and observability practices spread through knowledge sharing with a talented peer group.

Edge cases, failure modes, and bottlenecks are analyzed to prevent incidents for streaming platforms and datastores.

Tricky errors and performance issues on streaming platforms and datastores are investigated and debugged effectively.

Scalable infrastructure for a high-growth product is built using backend services and frontend interfaces.

Observability, rollout strategies, and risk mitigation are taught to fellow engineers as best practices.

Four or more years of infrastructure experience is required alongside five or more years of software engineering experience.

You will implement tenant isolation strategies to ensure that customer workloads remain secure and performant.

You will diagnose and resolve tricky errors on streaming platforms and datastores under time pressure.

You will design and deliver backend services that scale smoothly with large customer growth in cloud environments.

You will partner with data platform teams to optimize pipelines built on Kafka, Spark Streaming, PostgreSQL, Druid, and Clickhouse.

You will mentor peers on rollout strategies, observability, and risk mitigation to raise the standard of platform reliability.

Requirements

The posting states a bachelor's degree requirement. The posting states a minimum of 4 years of experience.

Edge cases, failure modes, and bottlenecks are analyzed to prevent incidents for streaming platforms and datastores.

Tricky errors and performance issues on streaming platforms and datastores are investigated and debugged effectively.

Scalable infrastructure for a high-growth product is built using backend services and frontend interfaces.

Observability, rollout strategies, and risk mitigation are taught to fellow engineers as best practices.

Four or more years of infrastructure experience is required alongside five or more years of software engineering experience.

You must be able to analyze failure modes and bottlenecks for streaming platforms and datastores.

You must investigate and debug tricky errors and performance issues on streaming platforms and datastores.

You must build scalable infrastructure using backend services and frontend interfaces.

You must teach observability, rollout strategies, and risk mitigation to other engineers.

You must have at least four years of infrastructure experience and at least five years of software engineering experience.

You must hold a bachelor's degree as stated in the posting requirements.

Practical notes

Remote contributors join the team in person once per quarter.

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 role works with streaming platforms, datastores, and cloud infrastructure.

Engineers build backend services and frontend interfaces using modern web technologies.

This is a role focused on reliability, scaling, and platform resilience.

Questions to ask

Useful questions for the interview: what a typical week looks like, how work is assigned, what tools the team uses, and how feedback works. Asking how the role has changed recently and what the team wishes it had known when joining is also reasonable. Questions about the manager's priorities are especially valued.

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.