My Journey

Before AI/ML, I explored multiple roles — graphic & marketing designer, web developer, clinical researcher, data analyst, engineer, and teacher. Each role shaped how I think today: I care about clean data, structured thinking, and systems that actually work in the real world.

Three years ago, I transitioned from web development into data science and AI. At first, it felt overwhelming — too many tools, too many opinions, too much noise.

What worked for me was simple: consistency over intensity.

I stopped trying to learn everything and focused on one thing at a time:

• one concept
• one implementation
• one project

That approach changed everything. Within months I started building real systems, and over time moved into production-grade AI/ML work and teaching others.

How I Work

I naturally think in systems, not just models.

• From clinical research, I learned rigor: results must be reproducible, not guessed
• From data analytics, I learned context: insights only matter if they solve real problems
• From engineering, I learned reliability: if it doesn't scale or monitor, it's incomplete
• From teaching, I learned clarity: if I can't explain it simply, I don't understand it well enough

This combination shapes everything I build today.

What I Build

I focus on production-ready AI systems, not just experiments.

• RAG systems and agentic AI workflows
• ML pipelines with reproducibility (MLflow, DVC, versioning)
• Data engineering pipelines (ETL/ELT, validation, governance)
• LLM systems with cost optimization (semantic caching, performance tuning)
• Cloud deployments using Docker, Kubernetes, Azure, Databricks

I care about one thing: Can this system survive in production and be trusted?

Impact

Philosophy

What I'm Looking For

I enjoy working on:

• Production AI systems
• MLOps & scalable ML pipelines
• RAG & agent-based architectures
• Data engineering at scale
• Real-world applied AI problems

Let's Connect