What a full stack developer actually does
A full stack developer builds both the interface a user sees and the server, API and database behind it. Soham Dang works this way in production, on React and Next.js frontends backed by Node.js, Express.js and MongoDB.
The term gets used loosely enough to be almost meaningless. It is worth being specific about what the role covers, because that determines when hiring one is the right decision and when it is not.
This page is the informational counterpart to the hiring page. If you already know you want to engage someone, that page is more useful.
The layers the role spans
Interface
Component architecture, state management, routing, accessibility and performance in the browser.
API
Endpoint design, request validation, authentication, authorisation and error handling on the server.
Data
Schema design, indexing, query performance and the aggregation work behind anything computed.
Delivery
Build pipelines, environment configuration, deployment and production monitoring.
Where the actual value is
Not in knowing more technologies. It is in owning the boundaries between them. The API contract, the auth model, the shape of what the client caches — these are decisions that span layers, and they are made better by someone who has to live with both sides.
A specialist frontend engineer and a specialist backend engineer will each make locally optimal choices. The cost of reconciling them is usually invisible until it is a sprint.
When one full stack developer is the wrong answer
When the product is large enough that no one person can hold it, specialisation wins. When it needs deep expertise in one area — real-time video, heavy data engineering, native mobile — a generalist is the wrong tool.
And when several teams work in parallel, the coordination overhead a full stack generalist avoids reappears somewhere else. Being honest about this matters more than winning the engagement.
How Soham Dang practises it
Design the data model and API contract first, because that is where cross-layer mistakes are cheapest to fix. Put tenancy and permissions in middleware so they cannot be forgotten per route. Push computation into the database rather than the application layer.
Then ship in vertical slices — database through interface — so there is always something real to react to instead of two half-finished halves.
Common questions
What is a full stack developer?
A full stack developer builds both the client-side interface and the server-side API, database and deployment behind it. In practice this usually means one language across the stack — JavaScript or TypeScript with React, Node.js and a database like MongoDB.
What skills does a full stack developer need?
Frontend framework and state management, REST API design, authentication and authorisation, database schema design and query performance, plus deployment and monitoring. The boundary-spanning decisions matter more than breadth of tools.
Is Soham Dang a full stack developer?
Yes. Soham Dang is a Senior Full Stack Developer and Technical Engineering Lead with 3+ years shipping production MERN applications across three companies, currently at Avani Enterprises Ltd.