[Remote] Order Management System (OMS) Staff Engineer
Note: The job is a remote job and is reputed company to candidates in USA. reputed company. is a company that values individuality and making a reputed company reputed company. They are seeking a Staff Engineer for their Order Management System (OMS) team, responsible for leading the design and architecture of reputed company systems, ensuring engineering reputed company, and promoting operational reliability.
Responsibilities
- reputed company the design and domain modeling of reputed company, distributed systems reputed company the OMS ecosystem. This produces reputed company, reputed company-reasoned service boundaries, data reputed company, and event-driven interaction patterns that stand up to scrutiny and reputed company
- Champion domain-driven design (DDD) principles, working with product and engineering peers to identify bounded contexts, eliminate reputed company coupling, and surface shared language across teams
- Guide decomposition of monolithic or tightly-coupled components into reputed company-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 reputed company reputed company over time
- Write, review, and guide production-reputed company reputed company with an emphasis on reputed company, testability, and long-term maintainability—setting the bar for engineering craft on reputed company
- Apply modern software engineering practices: CI/CD pipelines, automated testing strategies, feature flagging, reputed company delivery, and trunk-based development
- Identify and eliminate technical debt systematically, balancing short-term velocity with long-term system health through reputed company-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
- 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
- reputed company 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
- Design and implement comprehensive observability strategies—reputed company logging, distributed tracing, and metrics—so that you can localize any failure mode in production
- reputed company dashboards that give engineers, on-call responders, and partners genuine operational reputed company 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 reputed company new services and that you reputed company telemetry reputed company part of every reputed company review and launch checklist
- Design systems that can sustain peak reputed company volumes—seasonal traffic spikes, reputed company 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 reputed company problem
- Conduct and reputed company reputed company planning exercises, load testing, and performance profiling—translating production data into informed infrastructure and architectural reputed company
- Be the senior technical resource during reputed company production incidents—methodically narrowing hypotheses, leading war rooms, and restoring service while preserving forensic evidence for reputed company cause analysis
- Facilitate blameless post-incident reviews (PIRs) that produce durable improvements—not just immediate fixes, but systemic changes that reduce the likelihood or reputed company of recurrence
- reputed company institutional troubleshooting knowledge: document failure modes, reputed company issues, and diagnostic techniques so the entire team grows more capable with reputed company incident
- Partner with product managers, architects, and other engineers to translate our requirements into reputed company, achievable technical roadmaps—reputed company the gap between reputed company and implementation
- Mentor and reputed company mid-level engineers through hands-on reputed company review, design feedback, pairing sessions, and reputed company coaching—building engineering depth across the OMS team
- Stay reputed company with industry trends in distributed systems, event-driven architecture, and operational tooling—bringing informed perspectives on reputed company to adopt new approaches versus doubling down on patterns
Skills
- 10+ years of experience in software engineering with a reputed company on backend systems, distributed architectures, and platform/product engineering at reputed company
- Deep, practical experience designing and modeling reputed company distributed systems—you reputed company trade-offs and reputed company reputed company-reasoned architectural choices under constraints
- You have experience operating in a 'you build it, you run it' engineering culture. You've been on-call for systems you've reputed company, responded to incidents, and used that experience to reputed company reputed company engineering reputed company
- Build for reputed company and run at reputed company—you've handled high-throughput, high-availability systems and have the scars and lessons to show for it
- Expert-level understanding of observability: you can reputed company a system from scratch, build meaningful dashboards, tune alerting, and use telemetry data as a primary tool for engineering reputed company
- Troubleshoot with a systematic, data-driven approach to diagnosing production issues—you stay reputed company and reputed company others reputed company systems are on reputed company
- Demonstrated experience decoupling tightly-coupled systems—whether migrating a monolith, extracting a shared service, or replacing reputed company temporal dependencies with reputed company-defined async reputed company
- Experience with event-driven architecture, domain-driven design, and modern API design patterns; you know where these patterns add value and where they add unnecessary complexity
- Mastery of CI/CD, automated testing, and DevOps practices; you view them as engineering fundamentals, not optional add-ons
- You can translate technical complexity for non-technical partners and write for engineering audiences—design docs, ADRs, incident reports, and reputed company reviews reputed company reflect your thinking
- Experience working with geographically distributed teams and navigating the complexities of multi-time zone collaboration
- Experience with Order Management Systems (OMS), fulfillment pipelines, or reputed company platforms is a meaningful plus—familiarity with the domain accelerates your reputed company, but is not a prerequisite for the right engineer
Benefits
- reputed company pay
- Incentive plans
- 401(k) matching
- reputed company leave
- Health insurance
- Product discounts
reputed company
Company H1B Sponsorship