Staff Engineer

Benefits

Parental leave

Not verified

Non-birth-parent leave

Not verified

Family-building benefits

• Fertility benefits: Not verified
• Adoption assistance: Not verified
• Surrogacy assistance: Not verified

Mental health support

Not verified

Relocation assistance

Not verified

Childcare support

Not verified

Learning budget

Not verified

Verification

Not verified

Salary

$280K-$400K From the posting source checked Jun 20, 2026

401(k) match

Not verified

Was this benefit information wrong? Tell us.

Market context

U.S. role benchmark (BLS OEWS)

$116,543 U.S. median for this role

Projected growth (BLS Employment Projections)

+9.8% - Much faster than average

192% above the BLS role benchmark for software engineering aggregate.

Matched to SOC 15-1252 - Software Engineering aggregate by role bucket.

Source: U.S. Bureau of Labor Statistics, OEWS, May 2024 and Employment Projections, 2024-2034.

Role

Role function

Engineering From the posting source checked Jun 20, 2026

Seniority

Staff Plus From the posting source checked Jun 20, 2026

Schedule

Shift type

Not verified

Weekend work

Not verified

Company

Equity

Offered From the posting source checked Jun 20, 2026

Application

Cover letter

Not verified

Assessment

Required From the posting source checked Jun 20, 2026

Deadline

Not stated

Where they hire

State eligibility is not yet verified.

About this role

Staff Engineer San Francisco, California, United States ⚠️ Please read first - This is a full-time, in-person role based in San Francisco (Presidio) - we work from the office 5 days a week . - You must be based in the Bay Area or willing to relocate before starting . - We require US work authorisation , but are open to O-1 or J-1 visa sponsorship for exceptional candidates. What You'll Do You've seen what happens when systems hit scale, and you know which parts to rebuild before they break. This isn't a management role. You're the most experienced builder on the team, and the CTO's partner on every architectural decision that matters. Sauna's architecture works today. It won't be optimal at 1000x the current load with 50x the integration surface. You'll make the calls that shape what it becomes. Here are a few examples: - Make hard architectural tradeoffs and own the outcome: Durable Object SQLite vs. shared Postgres for session state. Cloudflare Workers CPU limits vs. longer-running workloads. Single-tenant sandboxes vs. multi-tenant pools. You decide, you migrate, you ship. - Design the system that handles concurrent agent sessions across integrations, an agent responding to an iMessage, checking Calendar, drafting a Slack reply, and updating Linear, all within one session with consistent state. - Define reliability and observability standards for a ~15-person team: SLOs, error budgets, tracing strategy, incident response patterns that actually work at our scale. - Review every significant PR. Set technical direction without blocking velocity. Your

Read the full description at jobs.ashbyhq.com. FewerJobs shows a preview and links to the original posting.