Forward Deployed Engineer

Context:

One of our fast-growing Series A Enterprise AI portfolio companies is expanding their forward deployed engineering team - and looking for sharp engineers who will own how their voice AI product gets deployed, adopted, and embedded into the operations of large financial institutions.

Location: Bengaluru, Mumbai and Gurugram

Experience: 2-7 years

What the work actually looks like:

• Own deployments end-to-end - from the first technical scoping call to the moment the agent goes live and beyond
• Integrate with core banking systems, CRMs, IVR stacks, and legacy systems.
• Write integration code, build custom connectors, and configure workflows that fit the customer's reality - not the other way around
• Debug things in production, under pressure, sometimes with CXOs watching over your shoulder
• Translate what you see in the field into sharp, actionable feedback for the product and engineering team back home
• Build deployment playbooks and templates so the next rollout is faster than the last one

What we are looking for:

• 24 years in a forward deployment, solutions engineering, or technical implementation role at a B2B software company
• Solid engineering fundamentals - Python and/or JavaScript, REST APIs, cloud infrastructure. You write real code, not just configuration
• Hands-on experience with Voice AI - ASR, TTS, and STT pipelines - you understand the latency, accuracy, and language model tradeoffs that make or break a voice product in production
• Familiarity with IVR telephony stacks and how they integrate with modern AI layers is a strong plus
• Familiarity with how large enterprises work: their risk posture, compliance requirements, and why decisions take longer than you'd like
• The ability to hold a technical conversation with an integration engineer and a business conversation with a CXO - sometimes in the same meeting

This role is probably right for you if:

• You get restless in purely internal roles and need the texture of working directly with customers
• Ambiguity doesn't slow you down - incomplete documentation, shifting requirements, and unclear ownership are just the job
• You have figured things out in environments that weren't set up for you to succeed and felt good about it
• You want to build something from close to the ground floor, and you understand what that trade-off actually means