Back to jobs

Software Engineer, Machine Learning

Pay
Pay not listedSimilar roles state $166K–$237K
Work setting
Hybrid — work setting source
Listed location: Mountain View (Hybrid)
Read the full posting
Employment
Full-time — employment source
Employment type: Full-time
From the employer’s posting
Team
Engineering — team source
Department: Engineering
From the employer’s posting
Education & alternatives
- Honest measurement. You would rather retire your own approach after a clean negative result than ship an improvement that disappears under a stronger evaluation. A master’s or PhD in a relevant field, or equivalent work or research experience. Papers, substantial open-source contributions, trained models and well-documented experiments can demonstrate that depth. Experience that would be especially useful

About Ema

Ema builds AI Employees for HR, IT and Finance.

In the employer’s words · Read in context · Company website ↗

Apply at Ema

Posting record

Report an error

Open 3 monthsWe first saw this posting 100 days ago and it is still up. Roles open this long are often slow to fill or kept open to collect applications.

Status in our records
Live
First seen by us
Aug 13, 2026100 days ago
Recorded sightings
92
Last seen by us
Nov 21, 2026

These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.

How this job compares

Pay

$166K–$237K is typical

The middle half of what similar US postings state. This one doesn’t list pay.

From 1,537 postings in the last year. Stated ranges, not salaries paid.

Time since we first saw it

Day 100

Up longer than most. Similar jobs usually come down between day 7 and day 76.

From 6,398 similar postings that came down. Coming down is not always a hire.

Ema is hiring

5 open jobs

Open jobs by the week we first saw them, last 12 weeks.

  • Its jobs tend to stay up a long time
Hiring record

See how this role fits your experience

Add your resume to compare the role’s scope, tools and requirements with your experience.

Your next step

Complete your application on jobs.ashbyhq.com. The employer’s form will show what is required.

Applying through Ashby

  • No account needed. “Autofill from resume” at the top of the form fills the key fields from your file.

Already applied? Track this application

Has Ema posted this job before?

Yes. We’ve followed 2 other Software Engineer, Machine Learning jobs there since June 2026. All 2 are still up.

  1. BengaluruStill up after 173 days, first seen Jun 2
  2. This jobUp 101 days so far, first seen Aug 13
  3. VancouverStill up after 60 days, first seen Sep 23

Job description

View original posting ↗

About Ema

Ema builds AI Employees for HR, IT and Finance. Our AI Employees take on the busy work across the employee experience, from recruiting, onboarding and benefits to IT support, invoice processing and payroll, so people can spend their time on work that needs them. Founded by former executives from Google, Coinbase, Flipkart, and Okta, our team includes engineers from premier tech companies and graduates of Stanford, MIT, UC Berkeley, CMU, and IITs.

We are backed by industry leading investors including Accel, Naspers/Prosus, Creaegis, Section32, and angels like Sheryl Sandberg and Dustin Moskovitz. Headquartered in Silicon Valley and with offices in London, Bangalore and Vancouver, Ema is at the frontier of what Agentic AI can do in production. We ship real systems that run real business processes at scale.

Build agents that learn from the work they do.

Ema builds AI employees that carry out complex workflows across enterprise applications. Our ML team works on the loop that makes them better: production traces become data, data becomes training and evaluation, and better agents produce better traces. The hard part is deciding which intervention will improve behavior in the next real workflow.


The problem space
  • Harnesses and inference-time compute. Design context, tools, skills and orchestration for multi-step agents, including work across documents, slides, images, audio and video. Test where extra reasoning, search or verification earns its latency and cost. Build self-improvement loops with explicit permissions, evaluation gates and rollback.

  • Agent post-training. Curate trajectories for SFT, optimize preferences, or run RL on real agent tasks. Investigate methods such as DPO, GRPO or DAPO where they fit; compare process and outcome supervision, shape rewards, and distill useful frontier behavior into smaller models. Measure whether gains transfer beyond the training environment.

  • Environments and rewards. Turn enterprise workflows into reproducible training and evaluation environments: fixture tenants, simulated users who may get impatient and leave, and rewards grounded in verifiable outcomes. Find the shortcuts an agent can exploit before a training run optimizes for them.

  • Data engines and evaluation. Mine production agent-steps for failures; build curated corpora and useful synthetic augmentation. Calibrate judges against human labels, construct behavior-level benchmarks from real workflows, and quantify data quality, performance uplift and reliability across stochastic runs.

  • Retrieval, memory and context graphs. Connect enterprise information with user- and tenant-level learnings. Separate failures of retrieval from failures to use retrieved context; test what to retain, update and retrieve so that past experience improves the next decision.

  • Quality per dollar. Build and evaluate routing, ensembles, caching and small-model specialization. Measure downstream task success alongside latency and cost; a cheaper model is useful only if the complete agent still succeeds.

