We’re building something new. Here’s what that looks like from the inside.

The team, how we work, and what to expect if you join us.

See open rolesHiring in London, Antwerp and New York
The Conveo team gathered on a beach, arms raised for a group photo.

About Conveo

Conveo’s AI moderator interviews real people, and those interviews compound into a queryable understanding layer: research-grade, and available to every team rather than locked in a deck. The customers are enterprises behind leading global brands, running thousands of conversations a year across dozens of markets.

The model is research as infrastructure rather than one-off studies. Always-on programmes run continuously — brand trackers, category pulse, usage and attitudes — and when a pattern emerges, a focused deep-dive study answers it in days. Every study feeds the same knowledge layer, so teams build on what the organisation already knows instead of starting from scratch. Studies end; customer understanding shouldn’t.

That shape is what makes the engineering interesting. A knowledge layer that organises itself, never researches the same thing twice and still reads as current is something you build rather than buy. Put quantitative methods under an AI moderator on top of it — MaxDiff, Van Westendorp, Gabor-Granger, conjoint — and there is no playbook for most of what we ship.

Engineers around a table at a Conveo offsite, laptops open mid-discussion.

The Conveo journey

Apr 2024

Founded in Antwerp, Belgium.

Jun 2024

Accepted into Y Combinator S24. First version of the product built.

Feb 2025

$5.3M seed led by 6 Degrees Capital. Team grows to about 12 people.

Mar 2026

$50M Series A led by DST Global, with YC, Balderton and Visionaries.

Jul 2026

StoryLines launched. Always-on consumer intelligence at enterprise scale.

Today

About 85 people across NYC, SF, London and Antwerp.

The product engineering team

The team is small and growing quickly. Everyone holds the same engineering role, so any engineer can own any part of the app. We have engineering leads who wear a bit of a product management hat: they help guide work along and support with hiring, but they’re still hands-on engineers.

Dieter, our CEO, is deeply technical and stays involved in the technical decisions. He’s ex-CTO at DataCamp. Maarten is our CTO, also ex-DataCamp. We have a lot of product engineering horsepower at the leadership level, and that shapes how the whole team operates. 💪

Seven of the team on a London rooftop terrace, the BT Tower behind them and yellow café chairs in the foreground.Engineers around a large round table mid-discussion, laptops, notebooks and coffee cups between them.The team gathered in a bright room listening to someone present, two colleagues framing the shot in the foreground.A group selfie in front of Tower Bridge in London on a bright day.

Engineering culture, with Dieter and Maarten

Our CEO and CTO on what it's like to build here. The longest of the set — worth it if you want the unedited version of how the two of them think about building here.

Hear it right from the team

Four conversations with Craig and Irene: on what it’s like to build with AI, what it means to work without a product management layer, what the team is actually like day to day, and why they joined in the first place.

Building with AI

3 min

Irene and Craig on what using AI at Conveo actually looks like, and how it compares to where they've worked before.

Working without a PM

3 min

What it means to own decisions directly, and why that changes how you build.

What it's like to be on the team

4 min

Craig and Irene on the day-to-day — the culture, the pace, and what makes this team different.

Why they said yes

5 min

What made Craig and Irene say yes, and what they'd tell someone considering it now.

What we value, and what we don't

What we value

  • Outcomes, not effort, not presence, not politics.
  • Good judgment, especially in ambiguous situations.
  • Range: people who do adjacent jobs when needed.
  • Low drama: interpersonal friction costs.
  • Long-term commitment: we operate with people we expect to be here in four years.

What we don’t

  • Hours visible in the office.
  • Being the loudest voice in the meeting.
  • Political skill that doesn't translate into outcomes.

How we work

No layers between engineers and customers

Engineers join customer conversations directly. You hear the problem first, no summaries, no request queues. You ask follow-up questions yourself.

Close to go-to-market

You work directly with sales, research, CS, and operations. They tell you what's blocking a deal. You tell them what's realistic and by when.

Ship as soon as it works

Product updates go into Slack as soon as there's something to show, polished or not. Friday demos happen every week at a company-wide meeting.

Bug duty rotates

One engineer takes bug duty each week so the rest of the team stays focused. It never lands on the same person twice in a row. If something serious breaks, it stops being one person's problem.

Short planning cycles

Daily standups Mon to Thu. Triage twice a week. Retros every other week. Planning every Friday, where we set work for the next week.

Our hiring process

First interview to offer takes around 30 days. The thing that usually slows us down is finding availability. If you need to move faster, tell us. We’ll match your urgency.

  1. Talent team call

    30 min

    You'll speak with someone from our talent team. They'll give you an honest rundown of where we are and where we're headed. Your chance to ask anything.

  2. Team fit call

    30 min

    Meet one of our engineering leads. They'll learn about how you work, dig into past projects, and tell you more about how the team operates day-to-day.

  3. Technical assessment

    45 min

    A session covering your experience with React and TypeScript, and other relevant technologies.

  4. Coding challenge

    1 to 2 hours

    Pick up an issue, get familiar with some tools we use, ship to a mergeable PR. Bring whatever AI tools you want. We're measuring how well you direct AI to own an outcome, not whether you can code without it.

  5. Co-founder meeting

    You'll meet Dieter and Hendrik, our co-founders. Everyone meets them during the process. They've worked hard to build Conveo's culture and everyone here is responsible for carrying it forward. Come with questions: this is your chance for one on one time with the people who started Conveo, so ask them anything. If you haven't met Maarten, our CTO, earlier in the process, we'll set up a call with him during this round too.

  6. References

    We like to speak to two former managers before making any formal offer. After the coding challenge, start thinking about who yours will be. We can't extend a formal offer until these are complete.

  7. Offer

    If it's a match, we move fast. 🚀

We’re hiring product engineers in London, Antwerp and New York.

See open rolesFirst interview to offer, about 30 days

Questions at any point in the process? Ask Meredith or Joanna directly.