AI researcher, applied AI engineer or AI product engineer

When to hire an AI researcher

An AI researcher earns their keep on open questions. Your product needs a capability that nobody has demonstrated at your constraints, and someone has to establish whether it is reachable at all. That work has no delivery date, and paying for it means accepting months with nothing shippable at the end.

The signal that identifies a strong one is first authorship at a venue with a hard review process. Author order carries meaning in machine learning: the first author did the work. Publication count rewards a large lab where everyone appears on everything, and citation count rewards seniority, since citations take two to four years to accumulate. A doctoral student finishing this year has published their best work too recently to be cited for it, so ranking candidates on citations sorts the people you can hire below the people you cannot.

The cost of this search is access rather than identification. The people you want are employed, contacted constantly, and reachable during a window of a few months at the end of a doctorate. Our full method is in how to find and hire AI researchers.

When to hire an applied AI engineer

An applied AI engineer takes a method that already works in a paper or a notebook and makes it survive contact with your traffic. Serving, latency, quantisation, retrieval, evaluation, the retraining loop, and above all the judgement about which failure modes matter and which are noise. Hire one when the science is settled and the engineering risk sits in your data and your bill.

The strongest signal here is a career move that has already happened. Someone who published research and then joined an industry lab or a product team carries model intuition from the first half of their career and production constraints from the second, and an organisation with a demanding interview process reached that conclusion about them at its own expense. Researchers declare that move publicly, with a start date, because their scholarly profile exists to establish authorship.

The cost of this search is identification. One job title covers people who fine-tune a model on a laptop and people who run inference for millions of daily requests, so keyword search returns noise. You filter on what their recent work is about. Full method in how to hire an applied AI engineer.

When to hire an AI product engineer

An AI product engineer builds everything around the model. Orchestration and tool use, evaluation harnesses, guardrails, cost control, and the interface. A system that is wrong five percent of the time is either unusable or excellent depending on what the product does when it is wrong, and designing that behaviour is this person's job.

They publish little, so the literature will not find them. Their record sits in repositories: code other people depend on, release histories, issues opened by strangers, tests where the hard parts are. Reading that record well takes a different search entirely, covered in how to find and hire AI engineers.

This is the profile teams skip. They hire two researchers, no product engineer, and then wonder why nothing reaches customers. It is also the profile most often paid a tier below the others because the title sounds junior next to Research Scientist.

How to decide which one you need

One question settles it. What is uncertain about your problem?

• Uncertain whether it is possible. You need a researcher, and you should budget for a period with no shippable output.
• Certain it is possible, uncertain it will hold in production. You need an applied AI engineer. The method exists and your risk is data, latency and cost.
• Certain it will hold, uncertain anyone will use it. You need a product engineer. The model works in a notebook and the question is whether the thing around it is any good.
• You cannot tell which of the three you are in. Run a two-week spike with a contractor before writing a job description. The answer changes what you hire, what you pay and how long the search takes.

What order to hire in

For a company adding AI to an existing product, the order that works is product engineer first, applied AI engineer second, researcher only if the roadmap runs into a wall that published work has not cleared. Plenty of companies never need the third hire.

For a company whose product is the model itself, the order inverts. The researcher comes first because there is nothing to build a product around yet, and the product engineer arrives at the point where the model becomes something a customer touches.

Picking wrong once is survivable. The expensive version is hiring the profile that matches your ambition rather than the one that matches your uncertainty, then spending a year discovering the difference.

Common questions

What is the difference between an AI researcher and an applied AI engineer?

An AI researcher establishes whether a capability is reachable, and is measured by published work that survived peer review. An applied AI engineer makes a known method hold on real data at production scale and cost, and is measured by a system that stays up. The two searches use different signals: first authorship at a top venue for the researcher, a documented move from research into industry for the applied engineer.

What is an AI product engineer?

An AI product engineer builds the software around a model without training it: orchestration, tool use, evaluation harnesses, cost control, and the interface and failure paths that make a probabilistic system usable. Most of the work in shipping an AI feature sits here rather than in modelling, and this is the role teams most often skip.

Do I need to hire an AI researcher?

Only if your product depends on a capability that does not exist yet at your constraints. If your problem can be solved by combining existing models with your own data, an applied AI engineer will ship it sooner and a researcher will run out of open problems within a few months and leave.

Which AI profile is hardest to hire?

Researchers are the hardest to reach: the strongest ones are employed, not looking, and approached by every lab. Applied AI engineers are the hardest to identify, because the job title covers people several capability tiers apart. Product engineers are the easiest to find and the most often underpaid.

Can one person do all three jobs?

At a junior level someone can cover parts of two. At a senior level the three reward different instincts: tolerance for open-ended failure, judgement about production risk, and taste for interface design. People who credibly span two of them exist and command a premium.

What job title should I put on the posting?

Whichever title the people you want already hold, which is usually not the one that describes the work. Someone doing applied AI work at a large company is often titled Software Engineer or Research Engineer. Write the posting around the problem and the constraints rather than the title, and search on evidence of the work instead of on the words in a headline.