Whippy
Whippy4 open roles

Forward Deployed Engineer

Dublin, IrelandOn-siteMidFull-time

Posted 23 days ago

The role in short

Embed with enterprise customers to design, implement, and debug production-grade integrations between Whippy's AI contact center platform and external systems like CRMs and telephony providers.

Dublin, Ireland | On-site
Full-time

Overview

Experience Required: 2+ years in software engineering, technical consulting, or a customer-facing engineering role
Education: Degree in Mathematics, Engineering, Computer Science, or equivalent practical experience

About Whippy

Whippy is an AI-powered enterprise contact centre that automates real business workflows across voice, SMS, chat, and APIs.

We integrate with telephony providers, CRMs, ATS platforms, and internal enterprise systems to power AI agents that handle inbound calls, qualification flows, onboarding processes, support queries, and operational tasks.

The Role

As a Forward Deployed Engineer, you will embed directly into enterprise deployments and own the technical delivery of integrations between Whippy and customer systems.

You will operate at the intersection of APIs, telephony, databases, and AI workflows. You will design and ship production-grade systems, debug live issues, and convert customer-specific requirements into reusable platform capabilities.

This is a high-ownership role. You will work closely with customers, product, and core engineering to ensure deployments are robust, scalable, and repeatable.

What You’ll Do

• Own end-to-end delivery of production integrations across CRM, ATS, telephony, and internal systems
• Design and implement reliable data flows between Whippy and external platforms
• Handle authentication, rate limits, retries, and failure modes in distributed systems
• Debug and resolve non-trivial production issues across webhooks, async workflows, and external APIs
• Improve logging, monitoring, and observability of deployment pipelines
• Translate ambiguous customer requirements into clear technical designs
• Identify repeated patterns and convert one-off implementations into reusable connectors or internal tooling
• Collaborate with product and engineering to push field learnings back into the platform

What We’re Looking For

• 2+ years of experience in software engineering or technical consulting
• Strong backend fundamentals and comfort working with APIs and relational databases such as Postgres
• Experience integrating third-party systems or working with external APIs in production
• Understanding of distributed systems concepts such as idempotency, retries, async processing, and error handling
• Experience debugging production systems under time pressure
• Clear, structured communicator able to explain trade-offs to both technical and non-technical stakeholders
• Ownership mindset and comfort operating with ambiguity

Nice to Have

• Experience with telephony, event-driven systems, or webhook-based architectures
• Exposure to AI workflows, automation systems, or LLM integrations
• Experience working directly with enterprise customers, e.g in consulting, banking or equivalent

What Success Looks Like

Within 90 days, you will:

• Own at least one enterprise deployment end-to-end
• Resolve a meaningful production issue independently
• Ship at least one reusable improvement that reduces future deployment effort
• Demonstrate strong judgment around scope, trade-offs, and customer impact

Prep for this interview

4 questions likely to come up at Whippy, each matched to a line in this posting.

  1. 1Integrations and APIs
    They wrote: “Debug and resolve non-trivial production issues across webhooks, async workflows, and external APIs”

    A customer's API starts returning errors in production at 2am. What do you do?

    How to answer

    Why they ask: FDEs often own production for their customers. This tests incident handling and communication.

    1. Check your side first: logs, recent deploys, retries piling up
    2. Stop the damage (pause jobs, queue requests, turn off the feature)
    3. Tell the customer what you see and what you've done, in plain words
    4. Afterwards: add a check that would have caught it, and write a short report

    Tip: Split the answer into the first hour and the week after.

  2. 2Ownership and working with customers
    They wrote: “Ownership mindset and comfort operating with ambiguity”

    Tell me about a project where the requirements kept changing. What did you do?

    How to answer

    Why they ask: Ambiguity is the norm. They want proof you can keep moving without a clear spec.

    1. The project and why requirements kept moving
    2. What you did to pin them down (short demos, written decisions)
    3. The trade-offs you made to keep shipping
    4. The result, with a number if you have one

    Tip: Show how you reduced the change, beyond how you coped with it.

  3. 3Discovery and scoping
    They wrote: “Translate ambiguous customer requirements into clear technical designs”

    Tell me about a time the customer asked for one thing but needed another.

    How to answer

    Why they ask: Good FDEs spot when a request is a guess at a solution. They want proof you can redirect a customer without losing their trust.

    1. What they asked for, and the detail that made you doubt it
    2. How you tested the doubt (shadowed users, looked at logs, ran a quick prototype)
    3. How you made the case to the customer
    4. What shipped and what changed for them

    Tip: Pick a story where you checked your hunch with data or users before pushing back.

  4. 4LLMs, RAG and agents
    They wrote: “We integrate with telephony providers, CRMs, ATS platforms, and internal enterprise systems to power AI agents that handle inbound calls, qualification flows, onboarding processes, support queries, and operational tasks.”

    The model gives a confident wrong answer to an important customer. What now?

    How to answer

    Why they ask: Tests how you handle trust, on top of the technical fix.

    1. Tell the customer the same day what you know and when they'll hear more
    2. Reproduce it and find the cause (bad retrieval, missing data, prompt, model)
    3. Add the case to the test set so it can't come back unnoticed
    4. Add a guard where it matters: citations, confidence checks, human review

    Tip: Own it with the customer first, then show the change that stops it happening again.

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 Whippy

Similar roles at other companies

Whippy

On-site

Apply