PRAVEEN YADAVFULL-STACK SOFTWARE ENGINEER · MUMBAI
I’m Praveen. I build web products end to end: the screens people use, the API behind them, the data underneath, and the servers that keep it all running.
One education platform for office staff, teachers, students and guardians, where the server decides what each person can see and do.
6 services behind one app72 data models246 API routes across 24 modules
A QA and delivery workspace where features, acceptance criteria, test runs, defects and team chat all link to each other.
93 API endpoints25 pages11 delivery stages, role-gated
A market research app that computes its analytics once a minute, explains every scanner match and is built so it can’t place a trade.
12 scanners that explain themselves1/min analytics refresh, shared by every user0 ways to place a trade
ALSO: WORK PROJECTS AND AN INTERNAL SERVICE
I’m a full-stack developer in Mumbai with around three years of development experience. I like the front of a product as much as the back, and I get uneasy shipping a screen if I don’t understand what happens after the click.
Day to day that means React, Node.js, Postgres or Mongo, sockets, and whatever deployment the project needs. The products so far have been school software, a QA tool, a market research app and an HR platform. Not a theme exactly, but they all have real users with real data, which is the part I enjoy.
Given the choice I’d rather own the whole path of a feature: what the user actually needs, what the API should allow, how the data is shaped, and being around after it ships.
B.Sc. in Computer Science, class of 2021.
I traded Nifty options for roughly five years before switching to engineering. It isn’t dev experience, but it is why The Rookie Traders exists and why it refuses to invent data.
QA Flow and The Rookie Traders I built alone. At work I’m part of a team, with a few services that are mine end to end.
A decision in the interface usually changes the API, the data model and how the thing runs in production. I’d rather follow it all the way down than hand it off halfway.
I build React interfaces around real workflows: shared components, clear permission states, layouts that change with the role. I would rather disable a button and say why than hide it and get a bug report.
React · TypeScript · Next.js · Tailwind CSS · Redux Toolkit
In SOL Assists, office staff, teachers, students and guardians all use the same app and see different things.
Full Stack Developer
I work on a workforce and HR platform used by multiple companies. Day to day that is React and Node.js modules, database migrations, code reviews and releases with the rest of the team. A few pieces are mine outright: the realtime and notification service, our internal admin console, and the monitoring setup.
Before this I spent several years trading Nifty options. I count that as domain knowledge, not as development experience.
Route guards and hidden menus are for ergonomics. The server decides what you can do and whose rows you can see, and it should decide from the session, not from whatever the request claims. I learned this properly on SOL Assists, where four kinds of user share one app.
A blocked release, a ranked candidate, a scanner match. Each of those is a decision, and a decision without a reason just gets worked around. So the reason ships with the answer, in words a person can argue with.
A zero that means “unknown” looks exactly like a zero that means zero. In The Rookie Traders a missing value renders as unavailable, full stop. That rule came from years of staring at charts that quietly lied.
Logs, metrics, a way to replay what went wrong and a note on how to recover. I treat those as part of the feature, because they are what make a system survivable when it breaks at a bad hour.
Some projects need a .NET backend, a machine learning piece, proper design work, or a dedicated QA and DevOps hand. For those I bring in people I have worked with and trust. They aren’t listed by name here, but this is roughly what the bench looks like.
3+ Years Experience
That’s me. The interface, the API, the data, the realtime bits and the production setup behind them, end to end.
5+ Years Experience
Enterprise backends, heavy database work, APIs and the kind of production support that needs someone who has seen it before.
Google Cloud certified
4+ Years Experience
Model integration, data pipelines and automation for products that need some intelligence without a research team.
2+ Years Experience
Takes rough flows and turns them into Figma prototypes and clean, responsive screens.
3+ Years Experience
Test automation, CI/CD, Docker, cloud setup and the Linux side of keeping things running.
Tell me what you’re building. I take on the full-stack work myself and pull in the right person when it makes sense.
Got a product idea, or a system that is misbehaving?