Sentient Labs
Applied ML Engineer

How your CV stacks up
Upload your CV to see how well it fits this job role
?%
The Role
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.
What You’ll Do
- 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.
Reasons to use Rodeo
I’m in my final year doing Economics and I don’t know whether to apply for grad schemes now or do a masters first. What do you think?
Honest answer — it depends on where you want to end up. A lot of top grad schemes (Big 4, civil service, banking) don’t need a masters. Let’s look at the ones you’d be competitive for now, and we can decide if a masters actually adds anything.
Also worth knowing: most autumn 2026 applications are open now. Timing matters more than you think.
Start with a chat, not a search bar
Grad scheme, placement, apprenticeship? Not sure what you want yet — that's fine. Your agent talks it through with you and turns "I have no idea" into a shortlist.
Graduate Consultant — 2026 Scheme
Why you're a good match
StrongYour economics background and your summer at a regional bank line up with what PwC looks for on the consulting scheme. Applications close in four weeks.
See breakdownIt searches the market for you
Every day your agent scans the market matching roles against what actually matters to you, not just keywords on a CV.
Why you're a good match
You’ve got the grades and the economics background, and your bank internship is exactly the experience this scheme looks for. Apply soon — deadlines close within the month.
Experience fit
Your summer at the bank plus your econometrics coursework map directly to the day-one responsibilities on this scheme — client modelling, market briefings, and deal support.
Only hits
No noise. No "maybe this fits." Just roles with a clear explanation of why they're right — and where to focus when applying.
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.
- 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.
Useful Experience
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.


Get help with your application
Your very own career expert that helps elevate your application to the next level.
What Success Looks Like in the First Six Months
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.
This Role Is Not
- 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.
“It took my CV and asked me questions relevant to understanding what kind of jobs to suggest for me. Suggestions were almost perfect. Jobs were exactly what I’ve been looking for.”
Jessica, London
Location