RTS Questionnaire · Question 18 of 52 · file: answers/q18.html
Have you worked with Node.js or Golang or any other web based frameworks? Optional.
Node.jsGolangBackend
✅ Yes — Node.js is a regular part of my stack, and I also build services in Go-style and Python/JVM frameworks when the use case fits.
Technical detail
- 🟩 Node.js (3+ years commercial) — Express-based REST APIs, middleware pipelines (auth, content negotiation, cookies, multipart uploads, request-scoped state), WebSocket/real-time services, MongoDB and PostgreSQL persistence, caching and third-party API integration, and Jest-tested handlers.
- 🧱 TypeScript-first Node — typed service layers, DTO validation, OpenAPI contracts, structured logging and graceful shutdown; deployment as containers or serverless functions.
- 🐹 Go — straightforward compiled services and CLI utilities with standard-library HTTP servers, goroutines for concurrency, context propagation and small static binaries that are ideal for sidecars and lightweight microservices.
- 🌐 Other web frameworks in my portfolio — Java Spring Boot 3/4 (primary), ASP.NET Core (.NET), Python FastAPI/Django/Flask, and front-end frameworks Angular 17/18, React 19 and Next.js.
🧠 The value of framework breadth: I choose pragmatically — Node.js for I/O-heavy APIs and real-time features, Spring Boot for complex enterprise domains, .NET where the enterprise standard demands it, FastAPI for data/AI services. 🔁 Common denominators across all of them: layered structure, typed contracts, automated tests, CI/CD and observability.
🧾 CV evidence: 2025 CV: 'Node.js' in core skills and Wizeline role (Java, Python, Node.js, TypeScript, React); 2023 CV ExpressJS patterns section; standalone Node/Express technical assessment (Oct 2025); Spring Boot 3/4 as primary back end.