Growth 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

Not verified

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

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

Mid From the posting source checked Jun 20, 2026

Work mode

Onsite From the posting source checked Jun 20, 2026

In-office days

5 days From the posting source checked Jun 20, 2026

Schedule

Shift type

Not verified

Weekend work

Not verified

Application

Cover letter

Not verified

Assessment

Not verified

Deadline

Not stated

Where they hire

State eligibility is not yet verified.

About this role

Growth Engineer San Francisco | OnSite We want to build agents that autonomously validate code changes. Today that looks like AI that reviews pull requests in GitHub, catching bugs and enforcing standards. We're reviewing close to 1B lines of code a month now for over 3,000 companies. Problems we're excited about - Coding standards can be idiosyncratic and are often poorly documented; can we build agents that learn them through osmosis like a new hire might? - Can we identify for each customer what types of PR feedback they do and don't care about, perhaps using some sample efficient RL, in order to increase signal-to-noise ratio? - Some bugs are best caught by running the code, potentially against discerning AI-generated E2E tests. Can we autonomously deploy feature branches and use agents to parallel try to break the application to detect bugs? Trajectory - 7,000+ customers - Raised $30M from Benchmark, YC, Paul Graham, Initialized Team - We have assembled a small, talent dense team who have scaled critical functions at companies like Stripe, Google, Figma, etc. Responsibilities - Own and ship growth-critical engineering projects end-to-end, from identifying opportunities to building, launching, and iterating based on results - Design, build, and run experiments across the full user journey, spanning the marketing website, onboarding, activation, and product interactions - Partner closely with product and growth teams to scope ideas and ship high-quality, production-ready implementations - Build and own the core analytics and attribution framework, including event instrumentation, dashboards, and reporting used to

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