On-siteFull Time55k € - 65k € per yearPosted 21 days ago
About the role
We’re looking for a Frontend Tech Lead to help shape how frontend engineering evolves at Caravelo
This is a highly hands-on role. You will still build features and platform capabilities yourself, but your impact should go beyond the code you personally write
You will help define how frontend engineers work, how architectural decisions are made, how code is reviewed, how reusable foundations evolve, and how we keep the platform healthy as more teams and use cases build on top of it
You will join the Platform team, report to the CPTO and be part of Engineering Leadership
Ou will report to the CPTO and participate in Engineering Leadership. You will work closely with:
Frontend engineers across Product and Platform
Backend and Platform engineers
Product Managers
Designers
Professional Services
Engineering leadership
You will remain deeply involved in implementation. You will:
Build and improve shared frontend capabilities used across Caravelo
Help evolve the design system and component foundations together with Design and other frontend engineers
Improve the developer experience around local development, CI/CD, testing and deployment
Keep the current frontend architecture healthy as new features and product lines are added
Make pragmatic architectural decisions without introducing unnecessary complexity
The goal is not to redesign the frontend for the sake of it. The goal is to make sure what we already have becomes increasingly robust, understandable and scalable
You will help set the standard for how frontend engineering is done across Caravelo. That includes:
Defining and evolving architecture conventions
Facilitating RFCs and technical decision-making
Raising the quality and consistency of code reviews
Mentoring other frontend engineers and helping them become more autonomous
You will not need direct reports to have a large impact. You will lead through technical judgment, clarity, consistency and the quality of the foundations you help create
A frontend platform is only useful if teams can trust it. You will help strengthen:
E2E testing and regression coverage
Monitoring and alerting
Performance visibility
Production debugging and troubleshooting
Confidence in releases and changes
We want to move toward a frontend practice where failures are easier to detect, easier to understand and less likely to surprise us
Frontend work often crosses team boundaries. You will help improve:
Visibility into frontend work and technical decisions
Documentation of architecture, patterns and shared capabilities
Collaboration between Platform, Product and Professional Services
Knowledge sharing so engineers do not depend on a small number of people to move forward
Follow-up on architectural decisions so they become practice rather than one-off conversations
A good technical decision is only useful if the rest of the team understands it and can apply it
We actively use AI-assisted development at Caravelo. You will help make sure AI improves frontend engineering rather than fragmenting it. That means:
Using AI tools to accelerate implementation, testing, debugging and documentation
Encouraging reusable workflows and consistent patterns
Helping engineers review and challenge AI-generated code
Using specifications and clear technical intent to guide AI-assisted development
Preventing speed from becoming an excuse for duplication or poor engineering judgment
AI can make output cheaper. Your job is to help make sure judgment, ownership and maintainability remain strong
You are succeeding in this role when:
Frontend engineers can ship new features with less friction and stronger confidence
The frontend architecture remains coherent as the product grows
Shared components and the design system are actively reused and evolved rather than bypassed
Frontend work is easier to understand across teams because standards, documentation and decisions are visible
Reliability improves through stronger E2E coverage, monitoring, alerting and performance practices
Engineers become more autonomous and fewer frontend decisions depend on a small number of people
AI-assisted development increases speed without increasing architectural inconsistency
Future frontend initiatives can be evaluated pragmatically, without chasing trends for their own sake
Our frontend stack currently includes: Vue 3 · Nuxt 4 · TypeScript · Vitest · Reka UI · Turborepo
We run a monorepo, deliver the frontend as a full SPA through a CDN, and have decoupled deployment for assets and translations
Our CI/CD runs through GitLab pipelines
We are not looking for someone to arrive and replace the stack. We are looking for someone who can help us make it increasingly effective
This role can grow in several directions depending on your strengths and interests. You may deepen your impact as a technical leader, take on broader platform responsibilities, or shape larger future frontend initiatives as they emerge
Possible future areas include hybrid or native app experiences, further platform productization, and continued evolution of developer tooling and frontend reliability Benefits
Fun environment & company events
Tax-free benefits: Transport, food, gym and childcare
Flexible hours & Remote work options
Spacious office in the heart of Barcelona with free coffee & beer
Competitive salary & progression framework
We are looking for someone who can operate as an experienced Tech Lead today, or a strong Senior Frontend Engineer ready to grow into that scope
Experience improving reliability through testing, observability, performance work and production debugging
Pragmatic judgment: you know when to improve architecture, when to keep things simple and when not to build something at all
Experience leading technical decisions, architecture discussions and code review practices in a frontend environment
Ability to mentor other engineers, communicate technical decisions clearly and influence without relying on hierarchy
Deep experience with Vue 3 and its ecosystem
Strong professional experience building modern frontend applications, with excellent engineering fundamentals
You like mentoring, reviewing and helping other engineers improve
You ask whether something already exists, whether it belongs in the shared platform, and whether the next engineer will understand and reuse what you build
And you measure part of your impact by what the engineers around you are able to do without needing you in every conversation
You enjoy technical discussions, but you care more about turning decisions into conventions and reusable foundations than winning arguments
You still enjoy writing code, but your first instinct is not necessarily to write more of it
You like architecture, but you are not interested in architecture theatre
If you enjoy building frontend systems, improving the way engineers work and helping a team scale without turning the codebase into a maze, we’d like to hear from you
Experience with Nuxt meta-framework
Experience working with design systems and shared component libraries
Experience with monorepos, developer tooling and frontend CI/CD
Experience with Playwright, Vitest or similar testing frameworks
Experience with Datadog or similar monitoring and observability tools
Experience leading or shaping frontend practices across multiple teams
Our hiring process usually takes around 3–4 weeks from application to offer and includes five stages
Intro call
15–20 min
A short conversation with our People team to get to know you, understand what you’re looking for and introduce Caravelo and the role
Hiring Manager interview
30–45 min
A deeper conversation about your experience, technical leadership and the frontend challenges you would be helping us solve
Practical assessment
A short, role-specific exercise designed to understand how you approach frontend architecture, technical trade-offs and engineering quality
Team interview
45–60 min
Meet future colleagues to discuss your experience and assessment, explore technical decisions and understand how we would work together
Founder / leadership interview
30–45 min
A final conversation to align on expectations, ways of working and any remaining questions
We aim to keep the process practical, transparent and moving quickly
Apply and tell us about a frontend system, practice or architecture you helped make better for other engineers