GTM Engineer

GTM Engineer — Berlin (Hybrid)

About emnify

emnify is a leading cloud-native IoT connectivity provider helping businesses connect and manage devices globally through a single, modern platform. Our technology powers connected products across industries including mobility, logistics, energy, healthcare, and security — enabling enterprises to scale IoT faster, more securely, and with greater flexibility.

Built for the cloud era, emnify combines global cellular connectivity, network intelligence, and seamless API integrations into one platform that simplifies how businesses deploy and manage connected devices worldwide.

With strong international growth and increasing momentum in the U.S. market, emnify is helping redefine what modern IoT connectivity looks like.

Your Role

This is a newly defined, full-time GTM Engineer role sitting within the Revenue Operations and Sales team in Berlin, reporting into Revenue Operations Lead. You will work day-to-day alongside a close-knit team of sales and operations professionals — and collaborate with the CRO and broader commercial leadership. Your core ownership is emnify's outbound engine and data enrichment infrastructure: building the automated flows, AI agents, and integrated systems that help the revenue team find, prioritise, and engage the right accounts faster and more intelligently.

Why emnify

emnify operates on a consumption-based model in a market — global IoT connectivity — that is still in its early innings of enterprise adoption, which means the GTM challenge here is genuinely complex and genuinely interesting. The company is profitable and growing, which gives you a stable platform to build from rather than a runway that is quietly ticking down. The go-to-market AI and automation infrastructure is still greenfield: a lot of the foundational work is yet to be done, which means real creative latitude and real visibility. You will be joining an experienced commercial team that is deeply bought into building this capability — leadership has done it before and knows what good looks like — and you will be part of a Berlin hub where you can collaborate in person rather than building in isolation.

Your Impact

Build and own emnify's lead enrichment infrastructure end-to-end — from signal sourcing through Clay, ZoomInfo, and first and second-party data providers, to clean, actionable data landing in Salesforce for the outbound team

Drive pipeline coverage improvement by deploying automated outbound workflows that surface the right accounts at the right time, connected across Salesforce, Amplemarket, and emnify's internal GTM platform

Develop AI agents using Claude and Clay that automate research, qualification signals, and personalisation at scale — turning hours of manual SDR work into reliable, repeatable flows

Own the integration layer between emnify's commercial stack — Salesforce, n8n, Attention, Weflow, Amplemarket, Sales Navigator — so data flows cleanly and the revenue team spends time selling, not fixing

Lead the build-out of emnify's company knowledge infrastructure , working toward a machine-readable, agent-accessible source of truth that keeps commercial processes documented and up to date automatically

What We Expect:

• A solid commercial foundation — you understand how leads move through a pipeline, what pipeline coverage actually means, why forecasting is hard in a consumption-based business, and why any of it matters for revenue

• Demonstrated experience building functioning enrichment flows — you have connected a CRM to data providers, built the logic, and shipped something that the sales team actually used

• Hands-on Clay experience — this is the core of the role and a genuine must-have; you should be able to walk us through a flow you have built in it

• Comfort with automation and integration tooling — n8n, Make, Zapier, or comparable; once you have worked with one, the others follow

• An AI-native approach to your work — you reach for Claude, agents, and LLM-powered tooling as a default, not an experiment

• Experience in a B2B environment — you understand the sales motion, the stakeholder dynamics, and why GTM tooling decisions have commercial consequences

• Confident enough to push back when a requested solution is the wrong one, and grounded enough to do it without making it a confrontation

• Coachability — we want someone who is excited to grow with us

Your First 6 Months

In your first few weeks, you will get hands-on with emnify's existing stack — Salesforce, n8n, Amplemarket, Attention, Clay — understand what has been built, where the gaps are, and where the biggest leverage sits for the outbound team. You will be spending time with the sales team to understand the commercial model, the ICP, and what good enrichment actually looks like for an IoT connectivity sale.

By month two or three, you will have shipped your first meaningful enrichment flow end-to-end — connecting signal sources to Salesforce, improving data quality for outbound, and showing measurable improvement in pipeline coverage. You will also have a clear view of where AI agents can start replacing manual steps in the research and qualification process.

By the halfway mark, you will own the enrichment and automation layer with real autonomy, be iterating based on what is working in the market, and have begun scoping emnify's company knowledge infrastructure — laying the groundwork for a system that keeps GTM processes accessible and up to date without constant manual upkeep.

Why It Might Not Be a Match

If you are most comfortable working from a detailed spec with clear requirements handed to you, this role will be frustrating — a significant part of the job is translating ambiguous commercial problems into something you can build, without a lot of hand-holding along the way

If you have built GTM tooling primarily inside large enterprises or implementation consultancies where security, governance, and process move slowly, the pace here will feel disorienting — emnify moves fast and expects you to ship before you have perfected the plan

If you are looking for a role where your output is measured by tickets closed rather than revenue outcomes, this is not the right fit — the team will expect you to care about whether the pipeline actually improved, not just whether the flow ran cleanly