
Forward Deployed Engineer – Intern
Posted 4 days ago
The role in short
Build and debug production API integrations and data flows between Whippy's AI platform and customer systems like CRMs and telephony providers.
Overview
Location: Dublin, Ireland, on-site
Requirement: Degree in Maths, Engineering or Computer Science (completed or final year)
About Whippy
Whippy is an AI-powered communication platform 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 Engineering Intern, you will work inside real enterprise deployments and ship production code that connects Whippy to customer systems.
You will operate at the intersection of APIs, telephony, databases, and AI workflows. This is not a research role and not a shadowing internship. You will build and debug real systems used by live customers.
This internship is designed as a pathway to a full-time Forward Deployed Engineer role.
What You’ll Do
• Build and extend API integrations with third-party systems (CRM, ATS, telephony, internal tools)
• Implement data flows between Whippy and external platforms
• Debug production issues involving webhooks, retries, and async workflows
• Improve logging, monitoring, and visibility across deployment systems
• Document integration architecture and deployment patterns
• Identify patterns across customer implementations and propose reusable improvements
What We’re Looking For
• Degree in Mathematics, Engineering, or Computer Science (completed or final year)
• Strong fundamentals in programming
• Experience building non-trivial software projects (internships, open source, side projects)
• Comfort working with APIs and relational databases
• Ability to reason clearly about data flow and failure modes
• Strong ownership mindset and willingness to debug real production issues, communicate clearly in writing and verbally
Prep for this interview
4 questions likely to come up at Whippy, each matched to a line in this posting.
- 1Integrations and APIs
They wrote: “Build and extend API integrations with third-party systems (CRM, ATS, telephony, internal tools)”
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.
- 2LLMs, 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.”
A customer wants a chatbot over their internal documents. How do you build it?
How to answer
Why they ask: RAG is the most common first project. They want the whole path, from messy files to answers people trust.
- Collect and clean the documents; handle permissions per user
- Split them into chunks, embed, and store with source links
- Retrieve, then answer with citations; say “I don't know” when retrieval is weak
- Build a test set of real questions with expected answers before launch
Tip: Spend more time on the data and on testing than on the model.
- 3Coding
They wrote: “As a Forward Deployed Engineering Intern, you will work inside real enterprise deployments and ship production code that connects Whippy to customer systems.”
How do you keep quality high when you ship fast at a customer site?
How to answer
Why they ask: Speed is the job, but broken code at a customer is costly. They want your guardrails.
- Tests for the parts that touch customer data or money
- Code review even when it's fast, ideally by someone on the product team
- Feature flags and an easy way to roll back
- Clean up the shortcuts in the next release, and write them down
Tip: Name the few checks you never skip, and what you skip on purpose.
- 4Ownership and working with customers
They wrote: “Strong ownership mindset and willingness to debug real production issues, communicate clearly in writing and verbally”
Describe a time you had to tell a customer bad news.
How to answer
Why they ask: FDEs are the face of the company on site. Trust is part of the job.
- The situation and what went wrong
- When and how you told them
- The plan you offered
- How the relationship looked afterwards
Tip: Pick a story where you told them early and came with a plan.
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.

