Software engineer — full stack · in production since 10/2024
Karan Keshav Dabare
Full-stack engineer — React, Next.js, React Native, and Node.js.I build the UI and the backend behind it, not just one side.Now shipping and owning full systems, end to end.
I'm a full-stack engineer in Pune working across React, Next.js, React Native, and Node.js. The work I'm best at sits where a UI has to tell the truth about a backend — auth sessions, wallet balances, live table availability — and where getting that wrong is immediately visible to users.
Since March 2026 I've been independent: taking client systems from requirements through architecture, development, and deployment, and staying around for what breaks after launch.
- availability
- open — full-time · freelance
- replies within 24h, IST
- location
- Pune · remote
- IST (UTC+5:30)
- now
- entavra — in development · active client work
- details on request
Journey
Inherit systems, stabilize systems, design systems. Each role answered a different question.
- B.E. Computer Science Engineering — Marathwada Mitra Mandal's Institute of Technology, Pune (SPPU)02/2021 – 09/2023
- Diploma in Computer Engineering — Shri Sai Polytechnic College, Chandrapur04/2018 – 07/2021
How I Think
The work before the code — understanding a product well enough to know what to build.
Before I open a design file or an editor, I try to answer a simpler question: what is this product actually for, and who is it for? A lot of what looks like design or engineering is really that — deciding what someone should understand in the first few seconds, what deserves their attention, and what should quietly be left out. Those calls get made before anything visual exists, and they're the ones that are expensive to get wrong.
So I build the model first — the business behind the product, the people who'll use it, the path they take through it. Structure and hierarchy fall out of that, not out of a layout grid. Only once it's clear do I move into design, architecture, and code, where the work goes faster because the decisions that shape everything are already made.
- 01What is this product actually for?
- 02Who uses it, and what do they need from it?
- 03What has to land in the first few seconds?
- 04What earns attention — and what gets cut?
- 05How is the information ordered, and why that order?
- 06How should the business come across?
- 07What should someone leave with?
It shows up in how I use tools like Claude Code and Cursor, too. I don't hand them a vague instruction and hope — I give them the context first: the objective, the constraints, who it's for, what the result should be. The prompt ends up reading more like a short product spec than a request. The understanding still has to come from me; the tools are only faster at the part that comes after it.
Selected work
Three systems I answer for end to end. Each card opens a full case study — architecture, the hard problems, and the tradeoffs I chose.
03/2026 – present · Opezey.com
Snooker Cafe Management System
Cross-platform venue management — a React Native app for staff, a Next.js platform for owners, kept in real-time sync over a Socket.io event layer.
09/2025 – 01/2026
Online Gaming & Wallet Platform
The frontend integration layer for card and crypto payments on a live, high-traffic wallet platform — many providers, one interface, state that has to be right.
2026
Multilingual IVF Platform
A fertility-care platform in English, Hindi, and Marathi from one Next.js codebase — locale routing and per-language SEO so each version is independently discoverable.
Job import pipeline with queue-based ingestion
A full-stack take-home built end to end: jobs are pulled from an XML feed (Jobicy), parsed with axios + xml2js, and pushed through BullMQ on Redis in configurable batches. A worker upserts each job into MongoDB, tracking new-versus-updated per run; an ImportRun records progress while batches process and an ImportLog captures the final tally. node-cron re-imports hourly.
The interesting part is the shape: ingestion as a queue of batches rather than one long request means the import survives slow feeds, retries at batch granularity, and reports progress while running — and the Next.js dashboard that triggers imports and pages through run history gets to be a thin client over honest state.
Aesthedent — dental clinic website
A production website for a dental clinic client, built with Next.js. The repository is the story here: 104 commits of sustained, conventional-commit-formatted work — scoped feat/fix messages on a solo client project where nobody was checking. That's what the discipline looks like when it's a habit rather than a policy.
GitHub profile scraper
A small, complete automation: a Python script drives Playwright to extract profile data from GitHub — username, bio, follower and repo counts — and persists it to Supabase, with the table schema shipped as SQL alongside the script.
Skills
The stack I actually reach for, grouped by layer. Hover a chip for where it's been used.
Stacks
Frontend
Backend
Data
Cloud / deploy
Tooling
Fundamentals
Contact
Building something, or hiring for a role you think fits? Tell me what you're working on.