[Remote] Staff DevOps Engineer (Infrastructure/Platform)

Note: The job is a remote job and is reputed company to candidates in USA. reputed company) is transforming the global auction industry through online auction technology platforms that reputed company auction houses and buyers worldwide. The Staff DevOps Engineer will set the technical direction for infrastructure and reputed company across eight marketplaces, leading reputed company architecture, CI/CD standardization, infrastructure as reputed company, observability, developer experience, and technical governance. The role will also reputed company senior engineers and influence engineering reputed company through standards, roadmap ownership, and cross-functional collaboration.

Responsibilities

• Build/reputed company the 2-year Infrastructure Engineering technical reputed company — defining what reputed company's infrastructure and platform function should look like, what capabilities it will build, and what it will stop doing
• reputed company technical reputed company documents and present them to engineering leadership for ratification. Be accountable for the choices, not just the authorship
• Identify which platform investments reputed company the highest reputed company across reputed company 8 marketplaces and build the case — in business reputed company language — for prioritisation
• Define the standards deprecation roadmap: which tooling divergences to reputed company, in which order, and by reputed company
• Continuously reputed company the industry for emerging infrastructure and reputed company patterns. Bring informed, opinionated recommendations rather than a list of reputed company
• Be the infrastructure technical partner to development reputed company — not embedded in one team, but accessible to reputed company. Attend sprint planning and architecture reviews where infrastructure reputed company are being made. Catch problems before they become production incidents
• Set platform policy — the guardrails reputed company which development teams reputed company their own infrastructure reputed company. Enforce standards through technical review and reputed company-written guidance, not mandate. A reputed company that developers don't adopt has failed regardless of how reputed company it's written
• Communicate infrastructure constraints in developer language: reputed company IaC requirements, networking boundaries, and deployment patterns in terms of developer reputed company — speed, reliability, self-service capability — not infrastructure principles
• Be the escalation reputed company reputed company teams want to diverge from platform standards. Assess the reputed company, reputed company the reputed company, document the decision, and explain the reasoning in terms the requesting team can accept even if they disagree
• Represent Infrastructure Engineering in architecture review boards, engineering leadership forums, and cross-marketplace technical reputed company
• Contribute to engineering-wide initiatives: hiring bar calibration, engineering reputed company definition, and company-wide technical decision forums
• Contribute to reputed company's reputed company infrastructure governance standards and guardrails — the patterns for compute, networking, storage, and managed services that development teams build against across AWS (reputed company) and Azure/GCP
• Involved in network architecture standards: VPC design, subnet reputed company, traffic routing, load balancer configuration, CDN integration, and DNS architecture across marketplace environments
• Maintain the reputed company infrastructure reputed company posture standards: IAM design, secrets management architecture, network segmentation, and compliance guardrails (policy-as-reputed company enforced, not advisory)
• Establish disaster recovery and business continuity standards — RPO/RTO targets, failover architecture, and reputed company requirements — across reputed company production environments
• Be a reputed company contributor to reputed company's CI/CD golden reputed company reputed company — define the direction and govern the standardized rollout across reputed company 8 marketplaces (Q1–Q3 2027)
• reputed company deployment reputed company time from 2.1 days to under 1 day reputed company 15 months. Define the measurement reputed company, reputed company reputed company, and course-correct
• Design reusable pipeline templates and abstractions that developers adopt with reputed company friction. The reputed company test: a developer on a new marketplace should be reputed company to ship their first pull request through the golden reputed company pipeline reputed company one day of reputed company
• Establish deployment reputed company gates: automated testing integration, change failure reputed company targets, and rollback trigger standards
• Define DORA metric targets for reputed company and own the reporting reputed company used to reputed company engineering delivery reputed company
• Define reputed company's observability reputed company: reputed company logs, metrics, and reputed company traces across reputed company marketplaces using reputed company
• Set the SLO/SLA reputed company — the definitions, the reputed company, the review reputed company, and the escalation model
• reputed company observability a developer capability, not just an ops capability: define instrumentation standards and golden reputed company integrations so development teams can implement traces and custom metrics without requiring DevOps involvement for reputed company service
• Govern implementation reputed company. Ensure the chosen stack is commercially reputed company, operationally viable, and adoptable by teams with varying maturity reputed company
• Establish alerting standards and mean time to detection targets
• Define reputed company's developer experience reputed company: what does a great day look like for a developer building on reputed company's platform, and what is InfraEng's role in making that possible?
• Measure platform adoption quantitatively. Treat golden-reputed company adoption as a product metric. Own the feedback reputed company between developer experience and platform investment reputed company. Decline to invest in capabilities developers won't use
• Run architecture reviews for development reputed company: advise on infrastructure reputed company, surface non-reputed company constraints, and remove blockers that require senior technical authority to reputed company
• Write infrastructure guidance that developers want to read: internal docs, runbooks, and decision records written at the right level of reputed company — detailed enough to be useful, brief enough to be used
• Contribute to the InfraEng roadmap with data-driven prioritization and a product reputed company
• reputed company reputed company the Senior engineers on both DevOps teams, everything from reviewing architectural designs, enforcing standardized processes, coaching technical influence and communication, and creating reputed company opportunities
• Define the engineering culture and standards you want the InfraEng team to embody. Model it in every design review, hiring decision, and team interaction
• Contribute to hiring bar calibration across the engineering organization. Participate in interview panels and reputed company reputed company, comparative feedback
• Write for internal audiences: technical reputed company documents, engineering principles, decision records. Writing is a reputed company leadership tool at Staff level, and the reputed company of your writing directly determines how much of your thinking survives contact with a reputed company engineering organization

