Jobs / United States / hims & hers

hims & hers

Sr. Reliability Engineer

Remote (USA) · Remote · US only Posted today

View original listing ↗ Tailor my CV first Source: Jobicy

Listed on Jobicy: the application continues on their site, which links to the employer. Optional: we can tailor a CV and cover letter for this job from your real experience first (the first one is free).

Skills this job asks for

JiraGraphQLTriage

Add your CV (free) to see which of these your CV is missing.

Where you can work from

United States only

Based on the listing's location: Remote (USA).

The company's headquarters is not the same as where you may work from. Visa sponsorship only matters if you would relocate; see below.

Visa sponsorship, if you would relocate

Sponsorship verdict

No sponsorship evidence yet

No government record and no wording either way. Not a refusal: ask the recruiter.

  • No government sponsor record hereThis employer posted directly and does not match a government sponsor register.
  • The posting doesn’t mention sponsorshipSilence isn’t a refusal — ask the recruiter before investing much time.
  • No salary bar for this routeH-1B has no fixed salary bar: the employer must pay at least the prevailing wage for the role and area.
  • Confirmed live todayWhen a source last listed this job as open.
Details and sources
No salary bar for this route
H-1B has no fixed salary bar: the employer must pay at least the prevailing wage for the role and area. Cap-subject employers enter a lottery weighted by wage level. Source: https://www.federalregister.gov/documents/2025/12/29/2025-23853/weighted-selection-process-for-registrants-and-petitioners-seeking-to-file-cap-subject-h-1b, rules effective 2026-02-27.

US H-1B: cap-subject employers enter a lottery weighted by wage level — Level I gets 1 entry, Level IV gets 4 (DHS projected selection odds ≈15% at Level I to ≈61% at Level IV). Universities and non-profit research employers are cap-exempt. The $100,000 fee for new petitions from abroad is currently blocked by a court order (appeal pending).

A verdict summarises public evidence. It is not legal advice and never a guarantee: the employer and the immigration authority decide. Sign in to factor in where you can already work.

Before you apply

Sponsorship unknown

No register record and no sponsorship wording in the posting. Worth asking the employer before investing significant time.

These come from the posting’s own wording. Read the original listing to confirm. See better-fit alternatives →

About the role

Hims & Hers is the leading health and wellness platform, on a mission to help the world feel great through the power of better health. We are redefining healthcare by putting the customer first and delivering access to care that is affordable, accessible, and personal, from diagnosis to treatment to delivery. No two people are the same, so we provide access to personalized care designed for results. By normalizing health & wellness challenges and innovating on their solutions, we’re making better health outcomes easier to achieve. Hims & Hers is a public company, traded on the NYSE under the ticker symbol “HIMS.” To learn more about the brand and offerings, you can visit hims.com/about and hims.com/how-it-works . For information on the company’s outstanding benefits, culture, and its talent-first flexible/remote work approach, see below and visit www.hims.com/careers-professionals . About the Role: We're looking for a Senior Reliability Engineer to make Hims & Hers systems measurably more reliable: building the observability, tooling, and automation that catch problems before people do. Recent work at this level includes preparing our stack for 32x baseline traffic during high-stakes seasonal surges with zero customer-facing issues and improved P95 latency, turning databases into a paved platform with consistent observability and guardrails, and building AI agents that pull FireHydrant, Datadog, Jira, and Confluence into a single incident picture. We use AI first: every engineer gets a Claude Enterprise license, and we expect you to use it as a core part of how you investigate, build, and write, not as an afterthought. You Will: • Own reliability for Tier 1 customer journeys: Define and instrument SLOs, golden signals, and business-level monitors for the journeys that matter most (checkout, telehealth visits, prescription fulfillment), so that degradation is detected by systems rather than by customers or support tickets. Move our "detected by monitors vs. detected by humans" ratio in the right direction and be able to show it. • Engineer for peak load and failure: Lead capacity and resilience work for high-stakes events and steady-state growth: load-test design, second-by-second analysis of prior events, database and backend bottleneck investigation, and hardening across caching, GraphQL, VPC capacity, and vendor rate limits. Validate before game day, not during it. • Build incident response as software: Mature FireHydrant, Datadog, and Jira into one connected pipeline: automated incident and RCA ticket creation, SLO burn-rate and composite alerting with deduplication, Tier 1 alert routing, and enforced post-mortem action tracking. Author and maintain the runbooks and severity standards that make any responder effective on any service. • Automate operational excellence with AI: Build and operate agents and tooling that reduce manual OE work: OER report generation, RCA drafting, stale action-item detection, monitor and runbook gap detection, and OpenClaw agents wired to Datadog and FireHydrant for first-pass incident triage. Ship these as reusable capabilities, not personal scripts. • Be the deep-debugging expert, and make teams better at it: Teams own debugging their own services, but you are the person they pull in when a problem crosses boundaries: silent service-to-service failures, anomalous traffic, or regressions that span frontend, API, mesh, and database layers. Bring that depth to the hardest cases yourself, then turn what you learn into runbooks, tooling, and pairing so teams can catch and resolve the next one on their own. Partner with Security and product teams on anomaly detection and response, weighing engineering cost and user impact alongside the benefit of any control. • Maintain the tooling that inform

View original listing ↗