Node.js backend and API development

A clear separation of routes, request validation, business logic and data access, with consistent error handling, logging and tests. That keeps endpoints thin and makes the code easy for any developer to extend, which is how I structure APIs for clients.

Yes, especially for I/O-heavy work such as REST APIs, integrations and real-time features. It shares TypeScript with your front end, has a large ecosystem and scales well horizontally. For CPU-heavy workloads I would recommend a different tool and say so.

REST is the default because it's simple to consume, document, and debug, and it fits most products. If your clients genuinely benefit from GraphQL, that's a conversation worth having during scoping rather than a reflex.

Yes. A common job is putting a clean API layer in front of an existing database or legacy service so new front ends and partners can use it safely, without rewriting what already works.

Clear structure, consistent error handling, validation at the edges, tests around the logic that matters, and written docs. The goal is that another engineer can pick it up in an afternoon - that's the standard I build to.