I have spent more than nine years building complete web and mobile applications, from the interface through to the database. I do not think of myself as purely “frontend” or “backend”: I am a product engineer. I choose the tool that best solves the problem.
I have worked with Angular from version 2 through to 19, with React and Next.js across multiple projects, and with Node.js and Python on the backend. Stack choices should always depend on context: team size, performance requirements and how quickly the product needs to evolve.
Typical stack
- Frontend — Angular, React, Next.js, Tailwind CSS.
- Backend — Node.js (NestJS, Express), Python (FastAPI, Django).
- Databases — PostgreSQL, MongoDB, Redis.
- APIs — REST, GraphQL. Design and documentation with OpenAPI.
Real projects
- B2B e-commerce platform with a microfrontend architecture: Angular and NestJS, allowing four teams to work in parallel without stepping on each other.
- Real-time analytics dashboard with React, WebSockets and PostgreSQL for operational KPI monitoring.
- Progressive migration from a PHP monolith to Node.js microservices with no downtime, maintaining backwards compatibility through a six-month transition.
FAQ
- What does modern full-stack development mean?
- It means building the whole product with judgement: interface, backend, data, performance, deployment and maintainability, without treating each layer as a separate silo.
- Can you join an existing product?
- Yes. I work well with live products: I audit architecture, technical debt and critical flows before proposing changes the team can absorb.
- Which technologies do you work with?
- I commonly work with React, Next.js, Angular, Node.js, Python, PostgreSQL, Redis, REST APIs, GraphQL and modern deployment tooling.
If you need to build something solid, or an existing product needs a technical step forward, contact me at [email protected].