Ex-Disney · Ex-Globant · Freelance since 2014
Hire a senior NestJS developer who ships.
I've built production NestJS APIs powering tourism platforms, healthcare CRMs and real-time mobile apps. Clean architecture, strong typing, real observability — not tutorials.
Start a projectArchitecture that survives scale
Modular NestJS with CQRS where it helps, pragmatic where it doesn't. Services split by bounded context, not by random convention. Testing built-in from day one.
Battle-tested integrations
Stripe, MercadoPago, WhatsApp Business, Twilio, SendGrid, OpenAI, Claude, OAuth providers, booking engines, CRM APIs — seen it, shipped it, know what breaks.
Solo engineer, senior mindset
You get an engineer who spent years at Disney and Globant shipping platforms used by millions — now available to your startup with zero coordination overhead.
Ships to production, not demos
Dockerized deployments, CI/CD, health checks, logging to Grafana or Datadog, proper error tracking, DB migrations that don't corrupt prod. End-to-end, not "it works on my machine."
The NestJS stack I work with
- NestJSBackend framework — modules, DI, pipes, guards
- TypeScriptLanguage — strict types, zero runtime surprises
- PostgreSQLRelational database — the default for transactional data
- PrismaType-safe ORM — schema-first, migrations I trust
- TypeORMORM for legacy codebases — decorator-heavy but stable
- RedisCache and rate limiting — fast, simple, boring (in a good way)
- BullMQBackground jobs and scheduled tasks on top of Redis
- DockerContainers — local parity with production
- GraphQLAPI query layer when REST becomes a chatty bottleneck
- WebSocketsReal-time transport — chat, presence, live dashboards
- SwaggerOpenAPI docs auto-generated from your DTOs
- JestUnit and integration testing built-in from day one
When NestJS is the right call
NestJS is my default when the backend will grow beyond a handful of endpoints. For a quick prototype, Express or Fastify can be faster. But the moment a project adds authentication, background jobs, third-party integrations, role-based permissions, and multiple developers — NestJS pays for itself in week two.
The dependency injection and module system force clean boundaries early, so you don't end up with the typical Node monolith where everything imports everything and tests are impossible. TypeScript is first-class, not bolted on. Pipes and guards give you real validation and authorization without reinventing the wheel. Interceptors make observability trivial.
Where NestJS doesn't fit: tiny CLI tools, edge functions with cold-start budgets under 100ms, or when your team strongly prefers Fastify's minimalism. For everything in between — an internal CRM, a multi-tenant SaaS backend, a booking platform, a mobile app API — it's the right tradeoff between structure and speed.
I've shipped NestJS backends handling complex multi-actor workflows (Argenway's CRM + ERP unification for a tourism operator), healthcare scheduling integrated with patient intake (Maeth), and real-time features on Socket.io for a global mobile community (Greether). Each one had a different shape, but the same fundamentals: explicit modules, testable services, zero surprise at 3am.
FAQs
Both. Most of my recent work is taking over or extending existing systems — auditing architecture, identifying bottlenecks, refactoring the modules that matter, and shipping new features without rewriting what already works. Greenfield is fine too, especially MVPs where getting to production fast matters.
PostgreSQL + Prisma is my default for new projects. TypeORM is still fine on inherited codebases — I won't push to migrate unless there's real pain. MongoDB when the data shape genuinely doesn't fit relational, not because it's trendy. Redis for caching, queues and rate limiting.
Full stack. On most projects I deliver Next.js or React frontends that consume the NestJS API, plus React Native when mobile is in scope. Hiring a single engineer who owns the contract between frontend and backend saves weeks of debugging.
Based in Rosario, Argentina (UTC-3). Comfortable overlap with Americas and European mornings. For Asian clients, I keep communication async and deliver on clearly scoped milestones.
Fixed-scope work for MVPs and defined features. Weekly retainer or hourly for ongoing work, audits or team augmentation. I'll never pad hours — if something takes less than the estimate, I pass the saving.
Yes to both. Mutual NDA before sharing sensitive code or architecture. Happy to sign client contracts or work under a simple SOW — I keep the legal overhead low so we can focus on shipping.
Need a NestJS engineer who actually ships?
Currently taking new freelance projects — audits, MVPs, feature work, team augmentation. Reply within 24 hours.
Start the conversation