Hire a JavaScript developer who works on both sides of the wire

Soham Dang writes JavaScript on both sides of the request — Node.js and Express services on the server, React interfaces in the browser — which is what lets one engineer own an API contract end to end.

JavaScript's reach is its main advantage and its main hazard. The same language everywhere removes context switching, but it also means the same engineer can make a server-side mistake that only shows up under concurrency and a client-side one that only shows up on a slow phone.

What follows is the part of JavaScript work that is not framework knowledge.

The language-level work that matters

  • Asynchronous control flow

    Promise composition, concurrency limits and cancellation — so a request that fans out to four services fails cleanly instead of hanging.

  • Error boundaries that actually catch

    Rejections handled where they can be acted on, not swallowed in a catch that logs and continues.

  • Memory and event-listener discipline

    Long-lived Node processes and long-lived SPA sessions both leak in ways that only appear after hours of uptime.

  • Types where they earn their keep

    TypeScript at the API and component boundaries, where a rename should break the build rather than production.

Where it gets used

Node.js and Express REST services with layered middleware, MongoDB access through Mongoose, and integrations with Razorpay, Cloudinary, the WhatsApp Business API and the OpenAI API.

On the client, React and Next.js with Redux where state is genuinely global, plus Three.js and React Three Fiber for WebGL work where the JavaScript has to stay off the main thread's critical path.

One language, two very different disciplines

Server-side JavaScript is judged on throughput, isolation and failure behaviour. Client-side JavaScript is judged on bundle size, interaction latency and how it behaves on a device four years old.

Treating them as the same skill is the most common reason full-stack JavaScript work goes wrong. The syntax transfers; the judgement does not.

Common questions

What JavaScript experience does Soham Dang have?

3+ years writing production JavaScript across three companies, on both Node.js/Express services and React/Next.js interfaces, including a 25+ module multi-tenant platform.

Does Soham Dang use TypeScript?

Yes. TypeScript is part of his daily stack, applied at the boundaries that matter most — API responses, component props and shared state — rather than uniformly for its own sake.

Can Soham Dang work on server-side JavaScript only?

Yes. Backend-only engagements are covered in more depth on the Node.js developer page, which goes into API architecture, authentication and database work.