Order Management System (OMS) Staff Engineer

Calling all originals: At Levi Strauss & Co., you can be yourself — and be part of something bigger. We're a company of people who like to forge our own path and leave the world better than we found it. Who believe that what makes us different makes us stronger. So add your voice. Make an impact. Find your fit — and your future.

As a Staff Engineer on the Order Management System (OMS) team, you will be an important technical voice. You will shape how we build, operate, and evolve a mission-critical platform. This platform powers commerce at Levi Strauss & Co. You will bring deep software engineering fundamentals to bear on hard problems—designing systems built for scale and untangling complexity so our platform can move faster with confidence. You operate at the intersection of engineering craft and real-world production ownership: you build it, you run it, you make it better.

About the Job

System Design & Architecture

• Lead the design and domain modeling of complex, distributed systems within the OMS ecosystem. This produces clear, well-reasoned service boundaries, data contracts, and event-driven interaction patterns that stand up to scrutiny and scale.
• Champion domain-driven design (DDD) principles, working with product and engineering peers to identify bounded contexts, eliminate implicit coupling, and surface shared language across teams.
• Guide decomposition of monolithic or tightly-coupled components into well-defined, independently deployable services—reducing blast radius, improving team autonomy, and promoting faster iteration.
• Author architecture decision records (ADRs) and technical design documents that communicate the "why" alongside the "what," helping teams make decisions over time.

Engineering Excellence

• Write, review, and guide production-quality code with an emphasis on clarity, testability, and long-term maintainability—setting the bar for engineering craft on the team.
• Apply modern software engineering practices: CI/CD pipelines, automated testing strategies, feature flagging, progressive delivery, and trunk-based development.
• Identify and eliminate technical debt systematically, balancing short-term velocity with long-term system health through well-argued, incremental improvement plans.
• Establish and promote coding standards, patterns, and best practices across the OMS team that are practical, enforceable, and grounded in production experience.

You Build It, You Run It

• Operate with full production: you design with failure in mind, participate in on-call rotations, and take accountability for the health and reliability of the systems you ship.
• Embed reliability engineering into the development lifecycle—defining SLOs, error budgets, and reliability targets upfront rather than as an afterthought.
• Treat runbooks, strategies, and operational documentation as first-class engineering artifacts, keeping them accurate, applicable, and tightly coupled to the systems they describe.

Observability & Operational Intelligence

• Design and implement comprehensive observability strategies—structured logging, distributed tracing, and metrics—so that you can localize any failure mode in production.
• Develop dashboards that give engineers, on-call responders, and partners genuine operational insight into system health—not just uptime pings, but meaningful golden signals and business-relevant Goals.
• Define and tune alerting strategies that are signal-rich and noise-poor—ensuring you wake on-call engineers for relevant events, not symptoms of unrelated upstream noise.
• Champion observability as a design constraint, ensuring you instrument new services and that you make telemetry quality part of every code review and launch checklist.

Scale & Performance

• Design systems that can sustain peak commercial volumes—seasonal traffic spikes, flash sales, and global expansion—without degraded experience or unplanned downtime.
• Apply scalability patterns: asynchronous messaging, event sourcing, CQRS, caching strategies, database sharding, and graceful degradation, selecting the right tool for each problem.
• Conduct and lead capacity planning exercises, load testing, and performance profiling—translating production data into informed infrastructure and architectural decisions.

Troubleshoot & Incident Response

• Be the senior technical resource during complex production incidents—methodically narrowing hypotheses, leading war rooms, and restoring service while preserving forensic evidence for root cause analysis.
• Facilitate blameless post-incident reviews (PIRs) that produce durable improvements—not just immediate fixes, but s