Skip to content

Frontend & Mobile Engineer · Pune, India

Abhinav
Deshmukh

I build web and mobile products that feel fast, and I write down why every decision was made.

Open to senior frontend roles

01About

I care about the why behind the code.

Portrait of Abhinav Deshmukh
Pune, India

I'm a frontend engineer who got here by caring about the product first. Before I write a component I want to know who it's for, what it's replacing and what happens when it fails. The code tends to get simpler once those answers are clear.

Most of my week is spent inside a large, long-lived React codebase, with years of decisions made by people who've since moved on. I like that kind of work. Improving a system people depend on, without stopping it, teaches you more about trade-offs than any greenfield project.

Outside of that, I'm building Lekhit on my own, on my own time: a private money tracker for India that sorts your UPI history and splits expenses with friends. It's where I get to own every layer, from the design system to the database, and where I keep sharpening my product judgement.

02Experience

Shipping inside long-lived codebases.

Most of the interesting work is in systems people already depend on: making them faster, safer and easier to change without stopping them.
  1. Pune, India

    Software Engineer · Noovosoft Technologies

    Full-time

    Frontend engineering on a large, long-lived, multi-tenant B2B web application.

    • Lead frontend architecture improvements in a large React codebase, rolling them out in small, reversible phases alongside feature work.
    • Improve data-fetching and caching patterns to cut redundant network requests and keep views consistent.
    • Apply secure-frontend practices as a habit: input sanitisation, safe redirects, masking sensitive data and keeping dependencies patched.
    • Keep the toolchain current through major framework and build-tool upgrades, and keep production errors under control.
    • Drive the team's adoption of AI-assisted development with shared conventions, tooling and guardrails.
    • React
    • TypeScript
    • MobX
    • React Query
    • Vite
  2. Pune, India

    Software Engineer · Valuenaire.ai

    Full-time

    Full-stack product engineering, mostly on the frontend.

    • Designed and built a library of reusable, responsive UI components.
    • Built complex forms and data tables with dynamic fields, real-time validation and API integration.
    • Designed REST APIs and server-side logic in Node.js, Express and Mongoose for the features I shipped on the frontend.
    • Worked in an agile team owning features end to end, from scoping to cross-browser QA.
    • React
    • TypeScript
    • Node.js
    • Express
    • MongoDB
    • Tailwind CSS

03Selected work

Projects, written up as decision logs.

Each one walks through the problem, the constraints, the calls I made and what they cost, and what I'd do differently next time.
Android beta openIndependent product

Lekhit

Your UPI history, sorted automatically. A private personal finance and budgeting app built for UPI, with splits built in.

  • Expo
  • React Native
  • Tamagui
  • Reanimated
  • Gesture Handler
  • Supabase
  • Postgres RLS
  • Turborepo

Read the decision log

Earlier · where it started
  • HealthCare System

    Where it started. A MERN app for patients, doctors and admins, built in college.

    React · Node.js · Express

04Skills

A toolkit, grouped by the problem it solves.

01WebLarge React apps that stay fast and keep their shape as they grow.
  • React
  • TypeScript
  • Next.js
  • Vite
  • MobX
  • React Query
  • Zustand
  • Tailwind CSS
02MobileReact Native apps that feel native, down to the gesture.
  • React Native
  • Expo
  • Reanimated
  • Gesture Handler
  • Expo Router
  • EAS
03Design systemsTokens and themes that make the right choice the easy one.
  • Tamagui
  • Design tokens
  • Theming
  • Accessible components
  • MUI
04BackendEnough of the server to own a feature end to end.
  • Supabase
  • Postgres
  • Row Level Security
  • Edge Functions
  • Node.js
  • REST
05Infra & toolingMonorepos, CI and the guardrails around them.
  • Turborepo
  • Bun
  • Cloudflare Pages
  • Sentry
  • Claude Code

05How I work

Research, spec, plan, then execute.

AI changed how fast code gets typed. It didn't change what makes code good. I use Claude Code daily, with the boring parts written down so the output fits the codebase.
  1. 00

    Research

    Product decisions start with evidence: app-store reviews, competitor teardowns, the forums where people complain. Lekhit exists because that research found a gap.

  2. 01

    Spec

    A short written spec before code: the problem, the constraints, what's out of scope. If I can't write it down, I don't understand it well enough to build it.

  3. 02

    Plan

    Break the spec into steps that can each ship and be reverted on their own. Big migrations go out in phases, not in one heroic PR.

  4. 03

    Execute with agents

    Claude Code does the typing; I do the judgement. CLAUDE.md conventions, custom skills and parallel git worktrees let several streams of work run at once, and review stays human.

06Now

What I'm focused on this quarter.

Updated

  • Growing the Lekhit Android beta

    Watching how the first users import their statements, fixing what confuses them, and getting the app ready for a public launch.

  • Going from senior to architect depth

    Writing design docs before code, studying how large frontends split ownership, and getting better at the decisions that are expensive to undo.

  • Getting deeper into agentic coding

    Turning what works in Claude Code into reusable skills, conventions and guardrails, so speed never comes at the cost of code I'd be happy to review.

07Contact

Let's build something.

I'm looking for a senior frontend role on a product team that cares about craft. If that's you, or you just want to talk about frontend architecture, my inbox is open.