What Tools Do
AI Engineers Use?
The core stack: Python, LangChain, vector databases like Pinecone, and cloud platforms.
But knowing which tools to learn first saves you months of wasted effort.
The AI Tool Landscape Is Overwhelming.
You Don't Know What to Prioritize.
New AI frameworks launch every week. LangChain, LlamaIndex, Haystack, CrewAI. You have no idea which ones employers actually care about.
You spent months learning a tool that became obsolete or that no one uses in production. Time wasted on the wrong stack.
Job postings list 15+ tools as requirements. You feel like you need to learn everything before you can even apply.
Learn the Tools Employers Actually Want
The World-Class AI Engineer Cohort
I've worked at GitHub and reviewed hundreds of AI engineering portfolios. Most tools in job postings are nice-to-haves. Master the core stack, and you're qualified for 80% of roles. Here's what actually matters.
Master the Core Stack
Python, LangChain, vector databases, basic cloud deployment
Build Production Projects
Use tools in real applications, not just tutorials
Learn on the Job
Specialized tools are learned once you're hired
Meet Your Mentor
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.
Real Results
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.
The AI Tool Ecosystem Moves Fast. Focus Beats Breadth.
Frequently Asked Questions
What are the essential tools for AI engineers in 2026?
The core stack: Python (non-negotiable), an orchestration framework like LangChain or LlamaIndex, a vector database (Pinecone, Weaviate, or Qdrant), API integration skills, and basic cloud deployment (AWS, GCP, or Azure). Master these and you're qualified for most AI engineering roles. Everything else is learned on the job.
Do I need to learn LangChain for AI engineering?
LangChain is the most requested framework in AI job postings, so yes, learn it. But understand the concepts behind it: chains, agents, memory, retrieval. Frameworks change, but the patterns remain. Once you know LangChain well, picking up alternatives like LlamaIndex takes days, not months.
Which vector database should I learn?
Start with Pinecone or Qdrant. They're popular in job postings and have good documentation. The specific database matters less than understanding how embeddings and similarity search work. Once you know one vector DB, switching to another is straightforward. Focus on building RAG systems that actually work.
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.
What cloud platforms do AI engineers need to know?
AWS is most common, followed by GCP and Azure. You don't need certification-level knowledge. Focus on: deploying containerized apps (ECS, Cloud Run), basic infrastructure (S3, API Gateway), and managed AI services (Bedrock, Vertex AI). Enough to deploy your projects, not enough to be a cloud architect.
How do I avoid tool overwhelm in AI engineering?
Focus on principles over specific tools. Learn one orchestration framework deeply, one vector DB, one cloud platform. Build projects that combine them. When job postings list tools you don't know, most are learnable in a week if you have solid fundamentals. Companies hire for problem-solving ability, not tool checkbox completion.
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.