You’ll go deep in a subset of these areas. Projects combine applied research with the engineering needed to make the result work in production.


Own the experiment and the system

Most projects develop over roughly four to six months, with useful improvements shipping along the way. You’ll define the problem and baseline, build the data or environment needed to test it, run experiments, and own serving and integration. Follow the system through deployment, monitoring and failure analysis until it is ready for a clear engineering handoff.

You’ll work with researchers and engineers across the Bay Area, Vancouver and India. We’re hiring from junior through senior levels, with project scope matched to your experience.


What we’re looking for
  • Depth you can defend. Substantial work in at least one of agent/tool-use systems, post-training, reward modeling or RL environments, retrieval and memory, or evaluation design. Be ready to explain the mechanism, the alternatives you rejected and the failure modes you found. One area you can teach us beats five you’ve touched.

  • Evidence of zero-to-one ownership. A system, model or research project you took from an ambiguous problem to a working result. We want to understand your contribution, the tradeoffs you made, and what changed when the work met real users or realistic tasks.

  • Statistical judgment. You can size an experiment, choose meaningful baselines and held-out tests, and account for variation across tasks, seeds and repeated runs. You can distinguish a real improvement from judge bias, data leakage or a benchmark shortcut.

  • Production engineering judgment. You can debug across the model and system boundary, isolate a failure, and turn the result into maintainable production code.

  • Honest measurement. You would rather retire your own approach after a clean negative result than ship an improvement that disappears under a stronger evaluation.

A master’s or PhD in a relevant field, or equivalent work or research experience. Papers, substantial open-source contributions, trained models and well-documented experiments can demonstrate that depth.


Experience that would be especially useful
  • Open-model post-training with TRL, veRL, OpenRLHF, or similar or a custom loop, especially debugging reward hacking or unstable optimization.

  • Interactive agent environments/harnesses for software engineering, web or tool use; large-scale trace analysis, data curation or synthetic generation.

  • Designing systems to support complex, long-horizon agent work across a multitude of modalities and platforms

  • Serving with vLLM or SGLang, distillation, quantization, or multi-node GPU training.

  • Practical security work on prompt injection, data governance or permission boundaries for agents that can act and improve themselves.

These are project-specific strengths; post-training experience is optional, and no candidate needs the entire list. Bring a repository, paper, model or technical write-up that lets us examine how you think and what you built.

Compensation offered will be determined by factors such as location, level, job-related knowledge, skills, and experience. Certain roles may be eligible for variable compensation, equity, and benefits.

Ema Unlimited is an equal opportunity employer and is committed to providing equal employment opportunities to all employees and applicants for employment without regard to race, color, religion, sex, national origin, age, disability, sexual orientation, gender identity, or genetics.

Demand for ML Engineer roles

New ML Engineer postings at the employers we follow are down 4% over the last 6 weeks compared with the 6 before.

Weekly new ML Engineer postings at the same employers, from the week of August 17 to the week of November 9. The fewest in a week was 508, the most 899, and the latest week had 508.
August 17Last week

Each bar is one week of new postings. The darkest bars are the last 6 weeks.

Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.

About the role

We file this job under ML Engineer, by the work the posting describes.

ML engineers put machine learning models into products. They write the code that trains, ships, serves and monitors models so a recommendation or prediction works for real users.

Postings ask for strong Python and software engineering, a framework such as PyTorch, cloud services, and more and more often experience with large language models.

A data scientist often works out which model to build; an ML engineer makes it run reliably in production.

US government figures for computer and information research scientists

Median yearly pay, May 2025
$140,300
Expected change, 2025 to 2035
21.8% more jobsagainst 3.5% for all jobs

The government has no code for ML engineers, so these figures are for the closest group, computer and information research scientists.

Source: US Bureau of Labor Statistics, Occupational Employment and Wage Statistics (May 2025) and Employment Projections (2025 to 2035). Occupation code 15-1221.

Source details

View original posting ↗

Source notes

Source excerpts

Selected passages from the saved posting. Check the full description for conditions and exceptions.

Pay

No pay amount identified in the saved description.

Location & working pattern

Mountain View (Hybrid)

Working pattern and location restrictions need checking in the full posting.

Work authorization

No clear work-authorization passage found. Eligibility is unconfirmed.

Find answers in the posting

AI
How answers work

AI selects complete passages from this posting. Check them for conditions and exceptions.

Uses this posting and your question. No profile needed.