Come catch bugs
with us.

We're building the AI that tests software the way a sharp colleague would: by understanding what the product is supposed to do. The ambition is to change how every software team ships. We raised €1.1M, we have customers, and we're hiring the people who'll build the thing, not inherit it.

The Holmes team laughing at their desks in the Ghent office
a regular Tuesday in Ghent
The Holmes meeting room behind a glass wall, with an orange armchair in front
where the whiteboard arguments happen
Founded
Feb 2026
and it's been a blur since
Raised
€1.1M
from people who've built this before
HQ
Ghent, BE
one room, everyone in it
Team
5
your desk would be number six

The people you'd sit next to.

No org chart, one room. Flip a card to get to know us.

?This spot is yours.we saved you a desk (and a hoodie)

The problem we can't stop thinking about.

Code is written faster than ever now, a lot of it with AI. Whether the product actually works the way users expect is a different story. Nobody builds a big QA team on day one, and every company hits the moment where manual testing starts holding them back.

That's the gap we're closing. It's a genuinely hard problem: agents that read a product, click through real UIs, decide what "broken" means, and get sharper with every release. We'd rather solve it with a handful of great people in one room than with a big org chart.

If you join now, you're not filling a slot. You'll make calls that shape the product and the company, together with everyone above.

— the Holmes team

Five things we actually do.

Not values on a poster. Habits you'd notice in your first week.

  1. 01

    Ship it, then make it better.

    A working version on Friday beats a perfect plan in a month. We'd rather learn from real usage than argue in a doc.

  2. 02

    Test your own work.

    We build a QA product. Shipping something we didn't check ourselves would be a little embarrassing.

  3. 03

    Budget over permission.

    Want to try a new model, tool or channel? You have the budget. Tell us what you learned, not what you're planning to ask.

  4. 04

    Same room, short loops.

    We work together in Ghent. Questions get answered across the table, not in a ticket three days later.

  5. 05

    Everyone sees everything.

    Numbers, customer calls, the pitch deck, the bank balance. Founding crew gets the full picture.

Honest check.

Saves us both an interview.

You'll love it here if…

  • you'd rather own a problem than a ticket
  • you like being close to customers and hearing what broke
  • you ship, look at what happened, and ship again
  • you want to be in the room when the big decisions get made
  • "we haven't figured that out yet" sounds exciting, not scary

