© 2026 | Carlos Diaz
Made with love and Good Vibes 😉
I'm Carlos Diaz, a Senior Fullstack Engineer with 6+ years building production web applications in TypeScript — Node.js and NestJS on the server, React, Next.js and Angular on the client. With a Master's in Information Technology from Universidad de Guadalajara, I specialize in owning features end to end: REST and GraphQL APIs, MongoDB data layers, and accessible component-based UIs.
Since 2022 I've been embedded full-time in a US healthcare SaaS through Improving, shipping HIPAA-compliant features across a TypeScript microservices platform in self-managed Scrum teams. I maintain Angular and React/Next.js codebases side by side, which is why I can advise on a framework decision from experience rather than from preference. Before that I contributed to IBM's Carbon Design System, which shaped my design-system thinking and my WCAG accessibility standards.
I integrate AI into real product workflows — generating vector embeddings to power semantic search — and accelerate delivery with AI pair-programming tools like Claude and GitHub Copilot, without compromising code quality. I'm Scrum.org certified (PSM I, PSD I, PSU I) and hold AWS Academy credentials in Cloud and Machine Learning Foundations.
I work daily with US-based clients in English, collaborate openly across product, design, and engineering, and consistently leave every codebase better than I found it.
Self-assessed proficiency
Common European Framework of Reference (CEFR)
First language. I think and design in it.
The language I work in every day: standups, design docs, code reviews and client calls with US teams mainly.
How they show up in my work
I write the design doc before the code, and I run reviews that leave product, design and engineering holding the same picture of the problem.
I reach for logs, traces and metrics before I reach for a rewrite. The fix that lasts is the one aimed at the actual cause.
I ask what a proposal costs at scale, under load and six months from now, before I agree that it works.
Constraints like HIPAA or an inherited schema are where my best design work happens. The interesting solution is the one that fits.
In self-managed Scrum teams I review generously, mentor deliberately, and treat a shared codebase as shared property.
Production incidents and requirements that move mid-sprint are part of the work. I keep the release calm and the team informed.
I decide with the information available, record why, and revisit the call when the evidence changes.
Where my study time goes right now
Targeted for the coming months




