Waylet

Knowledge

  export const Skills = {
    massiveImpact: "Building a product used by millions of people, with high criticality and a strong focus on scalability",
    backendRole: "Contributing to the design and development of backend services, ensuring performance and maintainability",
    closCollaboration: "Working closely with frontend, mobile, product and devops teams in an agile environment"
}

export const Tech = {
    languages: ["JavaScript", "TypeScript"],
    frameworks: ["ExpressJS", "NestJS", "Socket.io"],
    architecture: ["REST API", "Event-driven", "Domain-driven Design (DDD)"],
    databases: ["MongoDB", "Redis"],
    testing: ["Jest", "TDD", "Mocha"],
    tools: ["Lodash", "Luxon", "Axios", "Mailchimp", "Apidog"],
    devOps: ["AWS ECS", "Travis CI"],
    others: ["Swagger", "Real-time messaging", "Microservices"]
}

Experience

My journey through entrepreneurship — as a freelancer and as part of amazing startup teams — made it clear that, despite my deep passion for mobile development and how naturally it came to me, my drive to explore new tools and keep growing pushed me to take the leap into backend engineering.

Honestly, landing at Waylet could not have been a better decision. Joining as a Backend Engineer was a masterclass in what large-scale software development really looks like.

Waylet is a product well known across Spain, with millions of monthly active users and terabytes of data flowing through it — payment transactions alone exceeded 20 million movements per month. As you’d expect, a project at that scale demands extremely high technical standards, always focused on scalability, ensuring everything is thoroughly tested and bulletproof to keep serving users reliably around the clock — not just Waylet customers, but also various branches of Repsol that consume Waylet APIs for their own needs.

That environment pushed me to sharpen my thinking around mid-to-long-term technical strategies — because something that works today can become tomorrow’s bottleneck if it doesn’t scale well in terms of resources, costs, or reliability.

---

Resources

---