Forward Deployed Engineer

Excerpt from the original posting

Job Summary 
Forward Deployed Engineers take a defined use case from nothing to a working, production-grade system inside the customer's environment. That starts with knowing our platform deeply enough to combine its capabilities into solutions more complex than any single feature was designed for - and where a customer's specific needs call for something beyond the standard functionality, building that missing piece themselves. This is the role that builds the use case: not a prototype handed to someone else to production, but the system that goes live. 
This is a customer-facing role. Understanding the customer's needs and the realistic possibilities of their technical environment - and working in close, daily collaboration with them - is what makes a deployment succeed. We're in daily working contact with the customer's engineers and executives, mostly online, with our team and theirs operating as one delivery unit with shared planning. Success is measured on the customer's numbers - resolution rate, containment, response latency, CSAT, cost per contact - and accountability continues past go-live. 
Forward Deployed Engineering brings together two disciplines that used to sit apart: conversation design and integration engineering. An engineer who can build the technical logic behind a scenario; a conversation designer who can design the flow of the conversation itself - that is what an FDE is. We hire people who are genuinely strong in one of the two and want to grow the other - expert in both is a direction of travel, not an entry bar. The role is based in Prague and is part of a global function with teams in EMEA and North America. 

Please note this is a hybrid role with significant customer on-site availability required. 

Responsibilities 
- Own the solution design: translate a stated business problem into a technical architecture that fits the customer’s actual processes, constraints and systems. 
- Build the agent 0→1: design, build and iterate the first working version end to end - the system that goes into production, not a hand-off. 
- Close product gaps: build the custom extensions, integrations, services and tooling the deployment requires, without waiting for core roadmap prioritization. 
- Own the integration surface: systems of record, contact channels and data flows - and, for voice deployments, the telephony path from carrier to agent. 
- Evaluate, iterate, improve: define the workflow-specific tests that determine whether this deploymen…

→ CallMiner · Workable