Skip to content

Work experience / 01

Software I’ve built in production

I’m a software engineer working across full-stack systems, real-time infrastructure and AI-powered products — mostly backend architecture, media pipelines and the tool harnesses that let a model do useful work without being trusted with the database.

Roles
2
Since

Hyperion Future Tech Ventures Pvt. Ltd. (Gudz)

Software Engineer InternGurugram, India to Present

Software engineering on production AI-powered product systems: an agentic storefront builder on top of a live ERP, and the real-time media and inference services behind a warehouse monitoring platform. Most of my time goes to backend architecture, the AI tool harness and the reliability work that keeps both honest.

Core stack

  • TypeScript
  • Next.js
  • Node.js
  • Vercel AI SDK
  • Puck
  • PostgreSQL
  • Socket.IO
  • WebRTC
  • FastAPI
  • MCP

Featured

An AI-assisted no-code ecommerce storefront builder. Merchants describe what they want in plain language and the system creates and edits multi-tenant storefronts on top of the catalogue, inventory and orders already held in the ERP — built with Next.js, TypeScript, the Vercel AI SDK and the Puck visual page editor.

The engineering idea is that the model never touches merchant data. It reads, and it writes proposals. Every change moves through proposal, validation, merchant approval and verification before anything is applied, with optimistic locking and stale-read protection so a proposal built against an older version of a shop is refused rather than silently overwriting a newer edit.

Worked on this as part of a team. My contribution is the architecture and the constraints it enforces, the technical decisions and implementation direction, and the debugging, browser acceptance testing and review that closed them out.

Engineering focus

  • AI systems architecture
  • Typed tool calling
  • Proposal / apply safety model
  • Multi-tenant systems
  • Backend & API engineering
  • Reliability & validation

Technologies

  • Next.js
  • React
  • TypeScript
  • Node.js
  • Hono
  • tRPC
  • PostgreSQL
  • Drizzle
  • Puck
  • Vercel AI SDK
  • Zod
  • Tailwind

Architecture

AI tools
25
Read-only
11
Proposal-generating
14
Direct write tools
0

The zero is the design rather than an omission — the write path is unreachable from the model, so the guarantee is a property of the tool surface and not of a prompt.

Proof

Passing tests
1,628
Dark-mode verification checks
45
Contrast tests
22
Benchmark scenarios
30

Engineering figures, not business ones. Two bugs that every automated check passed were found by testing in the browser — a CSS specificity failure that left the theme attribute inert, and a hydration mismatch caused by correcting the theme before React hydrated. Both fixes were verified by removing them again and confirming the original failure returned.

Inside the build

Selected engineering work

  1. AI harness

    Typed tool definitions over the Vercel AI SDK with per-turn step budgets, a staleness guard that refuses proposals built from an outdated read, and a durable proposal lifecycle kept out of the model's context. Fixed two accuracy failures: the model answering questions instead of acting, and claiming work it had not done.

  2. Theme architecture

    First-class light, dark and system theming delivered additively, driven by one attribute on the storefront root and resolved entirely through CSS custom properties — no per-component branching, and existing shops render unchanged. The system preference is handled in CSS rather than JavaScript so it stays valid under server rendering.

  3. SEO & structured data

    Sitemap coverage, canonical handling for paginated and sorted views, and Organization, WebSite, BreadcrumbList and ItemList JSON-LD emitted only from stored values. A content-quality gate rejects keyword stuffing, unverifiable claims and thin copy, so the generator cannot invent product facts to fill a field.

  4. Validation & regression testing

    Schema validation that rejects unknown keys on write while staying lenient on read, plus a colour-contrast check that blocks unreadable palettes without punishing shops for problems they already had. Verification scripts fail loudly on missing fixtures rather than exiting green with nothing executed.

Also

Real-time warehouse monitoring

A real-time monitoring platform where mobile video is streamed to backend services and consumed three ways at once: object detection, vision-language analysis of on-screen text and unfamiliar objects, and live 3D reconstruction of the space being walked.

I moved the media layer off a peer-to-peer mesh onto an SFU over WHIP and WHEP, so the phone uploads one copy regardless of how many viewers are watching, and rewrote reconstruction from a batch job into a streaming one.

Time to first geometry

6.6s → 0.3s

Streaming inference in place of whole-clip reconstruction, with async workers keeping network I/O off the inference path.

  • Batch to streaming reconstruction — frame-by-frame inference with incremental fusion, validated as identical to the batch path before it replaced it.
  • Bounded work queues with backpressure, so capture that outruns inference degrades predictably instead of collapsing throughput.
  • Point-cloud results streamed to the browser as deltas while the walk is still happening, rather than after it finishes.
  • Multi-viewer media architecture — publish once, fan out server-side, no per-viewer encode on the device.
  • A three.js point-cloud viewer with camera trajectory, playback and fly-through navigation.

Stack

  • WebRTC
  • WHIP / WHEP
  • MediaMTX
  • Socket.IO
  • Node.js
  • Python
  • FastAPI
  • YOLO
  • VLM
  • Three.js
  • GPU inference
  • RunPod

FoundersCart

Software Engineer InternNew Delhi, India to

Production CRM integrations, communication tooling and scheduling systems — owning backend APIs and frontend integration end to end across four shipped surfaces.

Core stack

  • Node.js
  • Express
  • React
  • GraphQL
  • WebRTC
  • Chrome Extensions
  • Google Calendar API
  • Google Meet API
  • Zoom API

Shipped

What I built

  1. IVR Solution

    Architected and built a WebRTC softphone integrated with the monday.com CRM: click-to-call, in-call management, automated call logging written back to the board, and real-time contact synchronisation. Lifted lead generation 15%.

  2. Chrome extension

    Designed, developed and published the IVR Solutions WebRTC softphone to the Chrome Web Store — browser-based dialing, call management and automatic call logging that works across CRM platforms without a native integration on each one. Drove a 20% uplift in qualified leads.

  3. SensiBot

    A real-time multilingual messaging platform with automated translation between participants, persistent conversation logging, and integration into monday.com workflows so a conversation lands beside the record it belongs to.

  4. Meeting scheduler

    Timezone-aware availability with Google Calendar, Google Meet and Zoom integration — the correct slot in the participant's own zone, and a conferencing link provisioned on whichever platform the invite asks for.

Outcomes

Increase in lead generation
15%
Uplift in qualified leads
20%

Looking for someone to build this kind of thing?

Open to internships, full-time roles and collaborations. I usually reply within a day.