Probably not for you if…

  • you're packing your bag at 16:59 so you're out the door at 17:00
  • you're looking for a clear ladder and a detailed spec
  • you want to work fully remote
  • you prefer a big team to hide in (there isn't one, yet)
  • you need things to be finished before anyone sees them

3 founding roles, all in Ghent.

Equity, a competitive salary, and your name on the early chapters.

psst: all three come with a hoodie

Holmes raised €1.1M and we're moving fast. We're looking for a founding engineer who wants to lay the technical foundation — not inherit it. You'll have full access to every major LLM provider and a real budget to experiment. No permission needed to try things.

About the role

Holmes autonomously tests applications by understanding what a product is supposed to do — no scripts, no manual maintenance. As our Founding AI Engineer, you build the core of that system: a multi-agent architecture that reasons about product intent, navigates real UIs, and gets sharper with every release. You shape the architecture, pick the models, and set the technical direction. What you build now is what Holmes runs on.

Responsibilities

  • Extend and improve our multi-agent system
  • Improve how our agents drive real browsers and mobile apps
  • Select and tune LLMs per agent and use case — balancing performance, cost, and latency across providers
  • Set up evaluations, benchmarks, and quality metrics
  • Co-shape the technical architecture and strategic direction of the product

Requirements

  • Deep understanding of how LLMs work: tokenization, context windows, sampling, and tool use
  • Hands-on experience with multiple LLM providers and a clear view of their trade-offs
  • Strong engineering fundamentals, whatever language you grew up in
  • Experience with agent systems, browser automation, or complex LLM pipelines
  • Self-directed and pragmatic — you ship without waiting for perfect conditions

Nice to have

  • Hands-on experience with browser or mobile automation
  • Background in QA, testing, or developer tools
  • Previous experience at an early-stage startup

What you get

  • Founding engineer title and real ownership — equity included
  • Access to all major LLM providers with budget to experiment freely
  • Direct line to the founders and full visibility into product and company decisions
  • Competitive salary at a well-funded, fast-moving company
Apply for Founding AI EngineerA short note and something you've built beats a polished CV.

Holmes raised €1.1M and we're moving fast. Every test our agent runs depends on infrastructure that needs to be reliable, fast, and built to scale. You build that infrastructure — from the ground up.

About the role

Holmes plugs into a team's CI/CD pipeline and autonomously tests their application on every release. That means our backend needs to orchestrate browser agents running in the cloud, stream real-time events back to the UI, and stay rock solid under pressure. As our Founding Backend Engineer, you own that layer — the APIs, the job system, the data pipelines, the integrations. What you build now becomes the foundation everything else runs on.

Responsibilities

  • Build and maintain the API layer connecting Holmes to customer platforms and CI/CD systems
  • Design data pipelines for storing, processing, and feeding back test results to the agents
  • Own reliability, scalability, and observability of the backend from day one
  • Extend the job system and event bus that power real-time run updates
  • Build webhook and event integrations for GitHub, GitLab, Slack, Jira, Linear and others
  • Co-shape the technical architecture as the product and customer base grow

Requirements

  • Strong backend experience and a solid grip on relational databases
  • Solid grasp of API design and real-time communication
  • Comfortable with async, queue-based, and event-driven systems
  • Experience running production systems on a modern cloud platform
  • You think in systems, not just functions — and you write code others can maintain and extend
  • Self-directed and pragmatic — you make decisions without waiting for perfect specs

Nice to have

  • Familiarity with browser automation or LLM agent orchestration
  • Experience integrating with developer tools or CI/CD platforms
  • Background in QA, testing infrastructure, or observability tooling
  • Previous experience at an early-stage startup

What you get

  • Founding engineer title and real ownership — equity included
  • Direct line to the founders and full visibility into product and company decisions
  • The freedom to make real architectural calls — no legacy, no bureaucracy
  • Competitive salary at a well-funded, fast-moving company
Apply for Founding Backend EngineerA short note and something you've built beats a polished CV.

Holmes raised €1.1M and we're moving fast. There's no marketing playbook yet — you write it. You'll work directly with the founders, talk to customers daily, and own the full funnel from day one.

About the role

Holmes autonomously tests software so engineering teams can ship faster without breaking things. We have the product, the funding, and early traction. What we need now is someone who can build the engine that turns interest into pipeline. This is a founding role — you're not inheriting a strategy, you're defining one. ICP, messaging, channels, outbound, content: all yours to shape.

Responsibilities

  • Define and sharpen our ICP — know exactly who we're selling to and why they buy
  • Craft messaging that lands with engineering leads, CTOs, and heads of QA
  • Be where our ICP is — show up in the right communities, channels, and conversations
  • Own outbound from scratch — sequences, targeting, copy, iteration
  • Set up and run our demand gen engine across social, content, and paid
  • Work closely with the founders on positioning, pitch materials, and deal support
  • Track what works, kill what doesn't, and scale what does

Requirements

  • 3–5 years in B2B SaaS marketing or growth — early-stage experience is a strong plus
  • You understand the developer and engineering buyer: how they think, where they hang out, what they ignore
  • You can build and test messaging fast — sharp positioning instinct, strong pen
  • Hands-on with a CRM and modern outbound tooling
  • You're comfortable without a playbook — you build structure from ambiguity
  • Bias to action: you'd rather ship a campaign and learn than wait for perfect

Nice to have

  • Experience selling or marketing to engineering, DevOps, or QA teams
  • Background in developer tools, CI/CD, or testing infrastructure
  • Previous experience at an early-stage startup

What you get

  • Founding title and real ownership — equity included
  • Direct access to founders and full context on every deal and decision
  • Budget to test channels, tools, and campaigns without bureaucracy
  • Competitive salary at a well-funded, fast-moving company
Apply for Founding GTM MarketerA short note and something you've built beats a polished CV.

No mystery, no seven rounds.

Here's the whole process, and who you'll meet at each step.

  1. 01

    Say hi

    Send a short note and something you've built. No cover-letter theatre.

    Robbrecht
  2. 02

    Coffee or a call

    An hour to get to know each other. You ask as many questions as we do.

    Robin & Robbrecht
  3. 03

    Work on a real problem

    A hands-on session on something we're actually stuck on, with the people you'd work with every day.

    The team
  4. 04

    Offer

    Salary, equity and a start date, in one conversation. Then we order your hoodie.

    Robin & Robbrecht
Robbrecht sitting in the study
reads every one. really.

Don't see your role? Write us anyway.

Tell us what you've shipped, why this problem gets you out of bed, and what you'd take off our plate. Robbrecht reads every message himself.

Say hi