SR. ENGINEER · TECH LEAD · BANGALORE, OPEN TO WORK

I build the systems that other people's products depend on.

Seven years of it. GenAI platforms at Wiffy, live video at 50K concurrent viewers at Classplus, and a company of my own before either.

YOUR PORTRAIT

7 years
building software
50K
concurrent viewers held
10+
engineers and QA led
25s → 5s
live latency, rebuilt
3
companies, one my own

SELECTED WORK

Each one led by the constraint, not the stack

01WIFFY · 2023—NOW

A brain for a system that couldn't stop

A legacy commerce platform carrying real revenue, and a mandate to make it understand plain English. Nobody was willing to pause the business to get it.

MY ROLE — TECH LEAD, HANDS ON

TEAM OF 6

10 MONTHS

THE SITUATION

Leadership wanted GenAI capability inside a platform people used every day to run their business. The workflows were load-bearing. Turning it off was never on the table.

THE CONSTRAINTS

No downtime, no rewrite, and a team that had never built event-driven systems. Free-form user input had to trigger real business actions — so a wrong answer was not a bad demo, it was a wrong order.

OPTIONS I REJECTED, AND WHY

One large prompt with tools attached

Worked in a demo, collapsed under real inputs. No way to isolate which step failed.

Rewrite the monolith around the agent

Correct on a whiteboard. Would have taken the business offline for a quarter.

Synchronous calls between services

Any slow model call became a user-facing timeout across the whole flow.

WHAT I CHOSE

Specialised agents for reasoning, retrieval and action, sitting behind the existing system as microservices. Kafka and RabbitMQ for pub/sub so nothing blocked. The legacy platform never learned the agents existed.

THE TRADEOFF I ACCEPTED

Debugging got harder. A synchronous system fails in one place; this one fails across a timeline. I paid for that up front with tracing and a replayable event log — about three weeks nobody had budgeted.

WHAT WENT WRONG

The first version let agents retry freely. A malformed input produced a retry storm that duplicated downstream actions overnight. Idempotency keys and a circuit breaker went in the following week, and that incident is why every integration I have built since starts with the failure path.

WHAT I'D DO DIFFERENTLY

Ship the observability before the second agent, not after the fourth. I could see that the system worked long before I could see why.

zero
downtime during rollout
manual steps
removed from the daily flow
6
engineers onboarded to event-driven
02CLASSPLUS · 2021—2023

Twenty seconds of dead air

Constraint: fifty thousand people watching live, and a latency budget the existing pipeline could not meet. Rebuilt on WebRTC and HLS until the gap closed to five seconds.

03WIFFY · 2024

The migration nobody wanted

Constraint: keep shipping features while replacing the foundation underneath them. React 16 to 19, Node 16 to 24, JavaScript to TypeScript, with the lights on the whole time.

PERSONAL PROJECTS — YOURS TO LIST

Things I built because I wanted them to exist.

These are the ones with public code — different proof from the employer work.

  • Project one

    2025

    What it does, in one sentence, and the reason you built it rather than using something existing.

    next.js · fastapi · postgres

  • Project two

    2025

    One sentence. Say what was hard about it — that is the part worth reading.

    python · langchain · chroma

  • Project three

    2024

    One sentence. If it has users or stars, say so here.

    react native · expo · supabase

  • Project four

    2024

    One sentence.

    go · redis · docker

  • Project five

    2023

    One sentence.

    node · websockets · aws

  • This portfolio

    2026

    Live RAG agent, voice-to-voice, and a 3D system explorer. The site is the code sample.

    next.js · three.js · vercel

ASK ME ANYTHING

VOICE + TEXT · LIVE

Talk to it. It only knows what I have actually done.

Grounded in the case studies above and nothing else. Ask about a tradeoff, an incident, or something I got wrong — it will tell you when it does not know.

  • What did you get wrong at Wiffy?
  • How did you cut latency to 5s?
  • Have you led a team?
  • What would you do differently?
  • retrieved 4 passages
  • first token 142ms
  • grounded — no invention
  • session 2 of 5

SYSTEMS

Here is a system I built. Click anything to see why I chose it.

EDGE
nginxrate limiting
api gatewayauth + quotas
AGENTS
routerintent
retrieverRAG
plannertool choice
executoractions
TRANSPORT
kafkaorder.events
rabbitmqretries + DLQ
STATE
postgresledger
chromavectors
redisidempotency
  • 12 services
  • 4 event streams
  • every box has a tradeoff behind it
  • 3D loads on click, never on page load

HOW I WORK — PLACEHOLDER, YOUR WORDS NEEDED

01

Constraints first.

The stack is the last decision I make, not the first. Tell me what cannot change and the architecture mostly writes itself.

02

Boring where it counts.

Novel only where it pays for itself. Every clever choice is a bill someone pays at 3am.

03

Measured, or it isn't done.

If I cannot show you the number before and after, I did not finish the work.

04

Migrate before it hurts.

The upgrade you keep postponing is the one quietly costing the most.

ABOUT — PLACEHOLDER, INTAKE §7

I started by building shops for people who could not afford agencies.

CrossX was mine — a bakery, a couple of small firms, whatever came in. I learned more about shipping from clients who noticed the day a page got slower than from any system diagram. That habit never left. I still measure the thing before I claim it, and I still think the interesting part of engineering is what you decide not to build.

CURRENTLY LEARNING
Your answer — intake §7
AWARDS
Hard-Hitter · Mr Consistent · Super Striker — the stories behind these, §8
HACKATHON
1st place, AI hackathon — the winning project shipped to production
OUTSIDE WORK
Something true that isn't code. This is the line people remember.

A CANDID SHOT — NOT A SECOND HEADSHOT

WHAT OTHERS SAY — YOU HAVE NONE YET. BIGGEST GAP ON THE SITE.

Two sentences from your Wiffy manager about how you led the GenAI platform work.
Engineering Manager, Wiffy
Two sentences from your Classplus lead about the streaming rebuild.
Tech Lead, Classplus
Two sentences from a CrossX client about what shipping with you was like.
Founder, CrossX client

TIMELINE

Senior Full Stack Developer

Wiffy — Tech Lead for Ecommerce, SaaS and GenAI verticals

Jun 2023 — Present

Full Stack Developer, Multimedia

Classplus — Tech Lead for Video Streaming and Analytics

Jan 2021 — Jun 2023

Founder & Lead Developer

CrossX — ecommerce builds for Infidata, AKA Technologies, Lake of Cakes

Jan 2019 — Jan 2021

B.E. Information Science & Engineering

Sai Vidya Institute of Technology, Bangalore · GPA 7.8

2017 — 2021

THE ASK — PLACEHOLDER, INTAKE §2

Looking for a senior or lead role where AI is the product, not a feature.

Remote or Bangalore. Sixty-day notice. Happy to talk to anyone building something where the hard part is real.