AI developer recruitmentClients in the UK, Europe and USA

Every CV mentions LLMs now. Who can ship an AI feature you can trust?

If you are building products on top of models, you need an engineer who can make retrieval, evaluations, agents and API integrations reliable. An engineer reads every CV first, so you only interview the ones who can.

Where your hiring time goes

01

The re-screening tax

AI experience is the easiest thing to add to a CV and the hardest to check. A side project that calls a model and a production retrieval system look the same on paper. So every CV gets a second read from your most technical person, and the difference often only shows in the interview.

02

The CV stopped being evidence

The CV saysRAG, embeddings, vector databases
It can’t tell youWhether they can separate retrieval failures from generation failures, and judge embedding and reranking quality.
The CV saysLLM integration
It can’t tell youHow they stop low-quality or unsafe output from silently reaching your users.
The CV saysEvaluation, MLflow
It can’t tell youWhether their evaluations catch a regression before your users do.

If you run hiring for engineering

You need CVs that pass engineering’s interview, so you can send a shortlist it trusts. An engineer reads every CV before it reaches you. Fewer CVs, but better ones.

58%

of HR and recruitment leads who use agencies say the main reason engineering rejects agency candidates is that the CV looked good, but the person couldn’t do the job.

Source: our October 2026 survey of 134 HR and recruitment leads.

What the CV can’t tell you, and our interview does

A developer or CTO who works in the stack interviews every candidate. Each of these is a question you would otherwise only answer in your own interview.

Can they make retrieval work?

Whether they can design retrieval, reason about embedding and reranking quality, and separate retrieval failures from generation failures.

Do they measure quality?

Whether they build meaningful offline and online evaluations, so a prompt or model change is a measured decision and regressions are caught.

Can they integrate models safely?

How they handle model failures, latency, cost and confidential data, how they limit what an agent is allowed to do, and how they stop low-quality output from silently reaching users.

Need someone who trains models?

We find model-training specialists too. For those roles we test architecture, training dynamics, fine-tuning methods such as LoRA and QLoRA, evaluation for regressions and catastrophic forgetting, and serving on GPUs.

What every shortlisted candidate has to show

Knows what the model is doing

They understand what happens between the prompt and the answer, and can investigate a bad output instead of rewording the prompt until it goes away.

Uses AI with engineering discipline

They can explain how they verify generated code and model output, protect confidential data and stay accountable for what the feature does in production.

Honest about what the evidence shows

They resist overstating what a model can do, and say plainly what they have built, what they have not and what the evaluation does and does not prove.

How we take the screening off your desk

We recruit AI engineers who build products on top of models, and machine learning, LLM and AI research engineers who train and adapt them. Every candidate is screened on retrieval, evaluation, model integration and production reliability, with training depth assessed where the role needs it.

Either way you get about 3 to 5 screened CVs a week, per role.

Route 1: we screen, you run the deep interview

We do

  • Source candidates for the role
  • A technical screen of every candidate, run by a developer or CTO who works in your stack
  • A CTO approves every CV before it reaches you

You do

  • Run the deep technical interview with the shortlist
  • Make the offer

Route 2: we run the deep interview too

We do

  • Everything in Route 1, including the technical screen of every candidate
  • A 1.5 to 2 hour live-coding, architecture and implementation interview with your final candidates
  • A written assessment of each candidate after the interview

You do

  • Meet the candidates who passed
  • Make the offer

Teams we have hired for

eLockerOmnamBallerineHargreaves Lansdown

What clients say

“Metamindz helped us recruit our now CTO, reviewing CVs as they came in and then putting the CTO through a thorough 90-minute live 360 technical test. Feedback from our now CTO of the test was glowing and comms from Metamindz throughout the entire process were excellent. Highly recommend!”

Rupert Boddington

Co-Founder, Pockla

“Worked with Lev and Max. We worked with MetaMindz to help us interview and assess software engineering candidates. They were professional and great from the outset and throughout, great speed too. Would 100% recommend and we will be working with them again.”

Alexander Bushe

CEO, Fuller Focus

“We found it really easy working with Lev and the team to hire for our lead developer role and despite it still being early days, our new hire is making an impact already!” source

Billy Whiffen

Google review

Case studyeLocker

Five hires, and management time back for building product

5
hires across engineering and leadership roles
~90
candidates reviewed for eLocker's team
80%
retention: 4 of the 5 hires still in place, one left after more than a year due to career growth
  • Senior engineer

    Built the AI front end, set up a design system that removed the need for Figma, and architected analytics properly.

Impact as described by Billy Whiffen, eLocker.

What it costs

£5,000

Fixed fee for your first role

15% to 17%

Commission on each further hire

Included

  • Sourcing and screening
  • A technical screen of every candidate by a developer or CTO
  • A CTO approves every CV before you see it
  • About 3 to 5 screened CVs a week, per role
  • No exclusivity required
  • A 3 to 6 month guarantee, depending on seniority

Optional extra

  • Deep technical interview (Route 2)£300 an hour

    A 1.5 to 2 hour live-coding and technical grilling session per final candidate.

All fees exclude VAT.

Tell us about the role

Frequently Asked Questions

Engineers who build products on top of models, covering retrieval, evaluations, agents and model API integration. We also recruit machine learning, LLM and AI research engineers who train, fine-tune and serve models.

Yes. We test data preparation, training objectives, optimisation, distributed training, full and parameter-efficient fine-tuning, evaluation, failure analysis and the trade-offs involved in adapting foundation models.

Our assessment can cover RAG, embeddings, reranking, model evaluation and MLOps, and for training roles PyTorch, TensorFlow, JAX, Hugging Face Transformers, supervised fine-tuning, PEFT, LoRA, QLoRA, RLHF, DPO and distillation.

Looking to hire?

Give us a few details about the role and your hiring plans. We'll assess your needs and get back to you with a practical next step.

Technologies in briefs we have recruited for

Listed for reference. We use these to scope the brief with you. A keyword on a CV is where screening starts, and the interview decides whether the candidate can do the work.

Building on models

  • LLM integration
  • RAG
  • Embeddings
  • Vector databases
  • Reranking
  • AI agents

Evaluation and production

  • Evaluations
  • MLflow
  • Weights & Biases
  • Model serving
  • Quantisation

Model training

  • PyTorch
  • TensorFlow
  • JAX
  • Hugging Face Transformers
  • scikit-learn
  • Pretraining
  • Supervised fine-tuning
  • PEFT
  • LoRA
  • QLoRA
  • RLHF
  • DPO
  • Distillation
  • CUDA

Soft skills and working style

  • Scientific curiosity
  • Intellectual honesty
  • Experimental discipline
  • Ethical judgement
  • Comfort with uncertainty

Teams usually bring us in for: A product team adding its first AI features. An AI product that needs retrieval and evaluation to hold up in production. A team developing or fine-tuning its own model.