[Talent Pool] Forward Deployment Engineer
Description
Summary
Sit with the business, and turn a commercial ask into production software on a live consumer journey — in days, not quarters. FDEs are the people who make insourcing real: they take a journey currently delivered by a vendor and stand up an owned, instrumented, agent-ready replacement.
What you will do
- Build and extend insourced platforms — commercial catalogue, cross-brand product release, loan and lending, OTT gateway, conversational commerce.
- Own one consumer journey end-to-end: API, service, data contract, front-end surface, dashboards, on-call.
- Work AI-native by default — agentic coding tools for delivery, and agent frameworks with evals inside the product itself.
- Replace vendor-managed flows: reverse-engineer, write the parity test suite, run the dual-run, cut over without customer impact.
- Sit in the business review, not just the sprint review — take the requirement first-hand and push back on it.
- Leave the work operable: runbooks-as-code, SLOs, cost-per-transaction visible before launch.
Grade expectations
FDE1
Staff Engineer
SCOPE & DECISION RIGHTS :One service or journey slice. Makes implementation calls inside an agreed design; escalates contract changes.
ACCOUNTABLE FOR : Shipped, tested, observable code. Their share of the on-call rota. Story-level estimates that hold.
FDE2
Senior Staff Engineer
SCOPE & DECISION RIGHTS : A journey family across several platforms. Owns the design, sequences the cutover, approves peers' designs, sets the agent and eval pattern for the domain.
ACCOUNTABLE FOR : Journey SLOs and unit cost. A vendor-to-insource cutover delivered without regression. Growth of 3–5 FDEs.
FDE3
AVP, Forward Deployment
SCOPE & DECISION RIGHTS : Engineering for a business vertical. Build-vs-buy calls, team shape, tooling standards, spend inside an agreed envelope.
ACCOUNTABLE FOR : Portfolio delivery and build ratio. Capex/opex outcome for the vertical. Hiring and retaining the pod.
Engineering must-haves
- Strong production code in at least one of Java, Go, Kotlin, Python or Node/TypeScript.
- API and event design — REST/GraphQL, Kafka, idempotency, backward-compatible contracts.
- Cloud-native on GCP or equivalent: Kubernetes, IaC, CI/CD, progressive delivery.
- Observability as a habit: traces, SLOs, error budgets.
- LLM/agent engineering: tool-calling, retrieval, guardrails, evaluation harnesses.
Telecom domain must-haves
- Worked inside telco BSS: CRM, product catalogue, order-to-activate, charging, mediation, or digital channels.
- Understands prepaid economics — balance, validity, top-up, bundles, loans, and why a failed charge is a revenue event.
- Familiar with TM Forum Open APIs / ODA, eSIM, USSD and IN interaction models.
- Has shipped for high-volume consumer traffic with campaign-driven peaks.
- Multi-brand or multi-LOB product structures (mobile, FTTH, FWA, OTT) an advantage.
Skills
Sign in to read and join the discussion.