- I've made a 7B model run on a laptop GPU that had no business running one.SNKT
- I've rebuilt RAG from open-source parts — embeddings, chunking, rerankers, quantization.FWUMP
- I've put guardrails on a medical AI so it never plays doctor.NOPE
- I've reconciled five marketplaces before breakfast.SYNC
- Zero data-loss incidents. Not once.KNOCK
ALRIGHT. LET'S DO THIS ONE LAST TIME.
KIRTAN
TANK
AI ENGINEER · BACKEND · SURAT, INDIA
I learned this from the bottom up — open-source models, on my own hardware.
Two years building AI that has to work on a Tuesday, not just in a demo.
YOU KNOW
THE REST
EDUCATION
B.E. Computer Science & Engineering
2020 – 2024
GUJARAT TECHNOLOGICAL UNIVERSITY
(RNGPIT)
Minor specialisation in Artificial Intelligence and Machine Learning. The degree got me in the room. Everything past this page is what I did once I was there.
EARLY AI WORK
Where I learned RAG the hard way — from the bottom up, on a laptop.
Make the AI read the documents. And answer from them.
Every tutorial used the OpenAI API, which had just stopped being free — so I built it out of open-source parts instead. Embeddings, chunking, rerankers. Benchmarked FAISS, Milvus and Chroma for latency and recall. Then the model I needed didn't fit in 12 GB, and quantization became the whole problem.
GPTQ · AWQ · QAT → GPTQ
IT RAN.
Quantized Zephyr-7B, on a 12 GB laptop GPU
THE STACK
GENERATIVE AI
RAG & TOOLING
FULL-STACK
DEVOPS
AGENTIC RAG
US real-estate platformHuman-in-the-loop agentic RAG over live property APIs and FAQ documents — and it knows when to stop and ask a human.
MEDICAL GUARDRAILS
Dermatology clinic groupHIPAA-compliant image analysis, built around what it must never do: give medical advice.
INVOICE INTAKE
Global industrial manufacturerAn LLM reads purchase invoices and files them straight into SharePoint and Excel. Nobody types a number.
RECONCILIATION
D2C brand · 5 marketplacesA Frappe back office pulling orders from five marketplaces — reconciled, then tracked all the way to revenue. Now: manufacturing.
WORKSHOP SAAS
Automotive service platformGST-compliant sequential invoicing, an edit-approval workflow and owner analytics. Mine from the first commit.
BLOCKCHAIN × AI
US fintech · code reviewCode review and polishing on a system where an immutable on-chain ledger held the audit trail — and AI agents triaged incoming transactions: auto-clear the small ones, park anything over threshold for human approval. Same shape as the agentic RAG above, with money on the line.
ALSO SHIPPED
Five more, in briefStaged IVF report summaries for a fertility clinic. A certification portal and LMS. A field-service platform that replaced paper. A multi-agent concierge. And an OCR pipeline that reads what people scribbled, then GPT-3.5 to clean it up.
NONE OF IT MATTERS IF THE BACKEND IS A HOUSE OF CARDS.
So I got good at the boring parts too — schemas, scheduled jobs, retries, RBAC, and the error handling that decides whether a bad API day becomes an incident.
Turns out the AI was never the hard part.
SIDE QUESTS
My other personal projects.
LEDGER
An agent harness over an MCP tool server — refunds need code authorisation and a human approval, and a red-team measured what prompt injection does with and without them.
GAIA AGENT
Multimodal agent for the GAIA benchmark — reasoning, web search, page visits and audio transcription.
EVENT PLANNER AI
A CodeAgent on Hugging Face smolagents that plans events through web search and tool automation — with tracing, because agents lie.
I'M GOING DEEPER INTO
AI ENGINEERING — ON A BACKEND
THAT DOESN'T FLINCH.
Two years in, the thing I'm best at is the seam between them.
THE LONG VERSION How I learned this with no API budget → Origin story · ~7 minEND OF ISSUE
AI & backend engineer at RedSoft Solutions, working from Surat, India. If you've got a system that needs to be smart and stay up, I'd like to hear about it.