[Talent Pool] Forward Deployment Architect
Description
Summary
Decide the shape of the estate and make build-vs-buy an evidenced decision rather than a habit. The FDA converts strategy into an implementable blueprint, sequences the transition states, and holds the standards that stop a modern platform decaying into another set of point-to-point integrations.
What you will do
- Own the target architecture and the transition states for a consumer domain — current, next, target, and the date each is true.
- Design the headless, agent-led patterns: intent-first CRM, orchestration, tool contracts, human-in-the-loop fallbacks.
- Run the build-vs-buy case with real numbers: licence, managed-service scope, capex, cost-to-serve, exit cost, IP ownership.
- Define API, event and data contracts across brands and lines of business so one product model serves all channels.
- Plan vendor exits — scope carve-out, knowledge transfer, dual-run, contractual and data-ownership steps.
- Chair design review; make security, privacy and regulatory requirements part of the pattern, not a late gate.
- Prototype personally when the decision is unclear — a working spike beats an opinion.
Grade expectations
FDA1
Staff Architect
SCOPE & DECISION RIGHTS : One platform or capability. Recommends the design; decides within an agreed pattern.
ACCOUNTABLE FOR : A buildable design with interfaces, NFRs and a migration path. Estimates that survive delivery.
FDA2
Senior Staff Architect
SCOPE & DECISION RIGHTS : A domain (self-care, S&D, core, or conversational). Owns the transition-state plan and the build-vs-buy recommendation.
ACCOUNTABLE FOR : Cross-brand product and API model. Vendor-exit feasibility. Cost-to-serve model behind the business case.
FDA3
AVP, Architecture
SCOPE & DECISION RIGHTS : The consumer technology estate. Sets standards, reference architecture, cloud strategy and the insourcing sequence; signs off major spend patterns.
ACCOUNTABLE FOR : Architectural coherence and build ratio across the estate. Multi-year capex/opex trajectory. Regulator- and audit-ready posture.
Architecture must-haves
- Has architected and delivered — not just documented — a large replatforming or insourcing programme.
- Domain-driven decomposition, event-driven integration, API product thinking.
- Multi-cloud reality: primary hyperscaler plus a secondary cloud, data residency, egress and lock-in economics.
- Non-functional rigour: availability tiering, capacity, disaster recovery, zero-trust security, privacy by design.
- Writes clearly enough that a business sponsor and an engineer both act on the same document.
Telecom domain must-haves
- Deep BSS/OSS architecture: CRM, catalogue, charging and billing, order management, provisioning, partner settlement.
- TM Forum ODA/SID and Open API fluency; knows where the standard helps and where it slows you down.
- Has negotiated technically with tier-1 telco vendors and managed-service partners.
- Understands Indonesian market context: regulatory reporting, KYC, prepaid dominance, digital-wallet and OTT partnerships.
- Post-merger dual-brand or dual-stack consolidation experience strongly preferred.
Skills
Sign in to read and join the discussion.