Erhalte mehr Antworten von Arbeitgebern
Versende in nur wenigen Minuten einen passgenauen Lebenslauf.
GTMBase is an AI-first GTM engineering and RevOps agency focused on building scalable CRM solutions for multiple clients. You will be embedded with RevOps teams, shaping HubSpot-driven processes and automation. The role blends architecture, automation, and client collaboration in a fast-moving environment.
The ideal candidate thrives on building clean CRM designs, is comfortable with APIs and data governance, and embraces AI-assisted workflows to deliver measurable improvements in GTM operations.
RevOps is changing fast, and so is the way GTM processes get built and maintained inside the CRM.This role puts you on the front edge of it: forward-deployed in our clients' RevOps teams, building ... Mehr anzeigen
We are a digital advertising partner for offline businesses - we support retailers in their marketing activities and help them find a new audience.Would you like to join and be a part of digitalisa... Mehr anzeigen
With our powdered drinks HOLY Energy®, HOLY Hydration®, HOLY Iced Tea®, and HOLY Milkshake® you get amazing taste across 50+ flavors while maintaining a good conscience—for your body & the envi... Mehr anzeigen
Reliable data, resilient services and scalable architectures are at the heart of every CRM interaction at idealo.GDPR compliance and supporting personalized user experiences.You'll influence how da... Mehr anzeigen
Zenjob is an AI-powered flexible staffing platform that has efficiently connected companies and temporary workers since 2015.Companies use our platform to book ready-to-work staff in real time, whi... Mehr anzeigen
RevOps is changing fast, and so is the way GTM processes get built and maintained inside the CRM. This role puts you on the front edge of it: forward-deployed in our clients' RevOps teams, building and running their GTM systems in a genuinely AI-first environment.
GTMBase is an AI-first GTM engineering and RevOps agency. We help post-PMF B2B companies (€8M to €50M ARR, 5+ reps) whose go-to-market is over-performing their systems. Reps do manually what should be automated, sales and marketing data doesn't connect, and leadership can't trust the reporting.
We combine strategic GTM thinking with hands-on technical build, and we fix the foundation before running campaigns.
We've done this for clients including Groupon, Blinkist, Booksy, and Sendify. We work in small pods, with a Strategist, a CRM Architect, and a GTM Engineer.
We run the company on Claude Code. It's our operating system: client context, playbooks, automations, and delivery all live in it, and AI is the default way we work rather than a bolt-on. You'll work this way too, and get very good at it.
You're the person who turns our GTM strategy into a CRM that actually works. Most clients run their entire revenue motion on HubSpot or Salesforce, and the quality of that system runs through this role: how clean the data is, how well leads route, whether leadership can trust the reporting.
Here, "Architect" means architecting inside the CRM: the object model, pipelines, workflows, and automations. The GTM and revenue strategy is set with you in your pod, not by you alone, and you build it with real craft.
You're forward-deployed: you embed with clients' RevOps and sales teams and build inside their live CRM.
You'll build and maintain GTM process and automation inside our clients' CRMs, mostly HubSpot. Working from the direction set in your pod, you turn requirements into a clean, well-built system the sales team can rely on.
One week you're building a client's lead lifecycle and routing. The next you're debugging a broken automation, untangling duplicate deals, or shipping a dashboard a CRO asked for. You move across several client instances at once without dropping threads.
You're a builder with an admin's discipline. You know the object model, not just the UI. You sweat the details others miss, you test before you ship, and you document what you build so the rest of the pod can run it. When something breaks, you find the root cause and fix it properly.
Your pod is you (CRM Architect), a Strategist who sets direction and hands you requirements, and a GTM Engineer. You and the GTM Engineer are both builders, but you own different layers:
Think of it as the data into the CRM (GTM Engineer) versus the system it lands in and the process the sales team runs on (you). You don't need to be a Clay or Apify expert. You just need a solid working understanding of what a GTM Engineer does, enough to spec what you need, integrate their output cleanly, and know what's possible.
Must-have
Nice-to-have