At Kentech, I’ve contributed to the development and maintenance of several frontend projects in a high-traffic environment. My responsibilities include working on architecture improvements, refactoring legacy code with a focus on maintainability, and writing technical documentation to support team knowledge sharing and reduce knowledge silos. I also handle technical spikes and collaborate regularly with other developers to improve workflows.

I’ve been actively encouraging the adoption of Test-Driven Development (TDD) across the team. Through pair programming and one-on-one support, I’ve helped make testing a more natural and consistent part of our workflow. As a result, test coverage in one of our key projects has increased significantly, leading to better code stability and confidence when refactoring. Additionally, I’ve supported the recruitment process by interviewing candidates and proposing a new technical test aimed at evaluating problem-solving and design skills more effectively.

At Triditive, I contributed remotely to the development of a platform designed to manage additive manufacturing workflows. During my time there, I supported various technical tasks and looked for opportunities to add value in a dynamic and rapidly evolving environment. Despite the short engagement, I remained committed to writing clean code, collaborating asynchronously, and documenting my work to support the broader team.

At Lean Mind, I worked remotely as part of multidisciplinary teams for various clients, contributing to products ranging from e-learning platforms to billing systems and audience intelligence tools. The company operates with a strong commitment to Software Craftsmanship and eXtreme Programming, which aligned deeply with my own values as a developer. Our work focused not just on delivering features, but on building maintainable, well-tested, and meaningful software.

I was involved in full-stack development using technologies such as Node.js, TypeScript, React, and occasionally PHP when maintaining legacy systems. I regularly practiced pair programming and Test-Driven Development (TDD), and helped guide architectural decisions with long-term sustainability in mind. In one of the projects, our team was able to deliver features to production with zero bug reports thanks to a robust testing strategy and a focus on simplicity. We also achieved significant performance improvements by optimizing data-heavy processes that previously took weeks to run, reducing them to a single day. Beyond client work, I mentored apprentices—one of whom later joined the company—and led internal training sessions to foster continuous learning within the team. Lean Mind’s culture of trust, feedback, and continuous learning made this one of the most enriching stages of my career.

After being promoted within Kentech, I took on broader responsibilities across both backend and frontend development. I would alternate between building backend services in Node.js or PHP, and implementing frontend features with frameworks like AngularJS and React depending on the team’s needs. I often collaborated closely with solution architects and team leaders to design scalable, practical solutions aligned with project goals.

During this time, I played an active role in modernizing our development practices. I introduced several tools and methodologies to the team, including TypeScript, NestJS, Storybook, Microfrontends, Cypress, Husky, and the creation of internal npm packages. These efforts contributed to a more cohesive and maintainable codebase, as well as improved testing and documentation standards. Beyond development, I also supported production deployments, maintained development environments, and helped interview and onboard new developers for both frontend and backend positions.

I was hired as a Backend Developer due to my interest and performance in Node.js tasks during my internship. In the first six months, my main tasks were coding new features on Node.js microservices, helping the infrastructure area and handling deployments on our environments before CI/CD came to our lives. That meant handling web servers with Nginx and pm2 processes for Node.js, besides handling all the files on servers for other services. Thankfully, some really smart teammates deployed Rancher with Docker connected with our Gitlab, giving us the chance to add CI/CD on our workflow.

During the following six months, I gradually stop working on infrastructure and started creating new features across all the stack. I also evangelized best practices about ES2017 Promises with async / await.

As part of my final year in the Web Application Development studies, I chose to do my internship at Kentech—one of the few companies in Gran Canaria working with Node.js at the time. It was also a great opportunity to practice professional English, as the company operated fully in that language.

I began as a QA tester for the company’s main web application, but soon earned the opportunity to take on development tasks. I worked on UI performance optimizations for Opera Mini and developed a custom WordPress theme for a corporate site. Toward the end of the internship, my mentor introduced me to their microservices architecture and challenged me to build a proof of concept for a distributed cache-locking mechanism using MySQL and Redis. That hands-on exposure sparked my interest in backend architecture and laid the foundation for my transition to a full-time backend role.

While I was in the middle of my Web Application Development studies I joined Cmas Digital, a two-person studio where I applied much of what I had learned in Mokaps about content, project flow, and client interaction. I also applied everything I was learning in my Web Application Development studies. It was a great opportunity to work and study in the same field at the same time. As the sole developer, I designed and built websites using WordPress, HTML5, and CSS3, created wireframes, and helped organize project information.

The role required a great deal of independence and initiative. My experience at Mokaps helped me transition smoothly into a more technical role, taking ownership of full web projects.

At Mokaps Studio, a small creative agency I co-founded, I led digital marketing efforts while gaining my first hands-on experience with web technologies. I planned and executed content strategies across multiple channels, managed online communities, and handled crisis communication when needed. As a copywriter, I was responsible for all blog content and also worked directly on websites, inserting and styling content using HTML and CSS.

Running a business also meant wearing many hats. I dealt with client relationships, product planning, budgeting, taxes, and day-to-day problem-solving. This experience gave me a broader perspective on digital products and sparked my interest in programming, which later became my full-time path.