Time since we first saw it
Day 58
Similar jobs usually come down between day 7 and day 76.
From 6,389 similar postings that came down. Coming down is not always a hire.
Remote - APAC ( Singapore ) · SF Only · Remote - APAC ( Hong Kong ) · Remote - EMEA ( UK ) · Austin · Singapore
Live, first seen by us 58 days agoLocation type: RemoteFrom the employer’s posting
Employment type: Full-timeFrom the employer’s posting
Department: EngineeringFrom the employer’s posting
Reproduce and evaluate research methods using open-weight and API-accessible models
Design evaluation datasets, baselines, calibration tests, and experiment harnesses
Build evaluation infrastructure such as runners, judges, persistence, and reporting
Turn research workflows into product experiences like runs, traces, and comparisons
Test how verification methods hold up under fine-tuning, merging, quantization, and distillation
Reproduce and evaluate research methods using open-weight and API-accessible models.
Design evaluation datasets, probes, scoring methods, baselines, calibration tests, and experiment harnesses.
Build and extend our evaluation infrastructure, including runners, judges, persistence, experiment orchestration, and reporting.
Turn research workflows into product experiences, including experiment configuration, runs, traces, comparisons, reports, and review workflows.
Investigate how verification methods behave under model modification, including fine-tuning, merging, quantization, distillation, safety removal, and deliberate evasion.
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
Day 58
Similar jobs usually come down between day 7 and day 76.
From 6,389 similar postings that came down. Coming down is not always a hire.
1 open job
Open jobs by the week we first saw them, last 12 weeks.
Hiring recordAdd your resume and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.
What We’re Looking For - Strong Python engineering skills and hands-on experience with PyTorch and Hugging Face Transformers. - A strong understanding of ML evaluation, including dataset design, baselines, metrics, calibration, false positives, false negatives, statistical uncertainty, and reproducibility.
- Comfort working with open-weight models and understanding how modern LLM inference systems operate. - Ability to work across backend and frontend boundaries. Our product surface is primarily React/TypeScript, and you should be able to make complex experiments and results understandable to users. - Strong technical judgment about what experimental evidence does and does not support. For example, evidence that one model was derived from another is not necessarily evidence that it was directly trained on that model's outputs.
- Evaluation and inference infrastructure such as DSPy, LiteLLM, Temporal, Ray, vLLM, PostgreSQL/pgvector, or similar systems. - Next.js, React, TypeScript, data visualization, or experiment dashboards. - Running and serving open-weight models on GPUs and reasoning about latency, throughput, memory, precision, and cost tradeoffs.
- Activation and representation analysis, probing, model hooks, logits, hidden states, or other model-internals work. - Evaluation and inference infrastructure such as DSPy, LiteLLM, Temporal, Ray, vLLM, PostgreSQL/pgvector, or similar systems. - Next.js, React, TypeScript, data visualization, or experiment dashboards.
Complete your application on jobs.ashbyhq.com. The employer’s form will show what is required.
Already applied? Track this application
We’re looking for an Applied ML Engineer to build systems at the intersection of machine learning research and production software.
This is an end-to-end engineering role. You should be comfortable reading a research paper, identifying what is actually testable, building the smallest useful experiment, evaluating it rigorously, and turning the result into a production system that users can interact with.
You’ll work across model evaluation, model internals, inference infrastructure, backend systems, and product interfaces. The goal is not simply to reproduce research. It is to turn promising methods into reliable, measurable, and usable products.
Reproduce and evaluate research methods using open-weight and API-accessible models.
Design evaluation datasets, probes, scoring methods, baselines, calibration tests, and experiment harnesses.
Work directly with model weights, logits, hidden states, activations, model APIs, and inference infrastructure when required.
Build and extend our evaluation infrastructure, including runners, judges, persistence, experiment orchestration, and reporting.
Turn research workflows into product experiences, including experiment configuration, runs, traces, comparisons, reports, and review workflows.
Investigate how verification methods behave under model modification, including fine-tuning, merging, quantization, distillation, safety removal, and deliberate evasion.
Design controlled experiments that separate meaningful signals from artifacts or confounders.
Write clear technical reports that distinguish measured evidence, interpretation, and hypotheses.
Ship production-quality systems with APIs, background jobs, observability, testing, and documentation.
Strong Python engineering skills and hands-on experience with PyTorch and Hugging Face Transformers.
A strong understanding of ML evaluation, including dataset design, baselines, metrics, calibration, false positives, false negatives, statistical uncertainty, and reproducibility.
Ability to read ML research papers and implement methods from first principles rather than relying entirely on existing packages.
Experience building production software beyond notebooks, including APIs, asynchronous jobs, databases, logging, testing, and deployment.
Comfort working with open-weight models and understanding how modern LLM inference systems operate.
Ability to work across backend and frontend boundaries. Our product surface is primarily React/TypeScript, and you should be able to make complex experiments and results understandable to users.
Strong technical judgment about what experimental evidence does and does not support. For example, evidence that one model was derived from another is not necessarily evidence that it was directly trained on that model's outputs.
High agency and a strong sense of ownership. You are comfortable identifying problems, proposing solutions, and driving work forward without waiting for detailed instructions.
Comfortable working in a fast-moving startup environment where priorities can evolve quickly and individuals are expected to operate across functions.
Experience in any of the following is a plus:
Model provenance, fingerprinting, watermarking, distillation detection, red-teaming, safety evaluations, or interpretability.
Activation and representation analysis, probing, model hooks, logits, hidden states, or other model-internals work.
Evaluation and inference infrastructure such as DSPy, LiteLLM, Temporal, Ray, vLLM, PostgreSQL/pgvector, or similar systems.
Next.js, React, TypeScript, data visualization, or experiment dashboards.
Running and serving open-weight models on GPUs and reasoning about latency, throughput, memory, precision, and cost tradeoffs.
Designing adversarial evaluations or testing systems against deliberate attempts to evade detection.
You will:
Reproduce at least one published model-provenance or verification method and clearly document its capabilities, assumptions, and limitations.
Build a repeatable model-verification runner with versioned inputs, artifacts, metrics, and reports.
Add at least one verification workflow to Construct and make it accessible through the Eldros UI.
Run controlled experiments across base models, fine-tuned models, merged models, quantized models, and known distilled models.
Improve our ability to understand when verification methods succeed, when they fail, and why.
Leave behind production-quality code, tests, tooling, and documentation that another engineer can confidently operate and extend.
A pure research role where work ends with a paper or notebook.
A generic model-training or fine-tuning position.
A frontend-only or backend-only engineering role.
A role where benchmark scores are accepted at face value without understanding how they were produced.
A role for someone who wants to stay within a single layer of the stack.
We are looking for someone who enjoys moving between research, experimentation, engineering, and product, and who cares about building systems that produce evidence people can actually trust.
New ML Engineer postings at the employers we follow are down 4% over the last 6 weeks compared with the 6 before.
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.
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.
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.
Selected passages from the saved posting. Check the full description for conditions and exceptions.
No pay amount identified in the saved description.
Singapore
Working pattern and location restrictions need checking in the full posting.
No clear work-authorization passage found. Eligibility is unconfirmed.