Kong
Kong5 open roles

Forward Deployed Engineer, AI Gateway EMEA

England, UKOn-siteSeniorFull-time

Posted 16 days ago

The role in short

Embed with EMEA enterprise customers to design and build production-grade AI gateway integrations, agent workflows, and secure API architectures.

Are you ready to unlock intelligence?

If you don’t think you meet all of the criteria below but are still interested in the job, please apply. Nobody checks every box - we’re looking for candidates that are particularly strong in a few areas, and have some interest and capabilities in others.

About the Role:

If you don't think you meet all of the criteria below but are still interested in the job, please apply. Nobody checks every box - we're looking for candidates that are particularly strong in a few areas, and have some interest and capabilities in others.

You'll make our customers' first strategic AI use case work securely, in production, in their real environment. Not a demo. Not a proof-of-concept that quietly dies. Real traffic, real identity, real policy.

As a Forward-Deployed Engineer in EMEA, you'll sit with platform, security and engineering teams at some of the region's most important enterprises, and own the technical path from first discovery call to a workload that's actually running. You're a builder with enterprise architecture instincts, credible with staff engineers and security architects, and comfortable owning ambiguity across APIs, AI Gateway, agents, MCP, identity and policy.

This is not a demo-only SE role, and it's not a ticket-based implementation consultancy. You own technical success for strategic AI opportunities end to end, then take what you learn back into Kong's own engineering team to make the next deal faster.

What You'll Do:

  • Lead AI, API and agentic technical discovery with customer platform, security and engineering teams.
  • Design runtime architecture across models, APIs, MCP and tool access, identity and policy.
  • Build prototypes, integrations, evaluation flows and reference implementations that prove Kong governs real production traffic.
  • Remove blockers in pilot and production: auth, network, observability, latency and cost.
  • Own the technical path from pilot to paid, and stay on it until the workload is running.
  • Turn what you build into reusable patterns, so the next AI Gateway deal is faster and cheaper to win.
  • Spend regular time embedded with Kong's internal engineering team, pairing on AI Gateway and agentic roadmap work.
  • Feed field patterns and roadmap-critical requirements straight back to Product, before competitors define the narrative.
  • Partner with Sales, Solutions Engineering and Customer Success across EMEA on strategic AI opportunities.

What You'll Bring:

  • Strong hands-on engineering background, with experience building and shipping production software (Go, Python, TypeScript or similar).
  • Experience in a customer-facing technical role such as forward-deployed, solutions architecture, staff or principal engineering, or technical consulting.
  • Enterprise architecture instincts: you can design for identity, network, security and observability constraints in complex environments.
  • Production experience with LLMs and agents, with deep understanding of agent development frameworks and AI engineering principles, including model selection and routing, prompt and context design, tool calling, retrieval, testing and evaluation, and cost, latency and reliability trade-offs
  • Experience with API gateways or infrastructure: Kubernetes, service mesh, OAuth/OIDC, mTLS, policy enforcement.
  • Credibility with staff engineers and security architects. You can lead a technical discussion from whiteboard to working code.
  • You own outcomes, not tickets. You're comfortable with ambiguity and drive work to done.
  • Hands-on experience with MCP, including building or deploying MCP servers, and a clear understanding of how agents discover and call tools, how identity flows through those calls, and how tool access is secured
  • Strong written and verbal communication in English; additional European languages are a plus.
  • Willingness to travel to customer sites across EMEA as needed.

Bonus points

  • Prior experience at an AI-native, developer-platform or infrastructure company.
  • Experience with Kong Gateway, Konnect or other API management platforms.
  • Open source contributions, or a track record of publishing reference architectures or patterns.

#LI-JF1

About Kong:

Kong Inc., the AI Connectivity Company, is building the connectivity layer of AI. Trusted by the Fortune 500® and AI-native startups alike, Kong’s unified API and AI platform enables organizations to secure, manage, accelerate, govern, and monetize the flow of intelligence across APIs and AI traffic — on any model, any cloud. For more information, visit www.konghq.com.

Prep for this interview

5 questions likely to come up at Kong, each matched to a line in this posting.

  1. 1Coding
    They wrote: “Strong hands-on engineering background, with experience building and shipping production software (Go, Python, TypeScript or similar).”

    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.

    1. Read with a proper CSV parser; check the header first
    2. Validate each row and collect errors, not crash on the first one
    3. Send in batches with retries and a clear report at the end
    4. Write one or two quick tests for the parsing

    Tip: Talk through edge cases out loud: encodings, missing fields, duplicates, rate limits.

  2. 2Integrations and APIs
    They wrote: “Experience with API gateways or infrastructure: Kubernetes, service mesh, OAuth/OIDC, mTLS, policy enforcement.”

    How would you set up single sign-on for a large customer?

    How to answer

    Why they ask: SSO (SAML or OAuth/OIDC) is a common first task in enterprise deals and a common source of delays.

    1. Confirm their identity provider (Okta, Entra ID, Google) and protocol
    2. Exchange metadata and test in a staging tenant first
    3. Map user groups to roles in your product
    4. Plan for user removal: what happens when someone leaves the company

    Tip: Mention the people involved, and the protocol second. The customer's identity team usually controls the timeline.

  3. 3Travel
    They wrote: “Willingness to travel to customer sites across EMEA as needed.”

    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.

    1. Your past travel or on-site experience
    2. How you stay productive away from the team
    3. What travel level works for you, said plainly

    Tip: Be honest about what works for you. A mismatch here hurts both sides later.

  4. 4Discovery and scoping
    They wrote: “Lead AI, API and agentic technical discovery with customer platform, security and engineering teams.”

    A customer says “we want AI in our claims process.” What do you ask in the first meeting?

    How to answer

    Why they ask: Most FDE work starts this vague. They want to hear you find the real problem before you pick a tool.

    1. Map the current process: who touches a claim, in what order, with which systems
    2. Find the slowest or most error-prone step and ask what it costs them
    3. Agree on one measurable goal (for example time per claim, or error rate)
    4. Ask what data you can access, and who signs off on security

    Tip: Ask about the work, not the technology. Who does it today, how long it takes, what a mistake costs, and how they'd know it got better.

  5. 5LLMs, RAG and agents
    They wrote: “Spend regular time embedded with Kong's internal engineering team, pairing on AI Gateway and agentic roadmap work.”

    When would you use an agent that takes actions, and how do you keep it safe?

    How to answer

    Why they ask: Agent work is growing fast in FDE postings. Senior candidates are expected to know where agents fail.

    1. Use agents for multi-step tasks with clear success checks; avoid them where one wrong action is costly
    2. Give the agent narrow tools and permissions, not broad access
    3. Require human approval for risky actions
    4. Log every step so the customer can audit it

    Tip: Start from the cost of a wrong action. Limit what the agent can do, and log everything.

Not the one? Get the next one by email

New roles land here every day. Pick what you want to hear about.

FDE Info

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.

More at Kong

Similar roles at other companies

Kong

On-site

Apply