General information

Introduction

I am a passionate developer with a lifelong interest in technology and programming. Over the years, I have developed a versatile skill set that goes beyond technical expertise—I bridge the gap between complex technical challenges and business needs. My experience spans from backend development and DevOps to frontend work and mobile technologies, enabling me to approach problems holistically and deliver results that positively impact both the product and the organization.

I thrive on transforming challenges into opportunities, whether by optimizing processes, reducing costs, or pioneering innovative solutions that streamline operations. My commitment to continuous learning and my adaptability have allowed me to collaborate effectively with cross-functional teams, ensuring that technical implementations are perfectly aligned with business objectives.

I share a lot of my code at my Github page

Responsibilities: I seek a role where I can contribute not only as a developer but also as a strategic partner in the value creation process of the company and its products.
Challenging projects: I am eager to tackle innovative, demanding projects that push the boundaries of what’s possible and further expand my expertise.
Teamwork: I value joining a collaborative team that is committed to both technical excellence and delivering high-quality solutions.
Mentorship and Collaboration: I appreciate opportunities for mutual learning, where both my peers and I can grow and innovate together.
Continuous learning: I am dedicated to staying abreast of emerging trends and technologies, ensuring that my work continues to drive progress and efficiency.

Contact me at: ruben@nexolabs.xyz or at my Linkedin

My best practices

⏺ My approach to best practices has evolved through years of hands-on experience across different domains:

Architecture & Design Patterns

At LIN3S I adopted Domain-Driven Design, CQRS, and Clean Architecture working on the Euskaltel project. These patterns became foundational — I've since applied them in Nixon (Python/FastAPI) with event-driven architecture, repository pattern, and
proper aggregate roots with domain events.

Infrastructure as Code & GitOps

I migrated from manual Docker deployments with Jenkins to a fully declarative GitOps workflow: Kubernetes on Talos Linux, ArgoCD with App-of-Apps, Helm charts, and automated CD pipelines. Every infrastructure change goes through Git — no manual interventions, no snowflake servers.

Testing

I follow the Testing Trophy approach: focusing on integration and E2E tests that provide real confidence, complemented by unit tests where domain logic is complex. In Nixon, this means async API tests with pytest, BDD features, and data factories with polyfactory.

Monorepo & Code Organization

I structure projects as monorepos with shared packages (pnpm workspaces + Turborepo), auto-generated types from OpenAPI schemas, and strict TypeScript — eliminating types and enforcing type safety across frontend and backend boundaries.

Secrets & Security

Secrets are never hardcoded or committed. I use Infisical with External Secrets Operator in Kubernetes and SOPS/Age for encrypted secrets in Git, ensuring secure and auditable secret management.