
Principal Forward Deployed Engineer (EMEA)
Posted 25 days ago
The role in short
Embed with strategic customers to design, build, and ship production AI agents and integrations using Docker's platform, while driving adoption of secure agentic workflows.
About Docker
Docker is the platform at the center of how intelligent software gets built. For more than a decade, Docker has helped millions of developers and thousands of organizations build, ship, and run software consistently across any environment. Today, Docker extends that same trust to the AI era. Docker Hardened Images form the foundation agentic code is built on, local and cloud Docker Sandboxes isolate where agents run, and Docker AI Governance sets enterprise-wide policy. Together, they give builders and organizations the confidence to adopt any model, tool, or agent without compromising security, governance, or control.
_______________________________________________________________________
The Role
Docker Forward Deployed Engineers (FDE) embed directly with our most strategic customers to solve important, complex technical problems and turn ambitious ideas into production outcomes. FDEs take on the most challenging technical challenges using existing Docker products and patterns when possible, and work across customer, Docker Product and Engineering teams to realize new approaches when required.
As a Docker FDE, you will work side-by-side with customer engineering teams to deeply understand their goals, problems, constraints, and technical landscape; identify the highest-leverage opportunities; and design, build, and ship solutions with them. You own the technical journey from discovery and architecture through prototyping, implementation and production rollout.
The solutions you build may use existing Docker products, extend Docker into new environments, integrate deeply with customer and third-party systems, or reveal capabilities that Docker should build next. You work closely with Docker Solutions Architects to evolve existing patterns, and Docker Product and Engineering to turn new learnings into reusable patterns and product capabilities.
_______________________________________________________________________
Responsibilities
Build in Production with Customers
- Embed with customer engineering teams to design, build, and ship solutions from first prototype through stable production rollout. Use existing Docker products and patterns when possible, invent, prototype and validate innovative solutions when necessary.
- Deliver working technical artifacts to customers: custom MCP servers with tightly integrated Docker Sandbox environments for coding agents and containerized agents; Docker Compose definitions for multi-agent harnesses and model-backed applications; Hardened Image standardization and migration; New tools that unblock customer progress.
- Integrate Docker's AI platform with the customer's existing stack, including identity providers (OIDC/SAML/SSO), secrets management, private and air-gapped registries, Kubernetes, CI/CD pipelines, and observability tooling.
- Own technical delivery on your engagements: scope the work, sequence it, make trade-offs between speed and quality, remove blockers early, and contribute directly to code whenever progress depends on it.
Make AI Adoption Safe and Governable
- Translate customer security, compliance, and platform requirements into concrete plans and see those plans through from ideation to production.
- Help customers define controls to enable them to adopt agentic AI to solve their unique business problems without compromising security, compliance, data sovereignty or end-user experience.
- Establish quality and performance standards for customers and work closely with Docker Product and Engineering to quickly address issues that fall outside of established thresholds
- Partner with customer security and platform teams to get agentic workloads through architecture review, threat modeling, and change control.
Partner with Solutions Architecture and the Field
- Work closely with Solutions Architects to enable off-the-self solutions when possible and provide technical experience and leadership when a bespoke solution is necessary.
- Feed implementation learnings back into reference architectures, SOW templates, and success patterns so that FDE innovations become standard features and implementation patterns.
- Support the field with technical depth during proofs of concept, escalations, and expansion conversations when a working build is the fastest path to a customer adoption.
Close the Loop with Product and Engineering
- As part of Docker Engineering FDEs work closely with Product and Engineering teams to fold FDE innovations, learnings, and design patterns into existing or new products and services.
- Work with Customers, Product and Engineering to establish quality and performance thresholds, ensuring customer environments meet them consistently, and responding quickly and decisively when they don’t.
- Be the voice of the customer. Deliver data-driven and actionable feedback to Product and Engineering: what works well; what does not; what customers are asking for; and what blocks their adoption and forward progress. FDE experience directly influences the roadmap.
Shape the Practice
- Define the FDE engagement model, delivery standards, and quality bar, and codify them so that engagements are consistent across customers, regions, and delivery partners.
- Mentor and lead other Forward Deployed Engineers, and participate in hiring loops to grow the team.
- Act as the senior technical escalation point on the hardest problems impacting your customers. Every incident is an opportunity to improve Docker products and services.
- Maintain deep, current knowledge of the agentic AI stack: LLMs, APIs, MCP, coding agents, model and harness evaluation approaches, performance and quality thresholds, deployment patterns.
- This role may require participation in an on-call rotation to provide support outside of standard business hours, including evenings, weekends, and holidays, as needed.
_______________________________________________________________________
Qualifications
Required
- 10+ years of software engineering experience, including 4+ years in a customer-facing technical role such as Forward Deployed Engineer, Solutions Engineer, Professional Services Engineer, or Software Engineer with consulting or technical founder experience.
- Technical leadership across multiple engagements, teams, or domains, with a proven ability to set delivery standards, define repeatable patterns, and influence product direction through field evidence.
- Expert production coding skills in Go, Python, or TypeScript, with a track record of shipping and operating software that other people depend on and of leading technical design reviews.
- Deep, hands-on Docker expertise: Dockerfiles and multi-stage builds, Docker Compose, image and registry operations, container networking and storage, and container security fundamentals.
- Hands-on experience building with LLMs and agents in production, including tool use and function calling, the Model Context Protocol (MCP server and client implementation), prompt and context engineering, and evaluation of agent behavior.
- Working knowledge of software supply chain security: SBOMs, image signing and attestation, vulnerability management, minimal and hardened base images, and secure CI/CD.
- Experience integrating with enterprise systems: identity providers (Okta, Entra ID, LDAP/Active Directory), federated identity protocols (OIDC, SAML), secrets managers, Kubernetes, and at least one major cloud platform (AWS, Azure, GCP).
- Ability to scope and deliver complex work in ambiguous, fast-moving customer environments, making sound trade-offs between scope, speed, and quality.
- Excellent communication skills with engineers, security and platform teams, and executive stakeholders, with a low-ego, collaborative approach and the ability to lead through influence rather than authority.
- Proven track record of technical mentorship and of raising the bar for the engineers around you.
- High agency and comfort operating autonomously in distributed, remote-first teams.
- Bachelor's degree in Computer Science, Engineering, or a related field, or equivalent practical experience.
- Travel to customer sites to build in person with customer teams, estimated at up to 50%.
Bonus
- Experience with Docker Hardened Images, Docker Scout, MCP Gateway, MCP Toolkit, Docker Sandboxes, or Docker Model Runner.
- Experience deploying and operating coding agents (Claude Code, Codex, Gemini CLI, Cursor, or similar) in team or enterprise settings.
- Experience with air-gapped, regulated, or compliance-driven environments in financial services, healthcare, government, or similar sectors.
- Contributions to open source projects in the container, Kubernetes, or MCP ecosystems.
- Prior experience founding or scaling a Forward Deployed Engineering or Professional Services practice.
Visa sponsorship: Docker considers visa sponsorship on a case-by-case basis based on business needs.
_______________________________________________________________________
Compensation & Equity
All full-time roles include equity. Final compensation is determined on factors including but not limited to experience, skills, qualifications, and location.
Europe: €121K – €198K base
______________________________________________________________________
Posting Information
- Open vacancy: This posting is for an existing open role.
- AI in hiring: Docker may use AI-assisted tools during our recruiting process.
- Interview recordings: Candidates will be invited to opt in to interview recordings to support interviewer calibration and consistent evaluations. Recordings are optional and require explicit consent.
______________________________________________________________________
Perks & Benefits
- Remote-first by design – Work from your home, with offices in Seattle and Paris for connection and collaboration.
- Flexibility that fits your life – We trust you to manage your schedule while delivering great work.
- Time to recharge – Generous PTO, designated quarterly Whaleness Days, and a designated end-of-year Whaleness break.
- Home office support – Set up your workspace for comfort and success.
- Technology stipend – Equivalent to US$100 net per month to help support your work.
- Learning & development – Annual stipend for conferences, courses, certifications, and continued learning.
- Parental leave – 16 weeks of paid parental leave after six months of employment.
- Equity for all full-time employees – Share in Docker's long-term success as we continue to grow.
- Comprehensive benefits – Medical, retirement, and paid holidays vary by country.
- Docker swag – Because representing the whale never gets old.
Docker is proud to be an equal opportunity employer. We are committed to building a team that reflects a broad range of backgrounds, experiences, and perspectives. We believe diverse teams build better products, make better decisions, and better serve our global community.
#LI-REMOTE
Prep for this interview
5 questions likely to come up at Docker, Inc, each matched to a line in this posting.
- 1Coding
They wrote: “Expert production coding skills in Go, Python, or TypeScript, with a track record of shipping and operating software that other people depend on and of leading technical design reviews.”
Here's a CSV export from a customer. Write a script that cleans it and loads it into our API.
How to answer
Why they ask: Very close to real FDE work. They watch how you handle bad rows and failures.
- Read with a proper CSV parser; check the header first
- Validate each row and collect errors, not crash on the first one
- Send in batches with retries and a clear report at the end
- Write one or two quick tests for the parsing
Tip: Talk through edge cases out loud: encodings, missing fields, duplicates, rate limits.
- 2Cloud, deployment and security
They wrote: “Translate customer security, compliance, and platform requirements into concrete plans and see those plans through from ideation to production.”
The customer's security team sends a 200-question review. How do you handle it?
How to answer
Why they ask: Security reviews often block deals. FDEs help get through them.
- Start from your company's standard answers (SOC 2 report, past reviews)
- Answer clearly; don't oversell
- Bring in your security team for anything you're unsure of
- Keep the new answers for the next customer
Tip: Reuse past answers, flag honest gaps, and offer a call for the hard questions.
- 3Travel
They wrote: “Travel to customer sites to build in person with customer teams, estimated at up to 50%.”
How do you handle being on the road with customers for weeks at a time?
How to answer
Why they ask: Many FDE roles involve regular travel. They check you know what you're signing up for.
- Your past travel or on-site experience
- How you stay productive away from the team
- What travel level works for you, said plainly
Tip: Be honest about what works for you. A mismatch here hurts both sides later.
- 4Discovery and scoping
They wrote: “Own technical delivery on your engagements: scope the work, sequence it, make trade-offs between speed and quality, remove blockers early, and contribute directly to code whenever progress depends on it.”
How do you decide what to build first when a customer wants ten things?
How to answer
Why they ask: FDEs have limited weeks per customer. This tests judgment about value, effort and risk.
- Score each request by business value and by effort, with the customer in the room
- Pick one item that proves value fast and unblocks later work
- Write down what's out of scope so it doesn't creep back in
- Revisit the list after the first release, with real usage data
Tip: Show a simple way to rank the list and name what you'd leave out on purpose.
- 5Integrations and APIs
They wrote: “Maintain deep, current knowledge of the agentic AI stack: LLMs, APIs, MCP, coding agents, model and harness evaluation approaches, performance and quality thresholds, deployment patterns.”
Walk me through connecting our product to a customer's internal system that has no documentation.
How to answer
Why they ask: This happens weekly in the job. They want a calm, step-by-step method.
- Find who owns the system and get read access to a test environment
- Watch real traffic or logs to learn the data shapes
- Build a thin adapter with logging around every call
- Agree on how failures get reported, and who fixes what
Tip: Talk about finding the owner of the system first. The code is the easy part.
Not the one? Get the next one by email
New roles land here every day. Pick what you want to hear about.
Want the job, not just the posting? Learn how FDEs work.
FDE Info is our free weekly newsletter for forward deployed engineers: tools, field notes from real deployments, and how FDE teams hire and pay.
Free. One email a week. Unsubscribe in one click.