Go-to-market engineer (revops) - BONDR

Full-time · Amsterdam · start around 1 October

BONDR is a B2B go-to-market agency in Amsterdam, nine people. Three services, sold as one engine:

• Thought leadership. Founder-led LinkedIn content and Thought Leader Ads.
• GTM engineering. Signal scoring, enrichment and routing, built in Clay, landing in the client's CRM and Slack.
• Outbound. LinkedIn, email and phone cadences on the scored list, with BDRs following up until the meeting is booked.

We're good at this. That isn't the problem. The problem is that two people build the engineering side between everything else, we keep adding clients, and the list of things we want to test grows faster than the hours to test them.

So we're looking for someone who builds. All day. On real client engines.

Stack: Clay, Claude Code, HubSpot, n8n, HeyReach, Instantly, Apify.

What we think GTM engineering actually is. It’s named go-to-market for a reason. It runs across the whole bowtie: marketing, sales and customer success. Most of the category has parked itself in outbound. We're building out across all three, and that's the part you'd help build.

Content earns intent. Hiring, funding and new-in-role signals are available to anyone who pays for them. The ones actually worth acting on come from a client's own content, from people engaging with a real point of view. That's why thought leadership sits in the same engine, and it means you get to work with signals most GTM engineers never touch.

A lot of funnels, not one. We work with tech companies like AG5, Wyzetalk, Encompass, Workwize, and Co-Flo. Different ICP, different buyer, different data problem, every month. A KYC platform selling to compliance officers scores nothing like a skills-matrix tool selling to plant managers. In-house you learn one funnel deeply. Here you get to look inside a lot of kitchens and find out which parts generalize and which parts were luck.

Signal. ICP and persona definitions turned into something a machine can actually score across the buying journey. Lead scoring, qualification, routing logic. The build itself: tables, waterfalls, gates, tiering, and a cost per row that doesn't get silly. Then routing into HubSpot and Slack so a BDR knows what to do without opening anything.

Outbound. Campaign concepts and messaging angles, not just the plumbing under them. If you can't tell a good first line from a bad one, half this job stays closed to you. It’s fine if you don’t ace it yet; we will teach you. But you need to want to grow in it.

Experiments. Direct mail, email, LinkedIn, phone, and combinations nobody here has tried yet. Custom builds for one client's funnel that turn out to work for three. This is the part with the most room in it. Also the space where we’re growing beyond outbound/marketing work.

Charlotte owns integrations, HubSpot and automations. Aron lives in Clay. You'd build alongside both of them, and work with Mauk (founder) directly on what to try next. Plus you’ll work with our BDRs, Yuri and Giando, to make sure they focus on following up and booking meetings instead of doing manual work.

Mindset over tooling.

• You build constantly. Side projects, half-finished automations, things you made because the tool you wanted didn't exist.
• You're obsessed with AI in a practical way. Less "AGI by 2027", more "I wired this to that on Sunday and it saves four hours a week".
• Two systems that don't talk to each other bother you until they do.
• You'd rather run the experiment than win the argument about it.
• You're comfortable operationally. We're nine people. Some weeks are architecture, some weeks are fixing a list at 8 pm because a campaign goes out tomorrow.

Ideally you're hands-on in both Clay and Claude Code, with a real opinion about what each is for. Data problem or logic problem, and how fast you can tell the difference.

Nice, not required: HubSpot or another CRM, email infrastructure and domains, n8n, scraping. Missing pieces are fine, we'll teach you. No agency background needed either.

• Something market-tested to build on. We've been doing this for a few years, and it works. We're only now starting to scale it properly.
• Room. The processes exist, they're looser than they should be. That's the opportunity, not a warning. You'll shape how this gets done instead of inheriting someone's manual.
• A path, if you want it. This starts as a medior build role. If you're carrying client engines on your own after six months, we'll have the conversation about what comes next. Customer-facing, owning parts of the process, teamlead role etc.
• Real investment in your growth. Tools, courses, time to learn. Selfishly: everything you learn goes straight back into client work.
• A chance to work on your own personal brand. We build personal linkedin brands and want to incentivize BONDRs doing the same. We’ll teach you the same principles we use for our high-end founder clients, so you can build a true asset: your own personal brand.
• A nice office in Amsterdam, and the freedom to work remote when it suits.

Full-time, Amsterdam. €3,500 to €4,800 gross per month.

That's a wide range on purpose. Where you land depends on what you bring. The bottom is someone coming from RevOps, BDR or ops who's been teaching themselves Clay and Claude Code in their own time. The top is someone who's already built and run an automated signal layer across different campaigns, ICPs, and platforms.

Ideally based in Amsterdam. We’re a hybrid company, with most of the team remote. We’re building out the office culture and would love for you to join us.

If you're remote and genuinely strong, reach out anyway. We'd rather hear from you than not, and contractor arrangements work fine. Send your monthly or day rate.

Send a CV or a cover letter if you want to, we'll read it. But we're far more interested in what you've built.

So: send us something. A Loom, five minutes or so. Share your screen and walk us through one or two things you've made. The actual build, not a slide about the build. What it does, why you built it that way, what broke, and what you'd do differently now. A Clay table, an n8n flow, an agent, a scraper, a script that's ugly but useful. All of it counts.

Send it to [email protected]. If it's good, you'll hear within a few days; if it isn't, you'll still hear back