Who you are

- ? 5+ years of engineering experience, at least some of it in a SaaS startup or scale up

- ? You've owned a bug backlog, either for your squad, or for the entire engineering team at your previous company

- ? You debug code you didn't write, fast

- ? You think in systems and processes, not only individual tickets

- ? You've mentored or led at least 2 engineers. Management experience isn't required

- ? AI-native way of working. You already use AI daily, with good judgement and real productivity. Candidates who don't embrace AI are not a fit

- ? Fluent in Spanish and comfortable in English. We tend to speak Spanish at the office and in Slack, and write documentation and projects in English

What the job involves

- Right now, bug resolution at haddock is handled by a squad of two product engineers who rotate every month. It works, but it doesn't scale: twelve onboardings a year into the work that needs the most context, variable throughput month to month, and a backlog that goes down when we add people and back up when we take them away

- We're replacing that with a permanent Product Reliability Engineering team, and you'd be the first hire and the one who builds it. You'll lead two engineers plus a rotating seat from the product engineering team. This is a hands-on role where 75% of your time is expected to be spent doing software engineering work

- Conceptually, it's similar to a Support Engineering team, but so empowered with AI that we ambition going beyond "just fixing bugs", but actually creating the system and tooling to make haddock highly reliable and have issues quickly fixed

- Here's the part that matters most, and we want to be direct about it: your mission is not to close more tickets. It's to make the inflow shrink. A team that only drains a queue burns out. So this role comes with an explicit mandate, build solutions,



automations and processes that improve the reliability of the product. That's the deal
- The technical escalation layer. Triage, reproduction, diagnosis and resolution of everything escalated from our Customer Experience team

- Killing root causes. Moving from "this ticket" to "this class of ticket", and making the class go away

- Internal tooling for data correctness. Tools to fix data in bulk without hand-written SQL, and detection that catches incoherent data before the customer does
- The metrics and the weekly report, including where bugs come from and which squad shipped them. Quality accountability stays with the people who ship

- Two engineers, their onboarding and their growth, plus a rotating product engineer

- Our processes and tools are constantly improving, and everyone contributes to making them better

- ➡️ Example work

- Some example objectives you could be working towards in your first months:

- Managing the AI agents (like our Triager agent) that triage and fix tickets in the backlog, and creating new ones as needed to automate as much of the process as possible

- Fixing multiple issues per day, aided by swarms of AI agents that you direct with your experience, wisdom and principles

- Attacking proactively high-volume classes of problem that you detect, like a flaky connection to Square or data correctness issue with AI-digitalized documents

- Instrumenting real inflow and resolution metrics, like tickets per 100 accounts,



so we can prove the product is getting better and not just that we're running faster

- If you're excited by ownership, autonomy, and building technology that directly impacts real businesses every day, this is the right moment to join

- Come on board while we're still a startup. It's much more fun and motivating than joining an already established scale up or corporation where your role is very defined and limited!

- This is the first Product Reliability Engineering role at haddock. You'll set the triage policy, the severity model, the metrics and the standard. If you've been the escalation engineer inside a scale-up company and thought "I could run this function properly if it were mine", it can be

- You'll be close to the consequences. Our customers are restaurants, many of them in Barcelona, and when our data is wrong someone's margin is wrong. The feedback loop is short and real, and it's very rewarding to fix things for a restaurant you like

- Haddock is an AI-first company, and so is this role. You'll use AI daily to diagnose, to navigate systems, and to build tooling. A good chunk of our product runs on AI workflows, which means a good chunk of the failure modes you'll be diagnosing are new kinds of failure modes

The application process

- We usually respond within three days

- We move fast and communicate openly. Our goal is to wrap up the process within a week. Here's what to expect:

- Intro call with Guillermo (Head of Technology), 25 mins

- Call with Pol (co-founder), 25 mins

- Technical interview with Guillermo and another engineer in the team

- Call with Arnau (co-founder), 25 mins

- Sounds like an opportunity? Apply now. We'd love to meet you

- ? We answer all applications that include a personalized message or cover letter

Benefits

- Adaptable working hours

📌 Lead Software Engineer (Barcelona)
🏢 haddock
📍 Barcelona