Go-to-Market Engineer (FTE)

What this is about

At the customer, you are responsible for making sure that agents, workflows, automations and analytics run reliably and cleanly. Not “built at some point”, but every day in operation: the sequences send what they should. The workflows react to the right events. The agents make usable judgement calls. And the numbers in the reporting are correct.

To do that you monitor the systems, find and fix errors, measure the results and report them to the customer. You agree improvements with them and implement those. Building new setups is part of it: tables that research and score companies and contacts, sequences across email, LinkedIn and WhatsApp, workflows on real triggers. But the core of the role is the question of whether it runs cleanly at the customer and whether it moves the number: booked meetings and positive replies.

You need three things at once for this: you understand sales and know where a conversation breaks down. You have a feel for why one phrasing lands and the next does not. And you can find and fix errors in the system yourself, rather than describe them and hand them on.

CegTec is a GTM engineering partner for B2B brands in the DACH region. Profitable, bootstrapped, growing.

How we work

Every role at CegTec works with AI agents on the same principle:

1. Set the goal: You define what should be achieved, for example 20 qualified meetings a month.
2. Agents build: Agents do the work: research, data, drafts, routine.
3. Evaluate the result: You review what comes out and give clear feedback: good, not good, and why.
4. Iterate: The agents get better with every round until the goal is met.

That way your time goes where it matters: talking to people, meaning prospects, customers, partners and the team.

What you own

• Reliable operation at the customer. Agents, workflows, automations and analytics run cleanly, day after day. You are the person the customer calls when something is off, and ideally you are faster than they are.
• Monitoring and fixing errors. You spot outages, deviations and silent failures early (runs that hang, deliverability problems, wrong mappings, agents that miss), find the cause and fix it for good.
• Measuring and reporting. You read the numbers, interpret them honestly and tell the customer what works, what does not and why. The yardstick is meetings and positive replies, not features built.
• Improving with the customer. You propose changes to segment, copy, channels and flows, agree them with the customer, implement them and check whether the number moved.
• Building new setups. Tables with their columns and gates, sequences across several channels, workflows on real triggers, integrations with CRM, mailboxes, LinkedIn and third-party APIs. Whatever the customer already uses gets connected, not replaced.
• Copy as part of the system. Openers, salutations, variants. You write them yourself or get the agent to write them properly, and you check the result before it goes out.
• Deliverability and the gates. Unsubscribes, exclusion lists, sending windows, caps. The brakes are part of your work, not an obstacle to it.

What you explicitly do not do

New business sales stays with the founding team. The platform itself, its data model, interface and billing, is built by the product team. You manage nobody. Your field is the systems running at the customer and the results they produce.

Who you probably are

One of these three stories fits:

• You started in sales as an SDR, AE or in sales ops and taught yourself automation because the manual work annoyed you. Today you would rather build the system than work the list.
• You come from marketing ops or growth and realised the interesting levers sit behind the campaign: in the data, the enrichment, and what happens after the reply.
• You are a developer who worked on sales tooling in a B2B setting, close enough to the customer that you know why a meeting happens.

Requirements

• 2 to 4 years at the intersection of sales and engineering: GTM engineering, sales ops, RevOps, marketing ops or growth engineering
• At least one automation of your own that ran in production, with real recipients and numbers behind it
• You write outreach copy yourself and can explain why a variant lands
• Comfortable with APIs and data work: JSON, HTTP, webhooks, SQL basics, table logic
• Experience with at least one CRM at operator level (HubSpot, Salesforce or comparable)
• You work independently and dependably in a fast-changing environment and document what you build
• German at native level, English confident in daily work
• Living in or near Hamburg, regular presence in the office

Bonus

• Claude Code or comparable AI coding tools in daily use
• n8n, Clay, Instantly, Smartlead or a comparable stack
• Experience with LinkedIn or WhatsApp automation and its limits

What we offer

Cash

• €4,500 to €5,500 fixed per month, depending on experience
• KPI bonus on the numbers you influence: positive replies, meetings booked, system quality. Targets are agreed up front and can be recalculated.

Other

• Permanent employment with CegTec GmbH Hamburg, hybrid (Hamburg office + remote), living in or near Hamburg required
• Reporting directly to the CEO, no middle management
• A premium AI stack (Claude, n8n, HubSpot, Instantly, our own platform)
• You work on our own product, so what you build flows back into the platform

Selection process

Four steps over 4 to 6 weeks: intro call, a walkthrough of something you built, a practical task on a real case, then references and negotiation.

How to apply

Pitch by email to jobs@cegtec.net or on LinkedIn to Luca Ceglie. Bring two things:

• Three sentences. Which of the three stories fits, what interests you about the role, and what you would touch first.
• Something you built. An automation, a sequence, a workflow, a script. Show what it did, which numbers came out of it and what you changed as a result. A screenshot, a Loom (max 5 minutes) or one page of text, whichever format suits.

No cover letters.