Founding Frontend Engineer at Rocket

I build frontend systems for products that need to move fast without becoming fragile.

Senior frontend engineer with 5+ years of experience across React, Next.js, and TypeScript. I work from the first user interaction to the architecture, tooling, measurement, and runtime systems behind it.

Explore my work Email me

The frontend is not only the layer users see.

It is where product decisions, system constraints, performance, growth, and reliability meet. I work across that boundary, turning ambiguous ideas into clear interfaces, scalable architecture, and systems that teams can evolve without losing speed.

Where I have worked

Founding Frontend Engineer

Rocket · Present

I am one of the founding frontend engineers behind Rocket, an AI product-building platform that helps people turn ideas into production-ready applications.

I know the frontend and its surrounding systems end to end, from the first screen a user sees to how the product is generated, measured, delivered, and kept reliable under real traffic.

My work spans frontend architecture, product experiences, component systems, developer tooling, performance, technical SEO, analytics, observability, and production stability.

I work directly with the CTO and Office of the CTO on technical and product decisions, while partnering with design, product, growth, marketing, backend, and DevOps teams.

Frontend Engineer

DhiWise

Before Rocket, I worked on developer-focused products at DhiWise.

That work gave me early experience with code generation, developer experience, complex interface workflows, and the systems required to turn product intent into usable code.

It also shaped how I think about tools built for other engineers: the interface should reduce complexity, not expose more of it.

What I work across

01
Frontend and UI architecture
React and Next.js applications, TypeScript systems, Nx monorepos, component libraries, design systems, UI governance, and experience using abstract syntax trees for code transformation.
I care about clear boundaries, durable component APIs, and architecture that helps teams ship consistently as the product grows.
02
Performance and runtime reliability
Core Web Vitals, browser and runtime profiling, rendering and caching decisions, production debugging, error diagnosis, observability, and stable user journeys.
Performance is not a final optimization pass. It is part of product quality and should be designed into the system.
03
Product intelligence and experimentation
Technical SEO, structured data, indexing strategy, event design, funnels, behavioral analytics, feature rollouts, and experimentation.
I treat measurement as part of product design, not something added after a feature launches. The important user actions, their place in the journey, and the questions they should help answer are defined early and aligned with the relevant product, growth, and marketing stakeholders.
This keeps tracking intentional and makes the resulting data useful for understanding adoption, friction, and drop-off.
I have worked with Mixpanel, Segment, PostHog, Google Analytics, Google Search Console, Statsig, and Flagsmith to connect product changes with user behavior and support evidence-based rollout decisions.
04
Developer tooling and delivery
Developer workflows, internal tooling, frontend delivery, CDN behavior, and production debugging.
My infrastructure experience has developed through close collaboration with DevOps on frontend delivery and production issues. I have contributed to decisions around Rocket’s self-hosted, multi-region setup and worked with the team to investigate hosting, routing, caching, and runtime problems.
This has given me practical experience with Cloudflare, CloudFront, AWS Application Load Balancers, Nginx, PM2, Prometheus, Grafana, and Sentry, and a clearer understanding of how frontend decisions behave in production.

Core stack

TypeScript · React · Next.js · JavaScript · Zod

I also have backend experience with Node.js, Express, and MongoDB, and I have recently added Python to my toolkit. This knowledge helps me understand systems beyond the browser, collaborate effectively with backend teams, and make better frontend architecture decisions.

I am currently learning Go and exploring broader system architecture in greater depth.

How I work

I like to understand the system before changing it.

I begin by clarifying the actual problem, the people affected by it, and the constraints surrounding it. I question assumptions, compare trade-offs, and consider what today’s decision could make easier—or harder—as the product grows.

I prefer solutions that address the underlying problem, remain understandable to the team, and improve the system beyond the immediate task.

My best work usually happens when the problem is still ambiguous and engineering, product, design, and business considerations need to be brought together.

AI-native, engineering-led

AI is part of my daily engineering system, not a substitute for it.

I use models and agents to accelerate research, exploration, implementation, review, debugging, and documentation. I still own the problem framing, architecture, trade-offs, verification, and the final decision to ship.

AI increases my throughput. Judgment sets the direction and the quality bar.

Beyond the interface

I follow the systems that shape technology and products: AI models and inference, software architecture, developer tools, startups, product strategy, Indian business, markets, economics, and geopolitics.

I prefer explanations that go beyond what happened and examine why it happened: how a technical system works, why a company makes a particular decision, what incentives shape a market, and what second-order effects might follow.

That breadth strengthens my product judgment. It helps me connect engineering choices with user behavior, operating constraints, and business outcomes.

Have a difficult product problem?

Let’s build something that can move fast and hold up under pressure.

I am most useful in high-ownership teams where frontend engineering is treated as a core product system, not a finishing layer.

If that sounds like the kind of team you are building, I would like to hear from you.