AI Research Engineer Jobs:
Where Papers Become Products

Research Engineers bridge the gap between cutting-edge research and production systems.
Salaries range from $150K-$350K+ at AI labs and Big Tech research teams.

You Want to Do Research That Ships.
But the Path Is Unclear.

Job postings blur the line between Research Scientist and Research Engineer. You're not sure which one fits your skills and goals.

You don't want to spend years publishing papers that never see production. But you also don't want to lose touch with cutting-edge research.

Many roles list 'PhD preferred' or require publications. You're not sure if your engineering background is enough to compete.

Turn Engineering Skills Into Research Impact.

The World-Class AI Engineer Cohort

Research Engineers are the rare breed who can read papers AND ship code. You translate experimental prototypes into scalable systems. You collaborate with researchers while maintaining production standards. The role requires both depth in ML fundamentals and the engineering discipline to make research reproducible and deployable.

1

Clarify Your Path

Research Engineer vs Research Scientist: know the difference

2

Build Research-Grade Projects

Reimplement papers, contribute to open-source ML frameworks

3

Position as the Bridge

Demonstrate you can ship research, not just read it

Meet Your Mentor

Zen van Riel

My aim has been the same for years: become a world-class AI engineer. Every career move I've made has been measured against that.

I started as a software tester on a $500/month internship in the Netherlands. Taught myself to code, learned to ship real systems, and worked my way to Senior Engineer at GitHub.

Then I left GitHub. I joined an AI research lab as Member of Technical Staff, where I currently build products for secure AI monitoring.

The cohort draws directly from my real experience so you can make progress fast.

I run this special cohort with only a few people because hands-on work with me is what it takes to bring you to become a world-class AI engineer.

Career progression from Intern to Senior Engineer

Real Results

Vittor

Vittor

AI Engineer

Built and deployed his portfolio piece, then landed the AI role

"The coaching played a huge part in my success. I focused on AI fundamentals, the certification path, and soft skills like professional writing. Having access to expert guidance gave me confidence during interviews and helped me feel I was on the right path.

I built my own platform (simple but functional) and deployed it on AWS. I used it in my portfolio and showcased it during interviews. The way complex topics were explained, especially the restaurant analogy for AI systems, really stuck with me. Focusing on doing the basics well was absolutely essential."

What You Will Get

8 Weekly Tuesday Sessions

3 hours each for 24 live hours total.

Project Scoping at Kickoff

We set the scope of what you'll ship and the milestones to get there before the live sessions start.

Code Reviews

Reviews of your code from Zen during the cohort.

Lifetime Demo Access

Every architecture demo is recorded and yours to keep.

Demo Day

You present what you built and get feedback from Zen, with a recording you can use in your portfolio.

12 Months Community Access

Included with the cohort.

AI Labs Are Scaling Fast. Research Engineers Are in Short Supply.

8
Weeks
6
Seats per Cohort
24
Live Hours with Zen

Frequently Asked Questions

What's the difference between Research Engineer and Research Scientist?

Research Scientists focus on novel research, publishing papers, and advancing the field. Research Engineers focus on making research work at scale. You'll implement papers, optimize training pipelines, build infrastructure for experiments, and ensure research code can be reproduced and deployed. Research Scientists often have PhDs and focus on publications. Research Engineers typically have strong engineering backgrounds and focus on making research practical. Many Research Engineers eventually transition to Research Scientist roles after building deep domain expertise.

Do I need a PhD for AI Research Engineer roles?

It depends on the company. At academic-style AI labs (DeepMind, OpenAI research teams, FAIR), PhD preference is common but not universal. At Big Tech research teams (Google Brain, Apple ML Research, Amazon Science), strong engineering skills with demonstrated ML expertise can substitute. At applied AI companies, practical experience often matters more than credentials. The key differentiator: can you read, understand, and implement research papers? If you can show that through open-source contributions or paper reimplementations, you can compete without a PhD.

What do AI Research Engineers earn in 2026?

AI Research Engineer salaries reflect the specialized skillset required. Entry-level roles at well-funded startups or Big Tech start at $130K-$160K. Mid-level (3-5 years) ranges from $160K-$220K. Senior Research Engineers at AI labs (OpenAI, Anthropic, DeepMind) or Big Tech research divisions earn $220K-$350K+ total compensation including equity. Elite AI labs competing for top talent sometimes exceed $400K. The premium comes from the rare combination of research intuition and engineering discipline these roles require.

Which companies hire AI Research Engineers?

The market breaks into tiers: (1) Frontier AI labs - OpenAI, Anthropic, DeepMind, xAI, Mistral - where you work on cutting-edge models, (2) Big Tech research divisions - Google DeepMind, Meta FAIR, Microsoft Research, Apple ML Research, Amazon Science, (3) AI-native companies - Hugging Face, Cohere, Stability AI, Scale AI, (4) Applied research teams at tech companies building specialized AI products. Each tier has different cultures: AI labs emphasize publications and breakthrough research, Big Tech balances research with product impact, AI-native companies focus on open-source and developer tools.

How much time will this take?

You'll spend 3 hours every Tuesday in the live session and roughly 3 hours of async work in between, for 8 weeks. The Tuesday session time is fixed.

I've signed up for cohorts before and dropped out. How is this different?

It probably isn't, and you should hold the money. Most cohort dropouts are people who couldn't articulate what they were shipping when they signed up. That's why the consult exists, and why I turn down most applications. If we get on the call and you can't tell me what you'll have shipped at the end of week 8, I'll point you to the AI Native Engineer community until you can.

I'm not pivoting careers. I want to build a product. Does this still work?

Yes, the cohort works for people shipping their first serious AI system whether the goal is to land a senior role or to launch a product. The shipped system serves both equally well.

Do I need prior AI experience?

You need to be able to code in Python or TypeScript. Complete beginners can follow the classroom they get access to before the cohort sessions to come in well-prepared.

What does it cost?

It's a four-figure investment that we discuss during the 30-minute consult, alongside whether the cohort is the right fit for your project.

Can I do this while working full-time?

Yes, most attendees do. The live session is one Tuesday a week and the async work fits around your existing schedule, as long as you can carve out roughly 6 hours a week.

I accept those who have the highest chance of success.

In the 30-minute call we discuss your goals and whether you are ready for the program.