Software Engineer, Models

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

Hybrid From the posting source checked Jun 20, 2026

In-office days

2 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

Software Engineer, Models San Francisco | Hybrid | Remote WHY THIS ROLE EXISTS Network engineers carry the most valuable signal in the world in their heads, and it disappears the moment they close a ticket. Your job is to build the system that captures that signal so that our models can learn to think like network engineers. If you get this right, Meter can manage thousands of customers' networks autonomously, without adding a single engineer. THE PROBLEM YOU'RE WALKING INTO LLMs are good at code because of their access to Git. Commit messages explain why a change was made, PR threads capture expert disagreement, issue trackers record dead ends and eventual fixes. Models trained on that corpus of data don't just pattern-match, they've seen millions of examples of human reasoning through problems. Network engineering has none of this. When a network engineer looks at a set of device stats and figures out it's upstream packet loss - not a hardware failure, not a misconfiguration, specifically upstream packet loss - that reasoning lives in their head. Never in a place a model can learn from. You will build the Git and Github for network engineering. A structured, queryable record of what the network looked like, what the expert notice, and why they made the call they made. WHAT YOU WILL SHIP First 30 days Sit with our network engineers and watch how they work. Don't touch code yet. Understand what a great diagnostic reasoning record actually looks like and what data

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