Web apps
Angular and maintainable front-end architectures
Juan Conrado
// operational reliability, engineered in from day oneI design resilient and auditable systems that operate under load.
Full stack reliability specialist, 5+ years with Angular and Node.js/NestJS. I work on critical systems where data loss, duplicate events, or service degradation are not an option.
capabilities
Mobile apps
Mobile experiences built with web technologies
Desktop apps
Desktop applications powered by web stack
Data pipelines
Ingestion, normalization, and idempotency in production
Custom integrations
APIs, webhooks, and custom connectors
Backend and AWS
Node.js/NestJS and serverless, especially Lambda
What I build.
I build production systems and document verifiable technical patterns without exposing confidential client information.
Real-time media system on mediasoup (SFU). Focused on low latency, audio/video stability, and full control over the WebRTC stack. Built in public with technical progress documented on the blog.
end-to-end p95 latency: metric published with each update
typescript · node.js · mediasoup · webrtc · websockets
I design and implement robust integrations across systems with clear contracts, traceability, and failure handling. My approach combines APIs, queues, validation, and observability to keep operations stable over time.
node.js · nestjs · aws lambda · event-driven · observabilidad
the rest of the stack
i.
Full-stack applications, end to end
I build the whole product: APIs in Node.js/NestJS, interfaces in Angular, and the wiring between them. I can take a project from scratch or plug into an existing team.
typescript · angular · node.js · nestjs · tailwind
ii.
Backend and event-driven architecture
When the system has to handle load and not lose data: queues, retries, idempotency, strong typing. I think the architecture through before writing code.
typescript · node.js · nestjs · aws lambda · api gateway · dynamodb
How I run a project.
01 discovery
I align on goals, technical context, and business constraints. In this phase I identify risks and define a realistic scope.
02 design
I propose architecture and technical decisions with explicit trade-offs. No unnecessary complexity, yes sustainable choices.
03 implementation
I build for maintainability: strong typing, clear contracts, observability, and failure handling from day one.
04 delivery
I deliver with useful documentation and clear handoff to the team. The goal is not only to ship, but to operate without friction.
I write while I build.
what I learn, told in plain words
The first entries are on their way. I'm writing them right now.
Where I've built.
2023 — present
Senior Node.js Engineer / Senior Full Stack Engineer
N-iX, Bogota
I work on backend integrations and event-driven architecture on AWS, focused on idempotency, observability, and fault tolerance. I have also built insurance microservices with NestJS and Angular.
2020 — 2023
Backend Tech Lead / Full Stack
Smartsoft Labs
Led teams under SCRUM and built backend services with Clean Architecture —including a RabbitMQ notifications service— and a WebRTC video-call system. That WebRTC R&D is the seed of my current real-time media work (MRS).
Let's talk reliability.
If your system operates under load and you need to reduce operational risk, I can help you design and implement a more resilient architecture.