About

Hi, I'm Ansh Bharti

Ansh Bharti
Download Resume

I work mostly at the seam between automation and AI — building pipelines that pull messy real-world signals (search trends, marketplace listings, RSS feeds) and turn them into structured decisions or content a business can ship. Most of what I build runs on n8n orchestrating multiple Gemini calls, with as much engineering effort going into validation, deduplication, and bounded retries as into the AI calls themselves — I've been burned before by a third-party API silently handing back an empty field and corrupting a join, so I don't trust anything I haven't independently verified. I build solo, end to end: ingestion, the AI logic, the datastore, and — for anything that touches a public channel — a human approval gate before it publishes. I would rather label an estimate as an estimate than dress it up as a measurement.

I turn messy signals into decisions a business can act on.

01

Stack

What I reach for, and where — for the full picture, see how these show up in real projects.

Programming

TypeScript
JavaScript
C#
Python

AI / LLM Engineering

Google Gemini API
Prompt Engineering
LLM Pipelines
Structured Output Parsing
LangGraph
Agentic State Machines
Human-in-the-Loop Design

Automation

n8n
Make.com
Telegram Bot API
Webhooks

Web Development

Next.js
React
Tailwind CSS
Node.js
Lovable

Data & APIs

SerpAPI
Google Trends API
Google Ads API
Tavily API
RSS

Databases & Infra

Supabase
PostgreSQL
Browserless

Game Development

Unity
Universal Render Pipeline (URP)
Cinemachine
Unity Input System
AI Navigation (NavMesh)
ProBuilder
Shader Graph
See these applied in practice

02

Education

  1. 2022 - Present

    B.Tech in Computer Science & Engineering

    Sharda University, Greater Noida

    Currently pursuing. Most of the applied work — AI pipelines, automation, and API integration — happens outside coursework, in the projects on this site.

03

How I think about engineering

“If a system can fail silently, it eventually will — so I build the validator and the retry loop now, instead of debugging the silent corruption later.”
See it in the tradeoffs I made