TPM, Fwd Deployed Engineer, Business Innovation and AI
Amazon · Bellevue, WA · 1 mo ago
Project ManagementFull-time
We need to output HTML fragment with sections only when content present. Must use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to extract content.
Job description includes:
- Description paragraph(s) about role: "The Forward Deployed Engineering (FDE) team within Business Innovation & AI (BIA) is looking for a Technical Program Manager who builds..." etc. This is about the role.
- "What Makes This Role Different?" maybe part of About the role.
- "Key job responsibilities" list: Build AI & Agentic Solutions, Embedded; Program Delivery; Raising the Bar.
- "A day in the life" maybe part of responsibilities or about role.
- "About The Team" maybe about the team.
- "Basic Qualifications" and "Preferred Qualifications".
- Benefits: mention Amazon offers comprehensive benefits including health insurance..., 401(k) matching, paid time off, parental leave. Also mention sign-on payments and RSUs.
- Pay: base salary range listed for locations: USA, TN, Nashville - 120,800.00 - 163,400.00 USD annually; USA, WA, Bellevue - 127,100.00 - 172,000.00 USD annually.
- Schedule: not mentioned.
- Skills: maybe not explicit; we could infer from qualifications but better not to invent. Only include sections if posting has real specific content. Skills section not present explicitly; we could omit.
- Requirements: maybe basic qualifications.
- Qualifications: could combine basic and preferred? But we have both Basic Qualifications and Preferred Qualifications. Could put under Requirements (basic) and Qualifications (preferred) or combine. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections to include based on content.
We have content for About the role (description). Responsibilities (key job responsibilities + day in the life). Requirements (basic qualifications). Qualifications (preferred qualifications). Benefits (benefits description). Pay (salary ranges). Schedule: none -> omit. Skills: none explicit -> omit.
We must not repeat job title as heading. No Job ID etc.
We must preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like EEO etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
We need to output only HTML fragment, no /, no markdown fences.
Let's extract content precisely.
About the role: combine initial description and "What Makes This Role Different?" and "About The Team"? Actually About The Team could be separate but we can include under About the role or maybe separate section? The instruction list includes About the role as a heading; we can put all role description there.
Let's gather paragraphs:
"The Forward Deployed Engineering (FDE) team within Business Innovation & AI (BIA) is looking for a Technical Program Manager who builds. FDE embeds directly with teams across Amazon Global Operations Services (GOS), co-builds with them from day one, and ships working AI-powered solutions. Engagements range from short builds to multi-quarter programs. The impact here is internal: you build for the GOS org, not for external customers. We increasingly look for opportunities to replace manual processes and web-based interfaces with AI agents, so a lot of what you build will be agentic. This is a hands-on builder role. We’re looking for people who are already shipping AI solutions with the current generation of tooling, not people who are newly exploring AI or have only done some prompt engineering. The engineers who do well here are hands-on with agentic harnesses like Claude Code, Kiro, and Codex, and are plugged into the AI builder community closely enough to know what changed this month."
"What Makes This Role Different? Most program roles ask you to coordinate other people’s work from a distance. FDE asks you to sit with the operational team and build the solution yourself. You take prototypes to production and hand scalable patterns back to the broader org."
"About The Team Business Innovation & AI (BIA) finds the hardest, highest-value problems across Amazon Global Operations Services and builds AI-powered solutions that measurably change how work gets done. Forward Deployed Engineering (FDE) is BIA’s technical execution arm: a small, senior team with high autonomy and a bias for shipping. We embed with operational teams in the GOS org, co-build from day one, ship working solutions, and hand scalable patterns off to the broader organization. We don’t just automate the existing process; we redesign the work around what AI and agents make possible."
We can combine these into About the role section.
Responsibilities: list from "Key job responsibilities" bullet points and "A day in the life".
Key job responsibilities:
- Build AI & Agentic Solutions, Embedded
- Embed with GOS operational teams, co-build from day one, and ship AI-powered solutions that replace manual workflows
- Look for opportunities to replace manual processes and web-based interfaces with AI agents, and build those agents end to end
- Build with the current AI tooling yourself, including agentic harnesses (Claude Code, Kiro, Codex), LLM application frameworks, and RAG, and take prototypes to production
- Program Delivery
- Own the planning, coordination, and delivery of your AI programs, managing scope, risk, and dependencies without relying on direct authority
- Keep delivery moving across engineers, data scientists, and operational stakeholders
- Raising the Bar
- Bring back the tooling and patterns that work, and help the team ship faster
- Document and hand off scalable solutions to the broader organization
"A day in the life":
- You start the morning embedded with an operations team, mapping a manual workflow you’re replacing with an agent.
- By mid-morning you’re building, wiring it up with current tooling and putting the next iteration in front of them.
- In the afternoon you iterate with the customer in the room, then push the working pieces toward production.
- You close the day sharing a tooling trick with the team that cut your build time in half.
We can combine these into a
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to extract content.
Job description includes:
- Description paragraph(s) about role: "The Forward Deployed Engineering (FDE) team within Business Innovation & AI (BIA) is looking for a Technical Program Manager who builds..." etc. This is about the role.
- "What Makes This Role Different?" maybe part of About the role.
- "Key job responsibilities" list: Build AI & Agentic Solutions, Embedded; Program Delivery; Raising the Bar.
- "A day in the life" maybe part of responsibilities or about role.
- "About The Team" maybe about the team.
- "Basic Qualifications" and "Preferred Qualifications".
- Benefits: mention Amazon offers comprehensive benefits including health insurance..., 401(k) matching, paid time off, parental leave. Also mention sign-on payments and RSUs.
- Pay: base salary range listed for locations: USA, TN, Nashville - 120,800.00 - 163,400.00 USD annually; USA, WA, Bellevue - 127,100.00 - 172,000.00 USD annually.
- Schedule: not mentioned.
- Skills: maybe not explicit; we could infer from qualifications but better not to invent. Only include sections if posting has real specific content. Skills section not present explicitly; we could omit.
- Requirements: maybe basic qualifications.
- Qualifications: could combine basic and preferred? But we have both Basic Qualifications and Preferred Qualifications. Could put under Requirements (basic) and Qualifications (preferred) or combine. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections to include based on content.
We have content for About the role (description). Responsibilities (key job responsibilities + day in the life). Requirements (basic qualifications). Qualifications (preferred qualifications). Benefits (benefits description). Pay (salary ranges). Schedule: none -> omit. Skills: none explicit -> omit.
We must not repeat job title as heading. No Job ID etc.
We must preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like EEO etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
We need to output only HTML fragment, no /, no markdown fences.
Let's extract content precisely.
About the role: combine initial description and "What Makes This Role Different?" and "About The Team"? Actually About The Team could be separate but we can include under About the role or maybe separate section? The instruction list includes About the role as a heading; we can put all role description there.
Let's gather paragraphs:
"The Forward Deployed Engineering (FDE) team within Business Innovation & AI (BIA) is looking for a Technical Program Manager who builds. FDE embeds directly with teams across Amazon Global Operations Services (GOS), co-builds with them from day one, and ships working AI-powered solutions. Engagements range from short builds to multi-quarter programs. The impact here is internal: you build for the GOS org, not for external customers. We increasingly look for opportunities to replace manual processes and web-based interfaces with AI agents, so a lot of what you build will be agentic. This is a hands-on builder role. We’re looking for people who are already shipping AI solutions with the current generation of tooling, not people who are newly exploring AI or have only done some prompt engineering. The engineers who do well here are hands-on with agentic harnesses like Claude Code, Kiro, and Codex, and are plugged into the AI builder community closely enough to know what changed this month."
"What Makes This Role Different? Most program roles ask you to coordinate other people’s work from a distance. FDE asks you to sit with the operational team and build the solution yourself. You take prototypes to production and hand scalable patterns back to the broader org."
"About The Team Business Innovation & AI (BIA) finds the hardest, highest-value problems across Amazon Global Operations Services and builds AI-powered solutions that measurably change how work gets done. Forward Deployed Engineering (FDE) is BIA’s technical execution arm: a small, senior team with high autonomy and a bias for shipping. We embed with operational teams in the GOS org, co-build from day one, ship working solutions, and hand scalable patterns off to the broader organization. We don’t just automate the existing process; we redesign the work around what AI and agents make possible."
We can combine these into About the role section.
Responsibilities: list from "Key job responsibilities" bullet points and "A day in the life".
Key job responsibilities:
- Build AI & Agentic Solutions, Embedded
- Embed with GOS operational teams, co-build from day one, and ship AI-powered solutions that replace manual workflows
- Look for opportunities to replace manual processes and web-based interfaces with AI agents, and build those agents end to end
- Build with the current AI tooling yourself, including agentic harnesses (Claude Code, Kiro, Codex), LLM application frameworks, and RAG, and take prototypes to production
- Program Delivery
- Own the planning, coordination, and delivery of your AI programs, managing scope, risk, and dependencies without relying on direct authority
- Keep delivery moving across engineers, data scientists, and operational stakeholders
- Raising the Bar
- Bring back the tooling and patterns that work, and help the team ship faster
- Document and hand off scalable solutions to the broader organization
"A day in the life":
- You start the morning embedded with an operations team, mapping a manual workflow you’re replacing with an agent.
- By mid-morning you’re building, wiring it up with current tooling and putting the next iteration in front of them.
- In the afternoon you iterate with the customer in the room, then push the working pieces toward production.
- You close the day sharing a tooling trick with the team that cut your build time in half.
We can combine these into a - list.
Requirements (Basic Qualifications):
- 3+ years of technical program management experience
- Experience demonstrating software engineering skills in a previous intership, work experience, coding competitions, or publications, or experience with programming/scripting (Batch, VB, PowerShell, Java, C#, Chef, Perl, Ruby and/or PHP) and experience with automation and any version control tools
- Experience working with multiple groups of stakeholders
- Bachelor's degree or above in computer science, computer engineering, or related field, or experience working in Science, Technology, Engineering, or Mathematics (STEM)
- Experience in developing and deploying LLMs in production on GPUs, Neuron, TPU or other AI acceleration hardware, or experience in debugging, profiling, and implementing software engineering best practices in large-scale systems
We need to preserve exactly as given.
Preferred Qualifications:
- Experience building complex software systems that have been successfully delivered to customers, or experience in developing and deploying LLMs in production on GPUs, Neuron, TPU or other AI acceleration hardware
- Experience in professional, non-internship software development, or experience in developing and deploying LLMs in production on GPUs, Neuron, TPU or other AI acceleration hardware
- Experience building AI agents that replace manual or UI-driven workflows
- Fluency with the current GenAI tooling landscape (Amazon Bedrock, agent frameworks, LLM-powered workflows)
- Experience in rapid-prototyping, forward-deployed, or embedded engineering models
- Experience with AWS and Infrastructure as Code
- Data or analytics experience (SQL, pipelines, connecting source data to a customer need)
Note there is some duplication; we keep as is.
Benefits:
- "Amazon is an equal opportunity employer ..." that's boilerplate to remove. But benefits paragraph: "Our inclusive culture empowers Amazonians to deliver the best results for our customers. If you have a disability and need a workplace accommodation or adjustment during the application and hiring process, including support for the interview or onboarding process, please visit https://amazon.jobs/content/en/how-we-hire/accommodations for more information. If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." That's also boilerplate/accommodation; we should remove? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The accommodation link might be considered EEO/accommodation; better to remove. The benefits paragraph after that: "The base salary range for this position is listed below. Your Amazon package will include sign-on payments and restricted stock units (RSUs). Final compensation will be determined based on factors including experience, qualifications, and location. Amazon also offers comprehensive benefits including health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage), 401(k) matching, paid time off, and parental leave. Learn more about our benefits at https://amazon.jobs/en/benefits."
We need to keep the benefits description: comprehensive benefits including health insurance..., 401(k) matching, paid time off, parental leave. Also mention sign-on payments and RSUs (these are part of compensation but could be under Pay? but we can keep in Benefits or Pay). The instruction: Benefits section for benefits; Pay section for salary. So we can put sign-on payments and RSUs under Pay? Actually they said "Your Amazon package will include sign-on payments and restricted stock units (RSUs)." That's compensation, not base salary. Could be part of Pay. But we have Pay section for base salary range. We could include sign-on payments and RSUs in Pay as well, but the instruction says Pay section only when posting actually states them. It does state sign-on payments and RSUs, so we can include them in Pay section along with base salary range. However they also said "Prefer a few substantive sections over many thin ones." Might combine Pay and Benefits? But they are separate headings. We'll follow instruction: include Pay section if posting states them. It does state base salary range and sign-on payments and RSUs. So Pay section will include that info.
Benefits section will include health insurance etc.
Schedule: none -> omit.
Now we need to output HTML fragment with headings
and content
or
- .
We must not include any extra text outside HTML.
Let's craft.
Structure:
About the role
...combined paragraphs...
Responsibilities
- ... each bullet ...
...
We need to ensure we preserve all details. For responsibilities we can combine the bullet points and day-in-life as separate list items.
Let's list them:
- Embed with GOS operational teams, co-build from day one, and ship AI-powered solutions that replace manual workflows
- Look for opportunities to replace manual processes and web-based interfaces with AI agents, and build those agents end to end
- Build with the current AI tooling yourself, including agentic harnesses (Claude Code, Kiro, Codex), LLM application frameworks, and RAG, and take prototypes to production
- Own the planning, coordination, and delivery of your AI programs, managing scope, risk, and dependencies without relying on direct authority
- Keep delivery moving across engineers, data scientists, and operational stakeholders
- Bring back the tooling and patterns that work, and help the team ship faster
- Document and hand off scalable solutions to the broader organization
- You start the morning embedded with an operations team, mapping a manual workflow you’re replacing with an agent.
- By mid-morning you’re building, wiring it up with current tooling and putting the next iteration in
and content
or
- .
We must not include any extra text outside HTML.
Let's craft.
Structure:
About the role
...combined paragraphs...
Responsibilities
- ... each bullet ... ...