91%
Faster candidate screening
An autonomous scoring engine evaluates every open hiring ticket in a single pass.
I am a Software Engineer at Grid Dynamics, building AI-powered backend platforms that replace manual work with measurable throughput. Most of my time goes to asynchronous APIs, LLM integration and cloud-native infrastructure.
91%
An autonomous scoring engine evaluates every open hiring ticket in a single pass.
90%
Screening workflows that used to be human-driven now run end to end without intervention.
35+
Asynchronous FastAPI services backing structured and semantic data workloads.
80%
Untrusted user code isolated inside Firecracker microVMs rather than shared runtimes.

Bengaluru, India
Hardik Kumar Singh
Every architectural choice should be defensible in terms of latency, cost, or hours of human work removed.
Blocking a request thread on an LLM call is a design decision. Usually the wrong one.
User code, model output, and third-party responses all get a boundary before they touch the system.
I am Hardik, a Software Engineer at Grid Dynamics working on enterprise AI platforms that automate hiring workflows. I graduated from MNNIT Allahabad with a B.Tech in Computer Science and Engineering, and I have spent every role since trying to answer the same question: what has to be true for this system to still work when the load, the data, or the team triples?
My work sits at the intersection of backend engineering and applied AI. That means asynchronous FastAPI services, LLM integration through Vertex AI and GPT-4, PostgreSQL schemas designed for the query patterns they will actually see, and containerised deployments on Cloud Run that a small team can operate without a dedicated platform group.
What I care about is measurable impact rather than technology for its own sake. Ninety-one percent less screening time and a thirty-five percent accuracy improvement are the numbers I am proud of, because behind each one is a design decision that could have gone the other way.
2021
B.Tech in Computer Science and Engineering, finishing with a CPI of 8.27.
2024
Real-time object detection on a Jetson Nano taught me that latency budgets are a hardware conversation.
Jan 2025
Led the backend of an LLM-powered learning assistant and shipped 35+ REST APIs into production.
Aug 2025
Now own backend systems for an AI talent acquisition platform used to automate real hiring workflows.
Motilal Nehru National Institute of Technology, Allahabad
B.Tech, Computer Science and Engineering
CPI 8.27
Dec 2021 — May 2025
G.N. National Public School
CBSE, Class XII
95.4%
Apr 2021
AWS Certified Cloud Practitioner
Amazon Web Services
Certified
Depth in a handful of things and working literacy in the rest. This is what I reach for, not everything I have installed.
Chosen for the problem, not the résumé.
Asynchronous services that hold their latency budget.
Schemas designed for the queries they will actually see.
Containerised, cost-aware, and operable by a small team.
Models treated as a dependency with a latency and cost budget.
The unglamorous half of shipping.
I joined Grid Dynamics as an intern and stayed to own backend systems in production. Every achievement below has a measurement attached to it.
Grid DynamicsBengaluru, India
Own backend systems for an AI-powered talent acquisition platform: the APIs, the data model, the model integration, and the deployment path that carries them to production.
Grid DynamicsHyderabad, India
Led the backend of an LLM-powered learning assistant that turns arbitrary source material — PDFs, repositories, documentation, code — into interactive learning experiences.
Scroll to travel sideways
Screening that finishes before the recruiter opens the tab.
An enterprise platform that automates candidate screening end to end. Every incoming CV is parsed, embedded, semantically matched against open job descriptions, scored, and ranked — without a recruiter having to open a single profile first.
Any source material, turned into something you can practise against.
A learning platform that ingests PDFs, GitHub repositories, documentation and raw code, then generates interactive material from them: Q&A, guided explanation, and coding exercises that are evaluated automatically by executing the learner's submission.
Real-time detection on hardware that fits in your hand.
A computer vision system for real-time object detection and intelligent surveillance, running CenterNet ResNet-101 on a Jetson Nano across multiple live RTSP streams, with a chatbot layer that answers questions about what the cameras actually saw.
This is the shape most of my work takes: a thin async edge, model calls pushed off the request path, and storage chosen per access pattern rather than per habit. Select a node to see what it is responsible for and what it is allowed to fail at.
Hover or select a node
Labels are cheap. Each card opens onto the specific practices behind it.
FastAPI services built non-blocking from the start, so an API that depends on multi-second inference still answers in milliseconds and reports progress rather than holding a connection open.
Advanced filtering and pagination designed against the access patterns the client actually has, which is what turned into a 35% improvement in recruiter workflow efficiency.
35+ endpoints presenting relational, vector and cache storage as one coherent surface, so callers never need to know which store answered them.
The systems I am proudest of are proprietary. These are the repositories anyone can read.
Almost everything I have built professionally lives behind a company login, so this is the smaller half of the picture: the computer vision system from my final year, a conference site, and the web projects I learned on before I moved to backend work.
I am looking for backend and platform work where correctness and scale both matter, and where AI is part of the system rather than the pitch. If that sounds like what you are building, I would like to hear about it.