I'm a Senior Full Stack Engineer focused on building scalable, maintainable, and business-driven software.

I have experience working across the full software development lifecycle, from understanding business requirements and designing software architecture to building backend services, REST APIs, modern frontend applications, database models, integrations, authentication systems, and deployment environments.

My main focus is turning complex business requirements into reliable software solutions using modern technologies, pragmatic architecture, and solid engineering practices.

• 💻 Senior Full Stack Engineer
• ⚡ Specialized in TypeScript and modern web development
• 🏗 Interested in scalable and maintainable software architecture
• 🔌 Experience designing and developing REST APIs and backend services
• 🗄 Experience with relational databases, PostgreSQL and MySQL
• 🔐 Experience building authentication and authorization systems
• 🌐 Experience working across frontend and backend applications
• 🤖 AI-Assisted Development enthusiast

I enjoy understanding how a business works and translating its requirements into well-structured software that is easier to maintain and evolve.

I believe good software should not only work today — it should also be understandable, maintainable, secure, and ready to evolve as business requirements change.

Some of the practices and concepts I work with:

• Clean Architecture
• Domain-Driven Design (DDD)
• Modular architecture
• REST API Design
• Repository Pattern
• Service and Application Layers
• Mapper Pattern
• Authentication & Authorization
• JWT
• OAuth2
• Role-Based Access Control (RBAC)
• Database Modeling
• Multi-tenant architectures
• Input Validation
• Error Handling
• Automated Testing
• Dockerized Development Environments

I prefer pragmatic engineering decisions over unnecessary complexity. Architecture should help the team build and maintain software, not become an obstacle.

Throughout my career, I have worked on software solutions involving:

Building applications where frontend and backend work together as a complete system, including user interfaces, APIs, authentication, data models, and business workflows.

Designing and implementing REST APIs, application services, authentication systems, business rules, validation, error handling, and integrations with external services.

Developing backoffice and administration platforms used to manage business operations, data, users, products, customers, and internal workflows.

Working with:

• JWT authentication
• OAuth2 integrations
• Google authentication
• Role-based authorization
• Secure HTTP cookies
• Input validation
• Protected routes and API endpoints

Working directly with relational databases and data models using:

• PostgreSQL
• MySQL
• Prisma ORM
• SQL

My experience includes designing relationships, constraints, indexes, tenant boundaries, and data models based on business requirements.

I have experience integrating applications with external platforms and services, including:

• AWS services
• Salesforce
• Email providers
• OAuth providers
• Cloud storage
• External REST APIs

A full-stack multi-tenant SaaS platform designed to centralize commercial operations for organizations.

The platform acts as an internal Commerce Command Center, allowing organizations to manage:

• Products
• Customers
• Sales orders
• Suppliers
• Purchase orders
• Goods receipts

The project focuses on solving a common problem in small and medium-sized organizations: commercial information spread across spreadsheets and disconnected tools.

Each organization operates independently, with data isolation enforced throughout the application.

• Multi-tenant architecture with organization-scoped data
• Users can belong to multiple organizations
• Membership roles: OWNER, ADMIN, and MEMBER
• Modular backend architecture
• Pragmatic DDD and Clean Architecture
• Business rules encapsulated in the domain
• Historical snapshots for sales order products
• Controlled order lifecycle transitions
• Partial and complete goods receipts
• Stock updates triggered by goods receipts
• Consistent API response and error formats
• JWT authentication using secure httpOnly cookies
• Internationalized frontend in Spanish, English, and French
• End-to-end testing for public application routes

The project also explores responsible AI integration as an optional assistant rather than as an autonomous decision-maker.

The platform integrates:

• Google Gemini
• OpenAI

AI capabilities are designed to assist users with:

• Operational summaries
• Contextual section summaries
• Guided operational searches
• Connector availability checks

The AI layer is read-only and cannot:

• Modify business data
• Create records
• Modify stock
• Change order states
• Execute arbitrary database queries
• Bypass multi-tenant isolation

The project also includes a deterministic supply review that identifies low-stock products and evaluates pending purchase orders without relying on an LLM.

The repository is organized as a monorepo with dedicated documentation at different levels:

• 📘 Project Overview — Overall architecture, project scope, business context, and how the frontend and backend work together.
• 🖥️ Frontend Documentation — Frontend architecture, application structure, UI, internationalization, authentication flow, and testing.
• ⚙️ Backend Documentation — Backend architecture, API, domain logic, multi-tenancy, database design, security, and AI integrations.

I enjoy backend engineering because it sits at the intersection of business requirements and technical decisions.

When building backend systems, I usually think about:

1. What business problem are we solving?
2. What are the important business rules?
3. What data needs to exist?
4. What relationships and constraints should the database enforce?
5. Where should the business logic live?
6. How should the API expose the functionality?
7. How do we protect authentication and authorization?
8. How can the system evolve without becoming difficult to maintain?

I particularly enjoy working with modular architectures where business domains have clear responsibilities and infrastructure concerns remain separated from core business logic when appropriate.

I enjoy working across the full stack because it gives me a broader understanding of how software systems work end to end.

A feature often involves more than implementing a UI or writing an API endpoint.

It can involve:

• Understanding the business requirement
• Designing the data model
• Defining business rules
• Implementing backend services
• Designing API contracts
• Building the frontend interface
• Handling authentication and authorization
• Managing loading and error states
• Testing the workflow
• Integrating external services

Having experience across these areas helps me understand the impact of technical decisions beyond a single layer of the application.

I actively incorporate AI-assisted development tools into my engineering workflow.

Tools I use include:

• ChatGPT
• GitHub Copilot
• Cursor

I use AI to support areas such as:

• Software design
• Architecture discussions
• Code implementation
• Refactoring
• Code reviews
• Test generation
• Debugging
• Documentation
• Exploring technical alternatives

I see AI as an engineering tool, not a replacement for technical judgment.

The responsibility for architecture, correctness, security, maintainability, and business decisions remains with the engineer.

I'm continuously improving my skills and exploring areas such as:

• Software architecture
• Advanced TypeScript patterns
• Scalable backend systems
• AI-assisted software development
• Responsible LLM integration
• Multi-tenant SaaS architectures
• System design
• Cloud-native development

I enjoy working with people from different technical and professional backgrounds.

Beyond software development, I have also taught dance classes, which helped me develop communication, patience, and the ability to adapt explanations depending on the person and their experience level.

Those skills have also influenced how I work in engineering teams. I enjoy sharing knowledge, discussing ideas, helping teammates, and learning from different perspectives.

I'm open to connecting with developers, engineering teams, and opportunities where I can contribute to building high-quality software.

Building scalable, maintainable, and business-driven software through pragmatic engineering and continuous learning.