Summary
✨ AI‑Generated
Join a high-impact GTM operations role focused on building the systems and processes that keep a sales development team supplied with qualified accounts, enriched contacts, and actionable intelligence. You will own automated sourcing and enrichment workflows, account qualification, CRM processes, sales tooling, playbooks, and performance improvement initiatives. Working closely with senior leadership in a lean environment, you will have significant ownership and the opportunity to see your work translate quickly into pipeline growth and operational efficiency. The role offers a path toward leadership in sales development, GTM operations, revenue operations, or strategic operations.
Highlights
High-impact role working closely with senior leadership, with broad ownership across lead generation, sales operations, automation, tooling, and performance improvement. The role offers strong career progression into sales development leadership, GTM operations, RevOps, or a strategic operations position, with measurable impact on pipeline and team efficiency.
Description
About the job
You'll sit next to simplyblock's founder and build the machine that feeds our SDR team.
Your job is to make sure that SDRs never run out of qualified accounts, enriched contacts, and intel that makes their outreach land.
You help us improve the scripts, playbook, tooling, performance management practices.
This role eventually grows into Head of Sales Development, Head of GTM Ops/RevOps, Chief of Staff.
We're selling private cloud storage infrastructure to some of the largest enterprises in the world.
Our team is small enough that your work shows up in company metrics within weeks.
Every project clears one bar: it creates pipeline, saves real hours, or kills something we shouldn't be doing.
🛠️ What you'll own
Lead sourcing & enrichment engine — build and run automated pipelines that feed SDRs with fresh, qualified leads: sourcing, enrichment waterfalls, dedupe, CRM push.
SDRs prospect; you make sure they never have to build listsAccount qualification & intel — score and prioritize accounts with real signals: OpenShift/Kubernetes footprint, storage vendors in use, hiring patterns, tech stack, triggers.
Every account an SDR touches comes with a "why now"Outbound infrastructure — sequences, deliverability, sender health, tool integrations.
Own the stack end-to-end: Apollo, Clay, Surfe/Hublead, HubSpot, SalesforgeGTM performance tracking — dashboards on what the SDR machine actually produces, flag what's off, push fixesTool evaluation & stack decisions — test, compare, recommend, implement.
You own the GTM stack, not just operate it.
You recommend tools after deep research and don't take decisions after "Claude Cowork chat".Call intelligence & playbook — listen to SDR calls and transcripts, find what converts, codify it into the playbook, track SDR performance against it and push fixes.
🤖 How we work
Claude-native by default.
You'll work with Claude across the whole stack — connectors, APIs, agents, Claude Code.
If a workflow can be automated, it gets automated; we'd rather build the tool than hire the headcountAnything you'd do twice becomes a skill, an agent, or a script that outlives the taskSpec before work: every task has a written deliverable and due date before it starts.
Unclear? Ask at assignment — questions after delivery don't countOutput is the measure.
Hours, effort, AI leverage — irrelevant.
What counts: does the output match the spec.
"The AI said so" doesn't fly; "here's the output, here's how I verified it" doesYou own your task list, your notes, your decision log.
Decisions from working sessions get logged same day — nobody chases you, and nobody takes notes for youConcise or it doesn't count: no long AI-generated documents, no screenshot dumps.
Easiest-to-digest form winsZero BS: no pointless meetings, no weekly 1:1 theater, no managers of managers
📈 Where this grows
We're building the US market from a standing start — the people who build it own it.
Depending on where you pull and what the company needs: GTM/RevOps lead, Chief of Staff, or owning a function outright.
None of these roles exist yet.
That's the point.
🧭 Who you are
Hands-on experience with Apollo, Clay, Surfe or Hublead, and HubSpot — this is a must, not a nice-to-have.
You've built enrichment waterfalls and lead flows that ran without you babysitting them1–2 years building GTM/sales automations at a startup, agency, or in a founding role of your own — n8n, make, webhooks, APIsYou think in systems: an SDR asking "where do my leads come from" should have a boring answer because you built the pipelineAI-native, not AI-curious: you already use Claude (or similar) daily and have shipped at least one automation that's still runningTop of your peer group: provable through something you've built, led, or shipped, not just gradesFluent English; German is a plus.
Berlin-based or ready to relocate asap.
🎁 What we offer
Direct access and full autonomy from day one.
Projects that would normally sit with someone five years more seniorA front-row seat to enterprise infrastructure GTM: our product runs in production at large international enterprises and we work with some of top-5 US banks, riding the VMware exodus and enterprise Kubernetes adoptionThe AI tooling budget to match a Claude-native company: Claude Max, Claude Code, and whatever else you can justifyCompetitive salary + equityA team that celebrates ambition and outstanding results.
No participation trophies.
If you'd rather build the machine than maintain one; apply.
