IT Manager to AI Engineer
Return to Building.

More than you think. Project management translates to managing AI development lifecycles. Stakeholder communication helps you translate business requirements into technical specs. Vendor management experience applies to evaluating AI platforms and APIs. Systems thinking helps you architect AI solutions. Budget management means you understand cost-performance tradeoffs. You've likely also maintained some technical skills through architecture reviews, technical discussions, and staying current with your teams' work.

The core gaps are usually: 1) Modern Python development (async, type hints, modern tooling), 2) ML/AI fundamentals (transformers, embeddings, fine-tuning concepts), 3) LLM APIs and prompt engineering (OpenAI, Anthropic, local models), 4) Vector databases and RAG architectures, 5) AI deployment patterns (containerization, monitoring, evaluation). The good news: AI coding assistants like Claude and Cursor can dramatically accelerate your technical ramp-up if you know how to use them effectively.

AI PM is a legitimate path that leverages your management experience more directly. AI PMs bridge business and technical teams, define AI product strategy, and manage AI development without writing code daily. If you want to stay closer to leadership while working in AI, this might fit better. However, if you genuinely want to return to building things with your hands, AI engineering is more fulfilling despite the steeper technical ramp. Many ex-managers find the transition to IC work refreshing after years of meetings and politics.

Typically 4-8 months of focused effort. Your timeline depends on: how technical your management role was, how much coding you've maintained, your available study hours, and your target role level. With structured learning and 15-20 hours per week, most IT managers can become job-ready in 6 months. Using AI assistants to accelerate coding practice can compress this further. The key is consistent daily practice over marathon weekend sessions.

No. Companies increasingly value AI engineers who can communicate with executives, manage projects, and understand business context. These skills are rare in junior engineers. Target roles at mid-size companies and enterprises where your maturity is valued over raw coding speed. Avoid early-stage startups optimizing for cheap, fast coders. Position yourself for senior or staff-level roles where technical depth combines with strategic thinking. Your age becomes an asset when you stop competing on the same criteria as new grads.

Possibly initially, but not necessarily long-term. Senior AI engineers often earn $180K-$250K+ in 2026, which matches or exceeds many IT manager salaries. Your first AI role might pay 10-20% less than your management peak, but growth potential is higher. The AI engineering market rewards results over tenure. Many career transitioners reach or exceed their previous compensation within 18-24 months. Consider the opportunity cost of staying in management while AI reshapes the industry.

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.