Open to select freelance projects
Hi, I'm Abhishek Kumar.
I build web applications, reliable backend systems, and AI-powered features that help turn ideas into working products. From a first MVP to improving an existing app, I care about the complete experience—not just getting code to run.
You do not need to figure out every technical detail before reaching out. Start with the problem; we can shape the right solution together.
Practical scope. Clear communication. Code you can continue to own.
Turn a clear idea into a usable first version.
For founders and small teams who need a product experience without stitching together multiple developers.
Make the parts behind your product dependable.
For teams that need a new API, a better data model, reliable integrations or help untangling existing backend code.
Put AI to work on a real business task.
For products that need a focused AI capability—not a chatbot bolted on just to say they use AI.
Improve what you already have before rebuilding it.
For teams with an existing app that needs a feature, third-party integration, bug fix or cleaner handover.
Not sure which service fits? Tell me what you are trying to achieve. We can start there.
Describe your projectA mix of full-stack products, backend systems and experiments. Open demos and repositories are linked where available; workbench builds are clearly labelled.
01FEATUREDA project and task workspace built around team collaboration, not just CRUD screens.
Includes project/task tracking, role-based access, live updates, in-app notifications, real-time chat, message receipts and online presence using server-sent events.
Useful reference for product dashboards, collaboration flows and real-time application features.
02FEATUREDIn progressAn AI support assistant businesses can configure, train on their own knowledge and embed on a website.
Combines a dashboard, protected account flows, business-specific knowledge, Gemini-powered replies and an embeddable chat widget.
Shows how an AI capability can be connected to a real product workflow and admin experience.
03FEATUREDA finance-focused application combining market information, interactive charts and AI-assisted exploration.
Built with a React interface, FastAPI services, MongoDB, JWT authentication, financial/news data workflows and Gemini integration.
Relevant to data-heavy dashboards, external API integration and AI-assisted product features.
04FEATUREDA blogging platform where content management and AI-assisted authoring sit in the same workflow.
The project includes public blog discovery, admin publishing tools, Gemini-assisted content creation, comment moderation, image handling and dashboard statistics.
Relevant to content workflows, admin tools and AI-assisted productivity features.
05Backend services for a social experience with media, interactions and paginated feeds.
The repository covers JWT auth, post CRUD, S3 image uploads, pagination, comments/replies, likes, Zod validation and rate limiting.
Relevant to content APIs, file uploads, validation and request protection.
06A role-based authentication project focused on protected routes and access-controlled experiences.
A compact implementation exploring sign-in flows, JWT-based session handling and role-aware authorization across a Next.js and Node.js stack.
Relevant to account flows, protected dashboards and role-aware products.
08Work in progressA Cloudinary-style media workspace concept for uploading, organizing and managing digital assets.
The build explores a Next.js interface, Cloudinary media operations, Prisma/PostgreSQL data modeling and Clerk authentication. Public demo/repository link is not currently attached here.
Relevant to media-heavy applications, asset workflows and secure SaaS dashboards.
12An attendance workflow exploring face recognition for user identification.
A learning project that explores computer-vision-driven identity matching and attendance tracking; it is presented as an experiment, not as an audited access-control system.
Shows exploration of computer vision and workflow automation.
13A backend API for restaurant operations, including employee and menu management.
The public repository documents CRUD operations, structured routing, environment-based configuration and MongoDB data access with Mongoose.
Relevant to internal admin tools and small-business operations software.
14A small utility app for practicing external API integration and data presentation.
A focused project around fetching weather-related information and presenting it through a lightweight interface.
Relevant to third-party API integration and small, focused interfaces.
15Learning repositoryA focused repository for exploring common backend patterns with NestJS.
Covers API structure, authentication, authorization, database access, validation, caching and security topics as a learning reference.
Shows ongoing investment in structured backend engineering.
These are personal projects, learning builds and product experiments—not claimed client case studies. For client work, I share only details that are appropriate to make public.
The details change from project to project, but the way of working should never be mysterious.
We discuss the user, the business goal, current constraints and what a useful first delivery should accomplish.
I turn the brief into a clear scope, milestones, assumptions and deliverables before implementation starts.
You get focused updates, reviewable increments and a chance to give feedback before work drifts off course.
We review the result, document important decisions and cover the setup or deployment steps agreed in the scope.
The roles behind my approach to backend systems, full-stack features and product delivery.
Building backend foundations for Qedix, an AI-powered pull-request review platform for JavaScript and TypeScript repositories.
Worked on full-stack features and backend integrations in a live product environment.
Developed application features across frontend and backend codebases.
Built backend services and REST APIs using Node.js, Express.js and MongoDB.
I choose tools to fit the problem, existing codebase and delivery needs—not the other way around.
Application logic, APIs and access control.
Persistence, caching and background processing.
LLM-powered workflows and retrieval-oriented applications.
Usable product experiences backed by reliable services.
Collaborative development, deployments and operational basics.
Technologies reflect tools used across professional work and personal projects. Depth varies by tool and use case.
A little context on my background, how I think about engineering and what I bring to a project.
Backend · Full-stack · AI integrations
Bengaluru, IndiaI enjoy building things that are useful, reliable, and understandable.
My work sits at the intersection of backend engineering and product development. I spend a lot of time thinking about API boundaries, data models, authentication, integrations and asynchronous jobs—but I also care about whether the person using the product can complete their task without friction.
My professional experience spans backend development, full-stack product work and my current role as a Founding Engineer at Qohere. Alongside that work, I build personal projects to explore product ideas, AI capabilities and the engineering patterns behind them.
When working with a client, I aim to make the technical side feel less opaque: understand the actual need, make the trade-offs clear, build in reviewable steps, and leave behind something that can be maintained.
Cochin University of Science and Technology
B. N. Mandal University, Madhepura
A few things people often want to know before discussing a project.
Web apps and MVPs, API/backend work, AI integrations, workflow automation, and targeted improvements to an existing application are all good starting points. If the scope is unclear, we can begin with a short discovery conversation.
Yes. I can review the current architecture, identify a practical first milestone, and work within the stack where it makes sense instead of proposing a rewrite by default.
After understanding the scope, constraints and priority, I can suggest milestones and a project-specific estimate. I avoid quoting a fixed price before the work is clear.
The goal is a clear handover: readable code, setup guidance and notes about important decisions within the agreed scope. Credentials and deployment ownership should remain with the client wherever practical.
Share the idea, the problem or the part of your app that is slowing you down. A rough brief is completely fine.
No need for a perfect spec. Give me the context and we can work out the next sensible step.