Full-Stack Development

I build the whole slice of an application, not just one layer of it: the interface, the API it talks to, the database behind that, and the deployment that keeps it running. That ownership is what lets a feature move from idea to production without getting lost at a hand-off.

On the front end that means Next.js and React with TypeScript, built as server-rendered pages where that matters for speed and indexability, and as interactive dashboards where it does not. On the back end it means Node.js services, often with Express.js or NestJS depending on how much structure the project needs, talking to PostgreSQL, MongoDB or both.

This is the shape of most of the production systems in my work: a learner app and its admin dashboard sharing one backend, a booking platform with its own API, a CRM built on top of an existing codebase rather than a rewrite. The constraint is usually the same — ship a working feature, then the next one, without the system getting harder to change.