Hasnat Khan
Islamabad, Pakistan
Machine learning / MLOps / AI automation
Models don't ship themselves.
So I build the pipeline that does.
I train the model, wrap it in a pipeline that retrains and redeploys it, and automate everything either side of that.
I'm an AI/ML engineer working across the whole lifecycle: data collection, training, and the MLOps around it — containerised services, scheduled retraining, monitored endpoints. I learned it from underneath, writing classifiers in raw NumPy and file systems in C before trusting a framework, which is why I can tell a bad gradient from a bad deploy. Most of what I build now is automation: the scraper that feeds the model, the job that retrains it, the API that serves it.
Full-stack
data → model → deploy
Automated
retraining pipelines
4
ML models from scratch
Docker
+ FastAPI + React
How the work runs
data → model → deploy → back again
- 01Ingest
Scrape and clean the source nobody has a tidy CSV for
BeautifulSoup · Pandas
- 02Train
Fit it, and know the maths well enough to debug it
PyTorch · scikit-learn · NumPy
- 03Evaluate
Hold-out metrics, and the honest ones, not the flattering ones
Metrics · Validation
- 04Serve
Behind an API or a GUI a non-technical user can actually operate
FastAPI · Docker · React
- 05Monitor
Watch it drift, then trigger the retrain — automatically
Logging · Scheduled jobs
Drift detected → back to Train, automatically
Two ways in
20 projects either way
The interesting way
Drive the city
Every project is a building. Take the car out, find one you like, and pull up outside to read the file.
WebGL · desktop or touch
The straightforward way
Read the site
The same 20 projects, written out — work, the path that got me here, and how to reach me.
Fast · works everywhere
Leave a note
hiring, a question, or a suggestion