Founding GTM Engineer

Platoapp · Berlinjunior

En corto

▸Ingeniero GTM fundador que construye desde cero el motor de revenue de Plato.
▸Day-to-day: mejora de datos en HubSpot, automatización de procesos, IA en workflows y forecasting confiable.
▸Destacado: eres el primer GTM Engineer, tienes libertad para definir lo que se construye y ver impacto real en 90 días.

En ~1 minuto te damos: quién te entrevista, las preguntas probables con respuestas desde tu CV, y tu CV adaptado a esta vacante. Gratis, sin tarjeta.

🎧¿Llegás a la entrevista? Llevá el copiloto. Nuestra extensión escucha la entrevista en vivo y te muestra anclas de 3-4 palabras desde tu CV y tu preparación — mirás, conectás, hablás. Gratis. Ver la extensión →

¿Qué piden?

✓Experiencia práctica arquitectando HubSpot desde cero (objetos, propiedades, estructura de datos)
✓Experiencia en herramientas de outbound/enriquecimiento (ej. Clay)
✓Construcción de workflows con IA/LLMs en entornos productivos
✓Rigor en datos: análisis de funnel, detección de datos corruptos, medición de impacto
✓Pensamiento sistémico y secuencial, no centrado en tickets
✓Capacidad de defender decisiones bajo presión

¿No cumplís todo? Es lo normal — tu dossier gratis te dice qué gaps tenés y cómo cubrirlos en la entrevista.

HubSpotGrainClaySales NavigatorAI/LLMsprompt designagentsenrichment waterfallsorchestrationforecasting

¿A quién escribirle en Platoapp?

Tu dossier gratis identifica a las personas que te entrevistarían — con su background, qué valoran y cómo escribirles para destacar antes de aplicar.

Your responsibilities 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. 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 Why us? 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.

No apliques sin prepararte

Investigamos quién te entrevista, adaptamos tu CV y te ensayamos en vivo — gratis la primera.