Why I'm Leaving My Comfort Zone: From Engineering Leadership to AI-First Engineering

I've spent my career architecting distributed systems — designing fault-tolerant pipelines, making trade-offs between consistency and availability, and owning systems end-to-end from design through production.

Data pipelines. Streaming infrastructure. Backend at scale. I've built systems processing terabytes of data, architected platforms handling millions of requests.

I'm good at what I do.

So why am I starting over as a complete beginner in AI/ML?

What Happened

Two things made this impossible to ignore.

First, my company started hiring AI/ML engineers.

Suddenly, there were these people in meetings talking about RAG, agentic systems, and MCP, etc., and I'd nod along.

I had no idea what they were actually building.

All my experience, and I couldn't contribute to the most important projects at my company.

That hurt.

Second, I started using Claude Code.

Game changer. POCs that took me days? Done in hours. New features? 2-3x faster. Going from 0 to 1 on projects became almost effortless.

But here's the problem.

I didn't understand how it worked.

I was using AI. I wasn't building it. Couldn't explain it. Couldn't tell if solutions were actually good or just looked convincing.

Someone asked me: "How does Claude Code actually work?"

No answer.

That's when it hit me.

Why This Matters to Me

I've always believed understanding fundamentals lets you solve complex problems.

When I learned distributed systems - really learned them, not just used Kafka but understood partitioning, replication, consensus - that's when I stopped using tools and started building systems.

That's when I became valuable.

I need to do the same with AI.

Not just use it. Understand it. Build it.

What Scares Me

Transitioning from expert to beginner after leading distributed systems teams.
I'm back to asking foundational questions.

I should've started this in 2024. Every month I waited, AI moved faster.
But waiting for the "perfect time" would mean never starting.

Here I am.

What Pulls Me Forward

Two things make this worth the fear:

I want to be part of the conversation. Not the person nodding along while AI/ML engineers talk. I want to understand what they're building.

I want to build AI systems myself. Not just use Claude Code. Build things like it. Understand models, architectures, trade-offs.

I want to become an AI-first engineer.

Why Now and Not Later

Because I can't afford to fall further behind.

AI is accelerating too fast. Every day I wait, the gap widens.

I already feel late. Another year won't make this easier.

So I'm starting today.

The Plan

I'm learning AI/ML fundamentals from the ground up.

No shortcuts. No just-use-the-framework-without-understanding approach.

I want to understand:

• How models like Claude actually work
• How to build AI systems from scratch
• How to architect production AI solutions

Timeline? Don't have one. Just committed to the journey.

Goal? However long it takes - I want to:

• Lead or contribute to AI projects
• Understand how these models actually work
• Become a true AI-first engineer

What's Next

I'm documenting this journey here. Not polished tutorials. Real learning in public.

Wins. Struggles. Confusion. Breakthroughs.

Week 1 starts now.

I'm nervous. I'm excited. I'm deep into my career and starting over.

Let's see where this goes.

---

If you're also making a career transition into AI/ML, I'd love to hear about it in the comments.

Comments

[Raju C]

Thanks @nyrok . I will check it out