AWS Forward Deployed Engineering is now available in 15 countries, sold as fixed-price 45-day sprints
In a Nov 17 AWS blog post, FDE head Dr. Asa Kalavade says AWS Forward Deployed Engineering, launched in June, is now offered to commercial and public sector customers in 15 countries, with each 45-day sprint carrying a set price billed through the customer's AWS account.
AWS has widened its Forward Deployed Engineering (FDE) service, launched in June, to commercial and public sector customers in 15 countries: the US, Mexico, Brazil, Canada, Australia, Singapore, India, South Korea, Japan, the UK, Germany, the Netherlands, France, Sweden and Saudi Arabia. Buying it is also simpler now: each 45-day sprint has a set price under FDE Terms and is billed through the customer's AWS account.
In the post, Dr. Asa Kalavade describes the model: a small team of AWS engineers, scientists and product managers works alongside the customer's engineers and a crew of AI agents, building in the customer's own AWS account from day one. Many of the FDEs come from the teams behind Amazon Bedrock, AgentCore, Kiro, AWS Quick and Security Hub. The work follows AWS's AI-Driven Development Lifecycle (AI-DLC) on a standard stack with a shared context layer, a workbench, an AgentCore runtime and a governance control tower.
AWS gives three customer examples. Samsung Life Insurance got a governed agentic platform for four affiliates in 45 days. At Rio Tinto Iron Ore, agents mapped a 30-year-old Oracle supply-chain system with more than 5,000 tables in weeks. Marsh had its first use case in production about two months after work began, with efficiency gains of up to 70% in the targeted areas.
Why it matters for FDEs: AWS is turning forward deployed engineering into a packaged, fixed-price product across five continents, so expect more AWS FDE hiring outside the US. The post also shows what AWS values in the job: drawing out unwritten business rules from the people who do the work, building governance in from the start, and leaving customer teams able to run the system after the engagement ends.
Source: aws.amazon.com