Order Management System (OMS) Staff Engineer

About the role

As a Staff Engineer on the Order Management System (OMS) team at Levi Strauss & Co., you will be a key technical voice shaping a mission‑critical commerce platform. You will design, build, operate, and continuously improve large‑scale distributed services that power the company’s e‑commerce experience.

Key responsibilities

• Lead system design and domain modeling for complex, distributed OMS services, defining clear service boundaries, data contracts, and event‑driven interaction patterns.
• Champion domain‑driven design (DDD) principles, identify bounded contexts, and reduce implicit coupling across teams.
• Guide the decomposition of monolithic components into independently deployable services to improve autonomy and iteration speed.
• Author architecture decision records (ADRs) and technical design documents that explain the rationale behind architectural choices.
• Write, review, and maintain production‑quality code with a focus on clarity, testability, and long‑term maintainability.
• Apply modern engineering practices such as CI/CD pipelines, automated testing, feature flagging, progressive delivery, and trunk‑based development.
• Identify and systematically eliminate technical debt while balancing short‑term velocity with long‑term system health.
• Establish and promote coding standards, patterns, and best practices across the OMS team.
• Operate the system in production: design for failure, participate in on‑call rotations, and own reliability targets.
• Embed reliability engineering by defining SLOs, error budgets, and maintaining accurate runbooks and operational documentation.

Required profile

• Deep software engineering fundamentals with experience tackling hard problems at scale.
• Strong background in designing and operating distributed systems.
• Ownership mindset: you build it, you run it, and you continuously improve it.

Required skills

• Domain‑Driven Design (DDD)
• Distributed systems design and architecture
• CI/CD pipelines
• Automated testing strategies
• Feature flagging
• Progressive delivery
• Trunk‑based development
• Service boundaries, data contracts, event‑driven interaction patterns
• Reliability engineering (SLOs, error budgets)