Aman Kumar Singh — Team Lead & Senior Software Engineer. React, Next.js, Node.js, NestJS, PostgreSQL, Redis, and AWS.
Salem’s steel, textile, and agriculture businesses are the ones commissioning software, usually to tighten operations rather than to launch a product. Straightforward operational systems, built to run for years without a maintenance team standing by.
An industrial base moving to digital operations on its own timeline. I am Aman Kumar Singh, a Team Lead and Senior Full Stack Engineer in Noida: 6+ years, 15+ production applications, and teams of 5–10 engineers led through delivery.
Salem engagements run remote-first from my base in Noida, with a scheduled on-site visit for kickoff or a major release when it is worth the flight. Everything is on IST, so there is no timezone gap — same working day, same standup.
What I build for Salem clients
—Plant data capture, yield reporting, and dispatch reconciliation.
—Lot tracking, production planning, and export order management.
—Procurement, grading, and payment tracking for growers.
Yes. Salem engagements run remote-first from my base in Noida, with a scheduled on-site visit for kickoff or a major release when it is worth the flight. Everything is on IST, so there is no timezone gap — same working day, same standup.
What kind of software do Salem businesses usually need?+
Straightforward operational systems, built to run for years without a maintenance team standing by. Concretely, that tends to mean plant data capture, yield reporting, and dispatch reconciliation, lot tracking, production planning, and export order management, and procurement, grading, and payment tracking for growers. The stack is React and Next.js on the front end, Node.js and NestJS services behind it, PostgreSQL and Redis for data, and AWS for deployment.
Can you work with our existing stack in Salem?+
Yes. My default is TypeScript throughout — React and Next.js on the front, Node.js and NestJS services, PostgreSQL and Redis, Docker and AWS — but if your Salem team already runs something else, I work in it rather than arguing for a rewrite. Recommending a migration only makes sense when the current setup is genuinely the problem.
What does a Salem project typically cost?+
It depends on scope, so I quote per project rather than publishing a rate card. Before any money changes hands you get a fixed scope and timeline for phase one — you should know what you are buying before you agree to it. Email aman97aman@gmail.com describing what you want built in Salem and I will come back with a scope and an estimate.
Can you join an existing Salem team rather than build from scratch?+
Yes, and with an established Salem team that is often the better arrangement. I have led teams of 5–10 engineers and spent a lot of time in code review and mentoring, so joining an existing codebase to raise the standard — testing, CI, module boundaries, review culture — is familiar work rather than a compromise.
Read the engineering writing
The reasoning behind how I build — 200+ articles on architecture, backend, and performance.