Forward Deployed Engineer - Intern
Blue Machines AI
Forward Deployed Engineer — Intern
Blue Machines AI
Location: Bangalore (in-office) | Duration: [3–6] months, full-time | Reports to: Engineering Manager, Forward Deployed Engineering
About the role
Blue Machines AI builds enterprise CX systems for clients in banking, insurance, health insurance and e-commerce — voice agents, workflow automation, and the integrations that tie both into the customer’s existing stack.
Forward Deployed Engineers own live accounts: keeping deployments healthy, root-causing what breaks, and turning interaction data into decisions for both the client and our product team. As an intern, you will work on real accounts from week one, alongside the FDE who owns them.
What you’ll do
- Map and configure client workflows on the platform — the full journey across voice, backend systems and human handoff, not just a single agent turn
- Run root cause analysis on production issues: trace a failed interaction across logs, integration calls and workflow steps down to a specific cause, then write it up so it does not recur
- Build and maintain the integrations these workflows run on — REST APIs, webhooks, CRM / ticketing / core system connections — and debug them when auth, payloads or timeouts break
- Own account reporting: containment and deflection rates, drop-off points, latency, resolution rates — including the queries and dashboards behind the numbers
- Analyse call transcripts and workflow logs at volume to find failure patterns and quantify their impact before proposing a fix
- Support UAT and go-lives with scenario testing across the whole workflow, plus defect logging and triage
- Document RCAs, runbooks and configuration so an account can be handed over cleanly
- Track your work in JIRA and join the daily standup
Must have
- Final-year student or recent graduate in CS / IT / Engineering, or equivalent self-taught ability
- Python or JavaScript/TypeScript at a working level — enough to script, parse logs and call APIs
- SQL and genuine comfort with data — you can pull the number yourself, not just read a dashboard
- REST APIs, JSON, and a real debugging instinct: able to follow a problem across systems rather than stopping at the first error message
- Clear written English — RCAs and client updates are written deliverables
- Structured thinker who documents as they go
Good to have
- A BI or analytics tool (Metabase, Looker, Power BI or similar)
- Postman, Git