Staff Engineer (gn) - Data & AI Focus

๐Ÿข TQG ยท all TQG jobs
๐Ÿ“ Germany
๐Ÿ“… Posted 2026-07-18 ยท via Himalayas
๐Ÿท Data-Engineer,Technology-Leadership,Staff-Engineering,AI-Engineering,AI-Enablement,Software-Architecture,Staff-Data-Engineer,Staff-AI-Engineer,Staff-ML-Engineer,Staff-Applied-AI-Engineer,Sr.-Staff-AI-Engineer,Senior-AI-ML-Data-Engineer,Senior-AI-Data-Engineer
Apply on original site โ†—

Start: Immediately | Level: Staff | Location: remote, Germany | Working Hours: Full Time (40h/week)

Your next step in the Tech & Engineering team at ESN & More.

As Staff Engineer (gn) โ€“ AI Enablement , you will close the gap between AI potential and engineering reality. We have the platform, the tools, and the ambition โ€“ what we need is the person who sees where AI is changing how we build, drives that change without being asked, and makes it stick across teams. You work hands-on across our engineering organisation โ€“ enabling engineers to think and build with AI, leading our AI Community of Practice, and accelerating the shift to agent-driven workflows.

This is not a consulting role and it's not a ticket queue. You don't wait to be pointed at a problem. You find it, frame it, and start moving.

If you thrive on proactively identifying opportunities, moving teams forward through expertise rather than authority, and turning AI from a tool into a fundamental shift in how engineering works โ€“ this role is for you.

To ensure smooth collaboration, we require a current primary residence in Germany for this position.
Your mission

-
You identify AI opportunities across engineering before they appear on anyone's roadmap โ€“ and you drive them forward proactively, with or without a formal mandate

-
You lead our AI Community of Practice: you own the format, the cadence, the reusable playbooks and prompt libraries, and you measure whether engineers are actually working differently because of it

-
You accelerate the shift to agentic engineering by working hands-on with Claude Code, Codex, and n8n โ€“ building prototypes, sharing patterns, and helping teams move from AI-assisted to AI-driven workflows

-
You build reusable frameworks and experiment templates that multiply your impact: guides, decision frameworks, and best practices others can follow and improve on without needing you in the room

-
You co-shape AI strategy together with the Heads of Engineering and VP of Engineering โ€“ you are a key voice grounded in what's technically feasible and what engineers actually need, and you proactively surface the problems worth solving

-
You collaborate closely with our Cloud & Security team, which owns our enterprise AI platform (Codex and Claude Code via GDP Enterprise), to enable teams to use it well and to feed back what's missing

-
You work as part of a Staff Engineer team with different specialisations โ€“ you challenge each other, support across domains, and contribute your AI depth as the specialisation the team is currently missing

Your experience & skills

-
You are currently working at Staff level or equivalent and have demonstrable cross-team impact โ€“ not just within your own squad

-
You have solid, working knowledge of the modern AI toolkit โ€“ LLMs, prompt engineering, agentic frameworks, RAG, embeddings, and automation patterns โ€“ and you know when and why to use each. You don't need to have built all of it from scratch; you need the judgment to guide others through it and the credibility to be taken seriously when you do

-
Your personal AI practice is real: you use tools like Claude Code, Cursor, or Copilot not because you have to โ€“ because you can't imagine not using them. You've built workflows, pushed the limits, broken things, and learned from it. You can show your work

-
You have concrete experience enabling others: workshops, communities, documentation or guides that changed how a team actually works โ€“ you've moved people, not just written about moving them

-
Communication is one of your strongest skills: you explain complex AI concepts clearly to sceptical senior engineers, overwhelmed teams, and leadership who need the trade-offs without the implementation details

-
You know when AI is the wrong answer โ€“ you can make the case for keeping something deterministic, for stopping an experiment early, and for separating durable capability from compelling hype

-
You run experiments and kill what doesn't w

โ† All remote jobs