Skip to content

Kalpesh Khairnar

Frontend Engineer

I build React and TypeScript frontends for products that have to hold up in production: role-based access across eight user types, real-time data over WebSockets, and LLM features that do something useful rather than something impressive.

Open to new opportunitiesAhmedabad, India

kalpesh@dev · zsh

About

A read-only look inside my environment. Pick a file.

about.md — ~/developer

# Kalpesh Khairnar
 
> Frontend Engineer · Ahmedabad, India
> 3 years 2 months in the industry
 
I'm Kalpesh, a frontend engineer focused on building modern web
applications and developer tools. I work primarily with React,
Next.js, TypeScript and Node.js, building products that stay
scalable and intuitive as they grow.
 
Most of my work sits where the interface is the easy part:
role-based access, real-time data, and the failure states around
both. I design for the edges before the happy path, keep
architecture config-driven rather than clever, and treat
performance as a correctness problem.
 
Away from the keyboard: sport and training most days.
Open to new opportunities40 repos177 contributions

Experience

Roles in reverse chronological order, with what actually changed in each.

Sep 2023 → Present

currentFull-time

Software Development Engineer 1 · Solvative

Ahmedabad, Gujarat

  • Architected a config-driven React 19 and TypeScript frontend for an IoT dairy platform serving 8 user roles, cutting feature delivery time by 40% by removing cross-feature coupling.
  • Designed the end-to-end RBAC system for those 8 roles: a database-driven matrix of 17+ permissions enforced at the route, component and API interceptor layers, with no bypass path.
  • Built a production View As / impersonation flow on a dual-token JWT architecture, pairing a 30-minute short-lived impersonation token with the preserved real session.
  • Reduced the initial JS bundle by 42% through route-level lazy loading and Rollup chunk splitting.
  • Replaced ad-hoc fetch calls with a TanStack Query v5 caching strategy, removing 60% of redundant requests and taking perceived load from 1.4s to 320ms.
  • Shipped the WRE Portal on Next.js with SSR and SSG, improving survey completion and reducing respondent drop-off.
  • Built a Slack integration that routes production error alerts automatically instead of by hand.
  • React 19
  • TypeScript
  • Next.js
  • TanStack Query
  • Ant Design
  • MongoDB
  • Rollup
  • GitLab CI

Mar 2023 → Jun 2023

Internship

Frontend Developer Intern · Slideoo

Bengaluru, Karnataka

  • Built the frontend of the company's core application in Next.js and TypeScript, with responsive layouts and a reusable component set behind a consistent design system.
  • Integrated REST APIs alongside the backend team to power the product's data-driven features.
  • Translated UI/UX wireframes into pixel-accurate pages, working directly with designers to hold fidelity to the spec.
  • Next.js
  • TypeScript
  • React
  • REST APIs

Projects

A few things worth showing, with the problem each one was solving.

2 entries · sorted by featured

01

Real-Time Orderbook Viewer

Next.js2025

A live cryptocurrency orderbook that streams depth from three exchanges at once and lets you simulate an order against it before committing.

problem: Traders comparing venues had to keep three tabs open and eyeball the spread. This puts OKX, Bybit and Deribit in one view and estimates slippage for a hypothetical order.

  • Next.js
  • TypeScript
  • WebSocket API
  • Recharts
  • Tailwind CSS
  • book-forum

    Book Forum

    A cross-platform mobile app for community book discussion, with machine-learning recommendations layered over the forum data.

    React Native2023

    React Native · Node.js · Express · MongoDB

Skills

Grouped by what they are for. No percentages, because a self-assigned 92% in React tells you nothing you could verify.

36 technologies · 6 groups

Frontend

Where most of the work happens

  • TypeScript
  • React
  • Next.js
  • JavaScript (ES6+)
  • Redux
  • TanStack Query
  • HTML5
  • CSS3

UI systems

Design systems and styling

  • Tailwind CSS
  • Ant Design
  • Material UI
  • LESS
  • Responsive design

AI integration

Putting models behind a usable interface

  • OpenAI API
  • Gemini API
  • LangGraph
  • LLM integration
  • Prompt engineering

Backend and data

Enough to build the other half

  • Node.js
  • Express
  • REST APIs
  • WebSockets
  • MongoDB
  • MySQL
  • JWT auth

Tooling

Build, ship and debug

  • Git
  • GitLab CI
  • Webpack
  • Rollup
  • Babel
  • npm
  • Postman

Working style

How the work gets delivered

  • Agile / Scrum
  • Code review
  • RBAC design
  • Performance profiling

How I work

Technologies change every couple of years. This part does not.

01

Understand first

Most bad software is a correct solution to the wrong problem. Before writing anything I want to know who is affected, what they do today, and what breaks if this ships badly.

02

Design for the edges

The happy path is the easy 20%. I plan around the empty state, the slow network, the half-filled form and the record that already exists, because that is where users actually meet the product.

03

Build it plainly

Clear code that a teammate can change in six months beats clever code that only I can change today. I reach for abstraction after the third repetition, not before the first.

04

Ship, then measure

Shipping is the start of the feedback loop, not the end of the work. I instrument what matters, watch how it behaves under real load, and let the numbers decide what gets built next.

How compatible are we?

Let's see if we'd make a great team—or just create merge conflicts.😏

Get in touch

Hiring, contracting, or just comparing notes on something you are building. Either route below reaches me.

contact.sh

./contact.sh
Open to new opportunities

Prefer email? Write to kalpesh.er.dev@gmail.com.