Software Engineer, Models
Meter
Listing collected from Meter's career site. NextChapter is independent of Meter.
San Francisco, CA · Posted April 22, 2026
Will your résumé get you an interview here?
Drop your résumé and see in seconds how well it matches what Meter asks for. Free, no account needed.
Just laid off? Start here: a plan for the first weeks
More in California job market · Software Engineer jobs in San Francisco, CA (442) · All Software Engineer jobs (2,229) · Technology & Software · Engineering jobs
More roles at Meter
- Network Engineer · Phoenix, AZ
- Network Engineer · San Francisco, CA
- Firmware Engineer, Data Centers · San Francisco, CA
- Recruiter · San Francisco, CA
- Backend Engineer, Data Centers · San Francisco, CA
- Network Engineer
Similar jobs
- Forward Deployed Engineer (U.S. Government / IL5) · Uare Ai · San Francisco or Los Altos, CA
- Senior Software Engineer · CommodityAI · San Francisco, CA
- Senior Firmware Engineer · Fellow.app · San Francisco, CA
- Forward Deployed Engineer · Reducto · San Francisco, CA
- Sr Optical Transceiver Firmware Engineer · Super Micro Computer · San Jose, CA
- Sr. Software Engineer - AI/ML · Super Micro Computer · San Jose, CA
Where San Francisco, CA ranks
Where San Francisco, CA placed in our monthly rankings, month by month. Each month stays online at its own address.
November 2026
- #1Cities hosting the most engineering conferences18 conferences · of 27
- #1Cities hosting the most product conferences8 conferences · of 6
- #1Best cities for software and engineering jobs3,732 openings · of 100
- #1Best cities for software and engineering jobs in the West Coast3,732 openings · of 59
- #1Best all-round cities for mid-career professionals88 / 100 · of 100
- #1Best all-round cities for mid-career professionals in the West Coast84 / 100 · of 35
Rankings about engineering jobs
- Best cities for software and engineering jobs #1 San Francisco (3,732 openings)
- Best cities for engineering pay after cost of living #1 San Mateo ($163k)
- Most requested AI skills in engineering jobs #1 AI tools in daily work (6.1%)
- AI tools named most often in engineering jobs #1 Claude (1.7%)
- Employers with the most engineering jobs #1 Amazon (2,360 roles)
Pay compared with the market
This listing does not state pay. Across 541 open software engineer listings that state pay, the middle half runs $153,000 to $240,000 and the median is $195,000.
Listed pay is what employers advertise, not what people are paid.
How AI is used in this kind of work
Among software developers, AI is already used for some of the tasks. Measured exposure for software developers: 29% (some).
Share of this job’s tasks that AI is already used for at work, from real usage. It is not a forecast of job loss, and a low number means no use seen yet. Source: Anthropic Economic Index.
Skills this job asks for
Say which you have and which you want to build. We use it to match you to jobs like this one.
About the job
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 you’ll need to build one. Map the existing landscape: telemetry in ClickHouse, configs in Postgres, support history in Salesforce.
60 days in
Ship a working v1 of the annotation interface. Network engineers should be able to open a historical support ticket, see what the network looked like at the time of the incident, and log their diagnostic reasoning against it. It doesn’t have to be elegant, it has to be useful enough for engineers to want to use it.
90 days in
Our network engineers are generating training data independently without engineering support. The first model benchmarks built from the pipeline are running and you can point to a number knowing the model improved because of what you shipped.
TECH STACK
TypeScript, React, Go, GraphQL, Kafka, Postgres.
WHO YOU’LL WORK WITH
Our co-founder and CEO will lead the product roadmap.
In addition to your customers, network engineers, you’ll partner closely with two research engineers who have deep ML backgrounds and a clear picture of what training data needs to look like. They’re excited to have a partner in building the app.
MEASURING SUCCESS
- Within 90 days, Network engineers are generating training data independently, without pinging you
- We have a large set of high-quality annotated cases in the pipeline
- Model benchmark scores are moving in the right direction because of the data this pipeline produced
WHAT WE’RE LOOKING FOR
You’ve built backend systems end-to-end and made real architectural decisions with real consequences. You have opinions about data storage that come from having made the wrong decisions.
You have deep customer empathy. You’ll spend your first weeks learning how network engineers think and work. This knowledge will shape your future decisions.
You care about people using the tools you built for them. Network engineer tool adoption and satisfaction leads to critical training data, model improvement, and eventually autonomous networks.