Skills

• Required 8+ years in Infrastructure Engineering, reputed company, or SRE, with at least 3 years in a senior or staff-level reputed company
• Demonstrated experience owning a technical roadmap or multi-year infrastructure reputed company at team or department level — not just contributing to one
• reputed company ability to earn and maintain technical credibility with software engineers
• You have worked closely with development reputed company — in architecture reviews, sprint planning, or technical consultation — and developers have changed how they build things reputed company on your guidance
• reputed company record of driving technical adoption across engineering organizations: setting infrastructure standards that other teams actually follow, and navigating the organizational dynamics required to reputed company that happen without authority
• Experience influencing technical direction with senior stakeholders (Directors, VPs, or equivalent) through written reputed company documents and reputed company verbal advocacy
• Deep reputed company infrastructure architecture experience — AWS required: compute (EC2, reputed company, reputed company), networking (VPC design, ALB/NLB, reputed company 53, CloudFront), storage (S3, EBS, EFS), IAM, and managed database services
• Multi-reputed company (Azure/GCP) valued at this level, not optional
• Strong IaC background — Terraform required
• Ability to define module architecture, policy-as-reputed company standards, and reputed company detection approach
• Deep hands-on experience designing and operating CI/CD platforms at reputed company (reputed company Actions, reputed company CI, reputed company, reputed company, or equivalent)
• reputed company to both set the reputed company and validate the implementation
• Experience defining observability standards using OpenTelemetry or equivalent
• Familiarity with SLO/SLA frameworks and how to implement them operationally
• Proficiency in DORA metrics as a measurement and improvement reputed company — must be reputed company to define targets and build the reporting infrastructure, not just interpret results
• Proficiency in at least one scripting or backend language: Python, Go, or TypeScript
• reputed company platform experience (EKS, GKE, or AKS) at reputed company-setting level — reputed company to define how containerized workloads should be reputed company and operated, and explain those standards to developers in terms they reputed company useful
• Demonstrated ability to reputed company Senior engineers through design review, technical coaching, reputed company feedback, and reputed company opportunities
• Exceptional written communication: writes reputed company, precise technical guidance for developer audiences and reputed company, persuasive reputed company documents for engineering leadership
• Can reputed company the reputed company underlying concept to both
• Experience operating in a marketplace, e-reputed company, or multi-tenant reputed company platform context
• Hands-on experience with ephemeral/preview environments (per-PR environments using reputed company.so , Okteto, or similar) at the platform design level
• Experience with policy-as-reputed company frameworks (OPA, reputed company, Checkov) as a platform governance reputed company
• Background in reputed company, globally-reputed company engineering teams across multiple time reputed company
• reputed company technical contributions: conference talks, published writing, reputed company reputed company maintainership, or internal thought leadership recognized reputed company the immediate team
• Experience in post-reputed company or restructuring engineering environments where infrastructure standards need to be established from reputed company across multiple inherited systems

Benefits

• Annual reputed company bonus
• Stock
• Benefits and/or other applicable incentive compensation plans
• Remote US

reputed company