About the Role As the first machine learning engineer on the team, you will build the ML foundation for software that helps improve farm operations. You will turn fragmented agricultural data into carefully evaluated for…
Machine Learning Engineer jobs in San Francisco, CA
Machine learning engineers take models from notebook to production — building training pipelines, serving infrastructure, and monitoring so ML systems keep working after launch.
No email, no resume, no sign-up. Save any listing below and you start anonymously.
You're signed in. Saving a listing drops it straight into your pipeline.
Open machine learning engineer roles
11 shown of 2,282 · sorted by freshness
current delivery mechanism. The real product is a scalable risk engine, our Stand World Model . We stay when traditional insurers... ...and operate with far less friction. Role Summary: As a Machine Learning Engineer on…
The Role: As a Machine Learning Engineer at Sift, you will bridge the gap between data science and large-scale distributed systems. You won’t just train models in isolation; you will build end-to-end pipelines that extra…
About the Role We're looking for founding Machine Learning Engineers (MLEs) to own and improve our core action models end-to-end - the intelligence that powers Composite's proactive automation platform. You'll work at th…
people the fastest, and also allow us to learn as much about the brain as possible: developing... ...each other. About the role As a Machine Learning Lead at Nudge, you will drive... ...Partner closely with mechanical en…
over $100M from world-class investors including a16z, Benchmark, and First Round Capital. The Opportunity As an ML Infra Engineer , you’ll play a key role in building the inference and training frameworks that make it po…
About the Role Together AI is seeking a Machine Learning Engineer to join our Inference Engine team, focusing on optimizing and enhancing the performance of our AI inference systems. This role involves working with state…
recruiting process here . With more than 600 million users around the world and 300 billion ideas saved, Pinterest Machine Learning engineers build personalized experiences to help Pinners create a life they love. With j…
Responsibilities Design, train, and evaluate machine learning models for production use cases. Build end-to-end ML pipelines covering... ..., model serving, and monitoring. Partner with product, engineering, and domain e…
training, experiment design and evaluation. The role suits an engineer who can move quickly, test ideas rigorously and extend the... ...software engineer transitioning into AI research, or an AI or machine learning engin…
time driver pricing for billions of rides. Engineers on the team work on cutting-edge... ...tracked career growth and the opportunity to learn from experienced technical leaders.... ...approaches for online marketplaces…
What machine learning engineers earn in San Francisco
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $61–$84 | $126k–$175k |
| Mid level | $84–$114 | $175k–$238k |
| Senior | $111–$155 | $231k–$322k |
Adjusted for the San Francisco market from national ranges.
What employers ask for
The skills these listings keep naming
Interview questions worth rehearsing
With the thing the interviewer is actually listening for
Walk me through taking a model from prototype to production.
Cover data pipelines, training reproducibility, serving, and monitoring. Emphasize that the model is a small part of the system — that framing is the job.
How do you monitor a model in production?
Discuss input drift, prediction distributions, delayed labels, and business metrics — plus what triggers retraining. Mention that silent degradation is the default failure mode.
How would you reduce inference latency or cost for a large model?
Options include distillation, quantization, batching, caching, and smaller models. Frame it as measuring first, then choosing the cheapest acceptable quality tradeoff.
Tell me about a time a model failed in production. What happened?
A real story about skew, drift, or a data bug — with detection and prevention — is far more convincing than claiming smooth deployments.
How do you evaluate a model beyond accuracy?
Talk about the metric matching the business cost of errors, slicing by segment, and offline-online gaps. Naming a case where accuracy misled is a strong touch.
When would you fine-tune an LLM versus use retrieval or prompting?
Start cheap: prompting, then RAG for knowledge, fine-tuning for behavior and format. Cost and maintenance burden should drive the answer.
How do you make training reproducible?
Version code, data, and config; track experiments; pin environments. This is engineering discipline applied to ML, which is exactly the role.
Resume tips that move the needle
For machine learning engineers specifically — generic advice costs you here
Center bullets on production systems: models served, request volume, latency, and the business metric they moved.
Show software engineering credentials explicitly — testing, CI, code review — since MLE hiring filters hardest on engineering rigor.
Name the MLOps tooling you have run (MLflow, SageMaker, Kubeflow, vector databases) as these are common screens.
Include LLM work with specifics — fine-tuning, RAG, evaluation — if you have it; vague 'GenAI experience' claims read poorly.
Distinguish your role on shared projects: built the serving layer, owned the pipeline, or trained the model.
Where this role goes
Typical progression
Applying for machine learning engineer jobs in San Francisco?
Robbi carries this page into your first day: your role, your city, your shift preference. Then it hands you a few small things each morning and keeps the pipeline honest.
Save what looks right here, then let Robbi hand you a few small things each morning and keep the follow-ups honest.