> Markdown version of [/jobs/ext/2158617-founding-gtm-engineer](https://www.wearedevelopers.com/jobs/ext/2158617-founding-gtm-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Founding GTM Engineer - **Company:** PLATO AG - **Location:** Berlin, Germany - **Contract:** Permanent contract - **Skills:** Artificial Intelligence, Data Structures, Large Language Models, Prompt Engineering, Hubspot - **Published:** August 21, 2026 - **Apply:** https://www.adzuna.de/details/5848388373 ## About the Role Must-haves: * Hands-on experience architecting a CRM like HubSpot from the ground up - how objects, properties, and data structure are set up - not just administering one that's already built * Practical, production experience with outbound/enrichment tooling (e.g. Clay or similar) * You've built with AI/LLMs - prompt design, agents, or AI-powered workflows - in real production work * Strong data rigor: you can read a funnel, spot where the data is dirty, and quantify the impact of a fix before you build it * You think in systems and sequencing, not tickets - and can defend your reasoning under real pushback Nice-to-haves: * Experience as an early GTM-Ops/RevOps hire at another startup * Familiarity with our stack or similar: Grain, Sales Navigator-style outbound tooling * Comfort with unit economics (CAC, ACV, payback) * Experience with mid-market, multi-stakeholder B2B deal cycles ## Description We're looking for Plato's first GTM Engineer: the person who brings RevOps to Plato as a discipline and builds our revenue engine as a product, not a ticket queue. Pipeline, conversion, and revenue per headcount are your metrics. You're inheriting real infrastructure - HubSpot as our source of truth, a custom-built deal-scoring app, call intelligence via Grain, and company-wide AI access - but the layers underneath are still unbuilt: clean data, automated process, real forecasting rigor, AI-driven workflows. That's the job. This is a team-of-one role that's essentially a sandbox: a direct line to the founders, a mandate to change how we work, and no playbook telling you what to build first. If you want to build the infrastructure behind a revenue engine from the ground up and see your own builds move real numbers, let's talk. What you'll actually do: * Get the data foundation trustworthy: CRM hygiene, field governance, deduping, enrichment on create * Automate the revenue process: lead routing, SLAs, stage criteria, clean handoffs across teams * Build the pipeline generation stack: signal-based outbound (ICP scoring, enrichment waterfalls, orchestration) so effort goes into conversations, not list-building * Bring AI into daily workflows: call-intelligence automation, research agents, health/churn scoring * Get forecasting and reporting to a place leadership can steer from weekly * Make sure what you ship gets used: instrument adoption, train the team, iterate, You'd be Plato's first-ever GTM Engineer - not inheriting someone else's system, but building the one that doesn't exist yet, and introducing RevOps as a discipline at a company that's never had one. A direct line to the founders, real budget for tooling, and a mandate to change how the revenue team works, from day one. This is an individual contributor role today - you'll be doing the building yourself, not managing a team. If this function grows as Plato scales, you'd be the one shaping what it becomes, not stepping into a structure someone else already defined. Because the function touches everything - data, process, automation, AI - you won't be boxed into one lane. If you want to see your own build move a real number within your first 90 days, this is that role. ## Related Videos - [Marketing x Product: How We Stopped Gaslighting Each Other and Built AI Products That Actually Work](https://www.wearedevelopers.com/videos/100244-marketing-x-product-how-we-stopped-gaslighting-each-other-and-built-ai-products-that-actually-work) - [Same Words, Different Worlds: Who's in Control?](https://www.wearedevelopers.com/videos/2071-same-words-different-worlds-who-s-in-control) - [Phel, a native Lisp for PHP](https://www.wearedevelopers.com/videos/791-phel-a-native-lisp-for-php) - [Integrate your Cognitive Assistant with 3rd-party DBs and software](https://www.wearedevelopers.com/videos/249-integrate-your-cognitive-assistant-with-3rd-party-dbs-and-software) - [The Intent Engineer: Closing the Gap Between Business & Engineering - Manuel Klein](https://www.wearedevelopers.com/videos/1855-the-intent-engineer-closing-the-gap-between-business-engineering-manuel-klein) - [WeAreDevelopers LIVE - Markdown, Liquid and Checkouts](https://www.wearedevelopers.com/videos/1814-wearedevelopers-live-markdown-liquid-and-checkouts) ## Related Articles - [The Prompt Engineer ✍️](https://www.wearedevelopers.com/magazine/216-the-prompt-engineer) - [The Biggest German Tech Companies](https://www.wearedevelopers.com/magazine/424-the-biggest-german-tech-companies) - [The Best X (Twitter) Accounts for Developers](https://www.wearedevelopers.com/magazine/294-the-best-x-twitter-accounts-for-developers) - [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers) - [Graph and AI Trends 2026: Why Is AI Running but Not Yet Delivering?](https://www.wearedevelopers.com/magazine/680-graph-and-ai-trends-2026-why-is-ai-running-but-not-yet-delivering) - [How We Built a Worry-Free System That Runs for 10+ Years – And What We’d Do Again](https://www.wearedevelopers.com/magazine/751-how-we-built-a-worry-free-system-that-runs-for-10-years-and-what-we-d-do-again)