AI Portfolio Presentation Interview:
Showcase Your Work Effectively

Select projects that: (1) Demonstrate AI-specific skills (RAG, LLM integration, embeddings), (2) Show end-to-end implementation, not just notebooks, (3) Have measurable outcomes or clear use cases, (4) You can explain deeply and confidently. Quality over quantity—2-3 strong projects beat 10 superficial ones. At least one should involve production concerns like deployment or error handling.

For each project (5-8 minutes): (1) Problem—what you were solving, (2) Approach—why you chose this architecture, (3) Technical decisions—key choices and trade-offs, (4) Challenges—what was hard and how you solved it, (5) Results—what you achieved or learned, (6) Reflections—what you'd do differently. Interviewers remember stories better than feature lists.

Match depth to audience. Start high-level, then offer to dive deeper. Say: 'I used a hybrid search approach—would you like me to explain why?' This shows you can adapt communication. Be ready for deep dives on: model selection rationale, architecture decisions, performance trade-offs, error handling approaches. If you can't explain a decision, reconsider including that project.

If you don't know: 'I haven't explored that approach, but here's how I'd investigate it.' If you made a mistake: 'In retrospect, I'd do X differently because Y.' If it's outside scope: 'That wasn't a focus for this project, but here's how I'd approach it.' Honesty and thoughtfulness matter more than having all answers. Never bluff—interviewers can tell.

Live demos are high-risk, high-reward. If you demo: (1) Have a backup recording in case of failures, (2) Test everything immediately before, (3) Keep it short—2-3 minutes max, (4) Have a script for what you'll show. Alternatively, use recorded demos or screenshots. A smooth recording beats a nervous live demo that breaks. Focus on explaining, not performing.

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.

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.

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.

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.

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.

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.