Available · Just showcasing work
VaibhavMishra.
Frontend engineer · 5 years building products users actually enjoy using.
Currently exploring AI engineering — turning my curiosity into real systems.
01 — About
I make interfaces that feel right.
I've spent five years writing frontend code — the kind where one missed transition makes the whole thing feel cheap, and the right one makes a product unforgettable.
I obsess about the small details. The way a modal closes. The timing on a hover state. The empty state that should never have been empty. The accessibility no one asked for but everyone benefits from.
These days I'm extending that craft into AI — building backends, wiring vector databases, learning how the magic actually works under the hood.
0+
Years building frontends
0+
Components shipped to production
0
Cross-functional teams worked with
0
Big AI obsession (current)
02 — Skills
The stack I think in.
Move your cursor across the cards — each one tilts in 3D, because the fastest way to show I care about details is to build them.
React & TypeScript
Component architecture, hooks, custom state primitives, strict types. Five years of writing it and refactoring my own past mistakes.
- React 18 · Next.js · Vite
- Type-safe API contracts
- Custom hooks · Context patterns
CSS & Animation
Layouts that don't break. Motion that has reason. Designs that translate cleanly from Figma into code that holds up under real content.
- Tailwind · CSS Modules · Stylex
- Framer Motion · GSAP
- Responsive · Accessible · Dark mode
Node.js & APIs
Backend-for-frontend layers, REST and SSE consumption, auth flows, third-party integrations. The full surface between the UI and the database.
- Node · Express · FastAPI
- REST · SSE · WebSockets
- Auth · Caching · Rate limiting
AI Engineering
Newest chapter — last 6 months. Built RAG pipelines, ReAct agents, multi-agent orchestration, vector DB integrations from scratch.
- RAG · Vector search · Embeddings
- ReAct · Multi-agent pipelines
- Ollama · Groq · ChromaDB
03 — Featured Work
Six months of learning AI,
told as a timeline.
AI Studio
A full-stack AI playground I built to learn modern AI engineering — by building it from scratch instead of reading about it.
~12,000
Lines of code
39
Pytest tests
10
AI tools built
0
OpenAI dependencies
The journey →
Month 1
The dumb chatbot
Wired up a PDF uploader and a vector database. It worked. I didn't fully know why.
Month 2
Understanding embeddings
Built a 2D PCA visualization of the embedding space. Suddenly I could SEE what 'semantic similarity' meant.
Month 3
Beyond naive retrieval
Hand-rolled BM25 + Dense hybrid retrieval, HyDE, and Multi-Query with RRF. Wrote evaluation metrics to compare them.
Month 4
Going agentic
Implemented the ReAct pattern from scratch — Thought, Action, Observation loops. Hooked up DuckDuckGo, calculator, and document tools.
Month 5
Visual orchestration
Built a drag-and-drop workflow builder with React Flow. Implemented a DAG executor using Kahn's topological sort.
Month 6
Multi-agent pipelines
Chained specialized agents that pass context between themselves. Streaming tokens live per agent over SSE.
The point was never to build an AI product.
It was to stop treating AI as a black box.
04 — Interactive demo
A drag-and-drop editor.
Try it — it's live.
Before AI Studio, I spent two years building an enterprise email editor used by thousands of marketers — drag blocks, reorder rows, inline editing, autosave, undo/redo. This is a stripped-down version you can play with right here.
untitled.draft
Blocks
Click a block to add it. Drag the handle to reorder.
heading
text
button
3 blocks · auto-saved
in sync
05 — Principles
Things I obsess about
when nobody's watching.
Motion has meaning
Animation is feedback, not decoration. Every transition should answer 'where did this come from?' or 'what happens next?'
Empty states matter
The first thing a new user sees is the empty state. If it's blank, you've already lost them.
Accessibility isn't optional
Keyboard navigation, screen reader labels, focus rings, prefers-reduced-motion. All of it. Always.
Performance is UX
A janky 60fps button feels worse than a polished click. Profile before you ship. Then profile again.
Types are documentation
If a TypeScript signature needs a comment to explain it, the signature is wrong.
Mobile is the default
It's not 'responsive design'. It's 'designing for the device most of your users actually use.'
06 — Contact
Say hi.
Or just look around.
Not actively job-hunting, not pitching anything. Just building in public and happy to talk shop — frontend, AI, weird side projects, whatever.