Software Dev Engineer, AWS Billing
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information, not invent or summarize away detail. So we need to include details from description, responsibilities, qualifications, benefits, pay.
We must remove boilerplate: EEO, accommodation link, etc. Also remove duplicated lines. Also remove application instructions (none). Also remove navigation/cookie etc.
We need to ensure we don't include placeholder like "commensurate with experience". Not present.
Let's extract content.
Description: "Build the full-stack experiences that help millions of AWS customers understand and optimize their cloud spending. We own the console surfaces and services behind AWS Cost Explorer, BCM Dashboards, and AWS Budgets — and we're evolving them fast. As an SDE 2, you'll own features end-to-end — from frontend React components to backend Java services to the operational health of what you ship. You'll design solutions to difficult problems: making cost data intuitive at massive scale, building managed dashboard experiences, and migrating millions of customers to modernized console architectures. You won't just implement specs — you'll work directly with product and UX to understand customer pain, propose approaches, and ship iteratively. What makes this role compelling: You'll work across the full stack — React/TypeScript frontends, Java/AWS backend services, CDK infrastructure — with real ownership, not ticket work The problems are genuinely hard: multi-partition deployments, cost allocation at scale, and UX for data that is inherently complex Our team uses AI tools daily as development partners You'll mentor others, lead design reviews, and influence the team's technical direction — this is a role where your voice shapes the architecture This isn't a maintenance role. We're actively rebuilding and modernizing core billing console experiences while launching net-new dashboard and AI-driven cost insight products. You're joining while the hard decisions are still being made."
We can put that under About the role (or maybe a general description). The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should have About the role heading.
Responsibilities: list from "Key job responsibilities" bullet points.
Let's extract each bullet:
- Design and build full-stack features across AWS Cost Explorer, BCM Dashboards, and AWS Budgets — React/TypeScript frontends and Java backend services serving millions of AWS customers.
- Own features through the full software lifecycle — from customer problem discovery and technical design through implementation, testing, deployment, and production operations.
- Solve difficult problems at scale — cost data visualization, managed dashboard experiences, and console migration for millions of existing customers across multi-partition deployments.
- Author technical design documents, lead design reviews, and provide meaningful code reviews that raise the team's code bar.
- Drive operational excellence — own alarms, monitoring, runbooks, and on-call rotations for live production services; resolve root causes of systemic issues.
- Mentor engineers, onboard new team members, and foster an inclusive environment where diverse perspectives shape technical decisions.
- Collaborate with product management and UX to deeply understand customer pain points and translate them into incremental, shippable solutions.
- Contribute to team technical strategy and roadmap — help decide where to invest, what to modernize, and what to deprecate.
- Write clean, testable, production-ready code using AI-native development practices — leveraging GenAI tools as daily development partners.
We'll put each as
- .
Qualifications: Basic Qualifications and Preferred Qualifications.
Basic Qualifications:
- 2+ years of non-internship design or architecture (design patterns, reliability and scaling) of new and existing systems experience
- 2+ years of non-internship professional software development experience
- Experience programming with at least one software programming language
Preferred Qualifications:
- Bachelor's degree in computer science or equivalent
- 2+ years of full software development life cycle, including coding standards, code reviews, source control management, build processes, testing, and operations experience
We could combine under Qualifications heading with sub-sections? But instruction says use
for section headings; we can have Qualifications heading and then maybe separate Basic and Preferred as
or
. We'll list both as with items.
Skills: Could list technologies: React, TypeScript, Java, AWS, CDK, AI/GenAI tools. The description mentions those. We'll create a Skills section with .
Benefits: The posting includes benefits description: "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." Also mention sign-on payments and RSUs. We'll include that.
Pay: The base salary range: "USA, WA, Seattle - 143,700.00 - 194,400.00 USD annually". Also mention sign-on payments and RSUs but that's part of compensation. We'll include Pay section with that range.
Schedule: Not present, so omit.
We must not repeat job title. Not include Company? Could include as metadata? The instruction says do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short or drop it. So we could include a short
for company and location maybe. But not required. We could include a brief paragraph after About the role maybe. But we need to preserve all substantive information; company and location are substantive. We'll include a
after About the role maybe.
But we must not create headings for minor metadata. So we can include a
with "Amazon Development Center U.S., Inc. – Seattle, WA". That's fine.
Now produce HTML fragment.
Structure:
About the role
Build the full-stack experiences ... (the description paragraph(s)). Could be multiple paragraphs but we can combine into one
with line breaks? Better to keep as
for prose; we can have multiple
sentences.
We'll split description into maybe two
for readability but still okay.
Then maybe a
for company/location.
Then
Responsibilities
...
Then Qualifications
... maybe separate Basic and Preferred? Could have two with headings? But headings would be not allowed? Only for section headings. We could just list all qualifications in one but differentiate with text. Could add Basic Qualifications: then list items, then Preferred Qualifications:. That's okay inside ? Might be messy. Better to have two each preceded by a indicating type. But that adds extra
not prohibited. We'll do:
Qualifications
Basic Qualifications:
...
Preferred Qualifications:
...
That preserves info.
Then Skills
...
Then Benefits
...
Then Pay
...
Make sure no extra whitespace? It's fine.
Now craft content precisely.
About the role paragraph(s):
We'll take the description block: "Build the full-stack experiences that help millions of AWS customers understand and optimize their cloud spending. We own the console surfaces and services behind AWS Cost Explorer, BCM Dashboards, and AWS Budgets — and we're evolving them fast. As an SDE 2, you'll own features end-to-end — from frontend React components to backend Java services to the operational health of what you ship. You'll design solutions to difficult problems: making cost data intuitive at massive scale, building managed dashboard experiences, and migrating millions of customers to modernized console architectures. You won't just implement specs — you'll work directly with product and UX to understand customer pain, propose approaches, and ship iteratively. What makes this role compelling: You'll work across the full stack — React/TypeScript frontends, Java/AWS backend services, CDK infrastructure — with real ownership, not ticket work The problems are genuinely hard: multi-partition deployments, cost allocation at scale, and UX for data that is inherently complex Our team uses AI tools daily as development partners You'll mentor others, lead design reviews, and influence the team's technical direction — this is a role where your voice shapes the architecture This isn't a maintenance role. We're actively rebuilding and modernizing core billing console experiences while launching net-new dashboard and AI-driven cost insight products. You're joining while the hard decisions are still being made."
We need to ensure readability; maybe split into two paragraphs.
Paragraph1: first two sentences up to "modernized console architectures."
Paragraph2: rest.
Let's craft.
Paragraph1: "Build the full-stack experiences that help millions of AWS customers understand and optimize their cloud spending. We own the console surfaces and services behind AWS Cost Explorer, BCM Dashboards, and AWS Budgets — and we're evolving them fast. As an SDE 2, you'll own features end-to-end — from frontend React components to backend Java services to the operational health of what you ship. You'll design solutions to difficult problems: making cost data intuitive at massive scale, building managed dashboard experiences, and migrating millions of customers to modernized console architectures."
Paragraph2: "You won't just implement specs — you'll work directly with product and UX to understand customer pain, propose approaches, and ship iteratively. What makes this role compelling: You'll work across the full stack — React/TypeScript frontends, Java/AWS backend services, CDK infrastructure — with real ownership, not ticket work. The problems are genuinely hard: multi-partition deployments, cost allocation at scale, and UX for data that is inherently complex. Our team uses AI tools daily as development partners. You'll mentor others, lead design reviews, and influence the team's technical direction — this is a role where your voice shapes the architecture. This isn't a maintenance role. We're actively rebuilding and modernizing core billing console experiences while launching net-new dashboard and AI-driven cost insight products. You're joining while the hard decisions are still being made."
Now company/location paragraph: "Amazon Development Center U.S., Inc. – Seattle, WA"
Now responsibilities list.
Now qualifications.
Basic Qualifications items as given.
Preferred Qualifications items.
Skills: list React, TypeScript, Java, AWS, CDK, AI/GenAI tools.
Benefits: include health insurance details, 401(k) matching, paid time off, parental leave, sign-on payments, RSUs.
We need to preserve the benefits text: "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." Also mention sign-on payments and RSUs earlier: "Your Amazon package will include sign-on payments and restricted stock
for prose. We must preserve all substantive information, not invent or summarize away detail. So we need to include details from description, responsibilities, qualifications, benefits, pay. We must remove boilerplate: EEO, accommodation link, etc. Also remove duplicated lines. Also remove application instructions (none). Also remove navigation/cookie etc. We need to ensure we don't include placeholder like "commensurate with experience". Not present. Let's extract content. Description: "Build the full-stack experiences that help millions of AWS customers understand and optimize their cloud spending. We own the console surfaces and services behind AWS Cost Explorer, BCM Dashboards, and AWS Budgets — and we're evolving them fast. As an SDE 2, you'll own features end-to-end — from frontend React components to backend Java services to the operational health of what you ship. You'll design solutions to difficult problems: making cost data intuitive at massive scale, building managed dashboard experiences, and migrating millions of customers to modernized console architectures. You won't just implement specs — you'll work directly with product and UX to understand customer pain, propose approaches, and ship iteratively. What makes this role compelling: You'll work across the full stack — React/TypeScript frontends, Java/AWS backend services, CDK infrastructure — with real ownership, not ticket work The problems are genuinely hard: multi-partition deployments, cost allocation at scale, and UX for data that is inherently complex Our team uses AI tools daily as development partners You'll mentor others, lead design reviews, and influence the team's technical direction — this is a role where your voice shapes the architecture This isn't a maintenance role. We're actively rebuilding and modernizing core billing console experiences while launching net-new dashboard and AI-driven cost insight products. You're joining while the hard decisions are still being made." We can put that under About the role (or maybe a general description). The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should have About the role heading. Responsibilities: list from "Key job responsibilities" bullet points. Let's extract each bullet: - Design and build full-stack features across AWS Cost Explorer, BCM Dashboards, and AWS Budgets — React/TypeScript frontends and Java backend services serving millions of AWS customers. - Own features through the full software lifecycle — from customer problem discovery and technical design through implementation, testing, deployment, and production operations. - Solve difficult problems at scale — cost data visualization, managed dashboard experiences, and console migration for millions of existing customers across multi-partition deployments. - Author technical design documents, lead design reviews, and provide meaningful code reviews that raise the team's code bar. - Drive operational excellence — own alarms, monitoring, runbooks, and on-call rotations for live production services; resolve root causes of systemic issues. - Mentor engineers, onboard new team members, and foster an inclusive environment where diverse perspectives shape technical decisions. - Collaborate with product management and UX to deeply understand customer pain points and translate them into incremental, shippable solutions. - Contribute to team technical strategy and roadmap — help decide where to invest, what to modernize, and what to deprecate. - Write clean, testable, production-ready code using AI-native development practices — leveraging GenAI tools as daily development partners. We'll put each as
for section headings; we can have Qualifications heading and then maybe separate Basic and Preferred as
or
- . We'll list both as
- with items.
Skills: Could list technologies: React, TypeScript, Java, AWS, CDK, AI/GenAI tools. The description mentions those. We'll create a Skills section with
- .
Benefits: The posting includes benefits description: "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." Also mention sign-on payments and RSUs. We'll include that.
Pay: The base salary range: "USA, WA, Seattle - 143,700.00 - 194,400.00 USD annually". Also mention sign-on payments and RSUs but that's part of compensation. We'll include Pay section with that range.
Schedule: Not present, so omit.
We must not repeat job title. Not include Company? Could include as metadata? The instruction says do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we could include a short
for company and location maybe. But not required. We could include a brief paragraph after About the role maybe. But we need to preserve all substantive information; company and location are substantive. We'll include a
after About the role maybe. But we must not create headings for minor metadata. So we can include a
with "Amazon Development Center U.S., Inc. – Seattle, WA". That's fine. Now produce HTML fragment. Structure:
About the role
Build the full-stack experiences ... (the description paragraph(s)). Could be multiple paragraphs but we can combine into one
with line breaks? Better to keep as
for prose; we can have multiple
sentences. We'll split description into maybe two
for readability but still okay. Then maybe a
for company/location. Then
Responsibilities
- ...
Qualifications
- ... maybe separate Basic and Preferred? Could have two
- with headings? But headings would be
not allowed? Only for section headings. We could just list all qualifications in one but differentiate with text. Could add Basic Qualifications: then list items, then Preferred Qualifications:. That's okay inside ? Might be messy. Better to have two each preceded by a indicating type. But that adds extra
not prohibited. We'll do:
Qualifications
Basic Qualifications:
...
Preferred Qualifications:
...
That preserves info.
Then Skills
...
Then Benefits
...
Then Pay
...
Make sure no extra whitespace? It's fine.
Now craft content precisely.
About the role paragraph(s):
We'll take the description block: "Build the full-stack experiences that help millions of AWS customers understand and optimize their cloud spending. We own the console surfaces and services behind AWS Cost Explorer, BCM Dashboards, and AWS Budgets — and we're evolving them fast. As an SDE 2, you'll own features end-to-end — from frontend React components to backend Java services to the operational health of what you ship. You'll design solutions to difficult problems: making cost data intuitive at massive scale, building managed dashboard experiences, and migrating millions of customers to modernized console architectures. You won't just implement specs — you'll work directly with product and UX to understand customer pain, propose approaches, and ship iteratively. What makes this role compelling: You'll work across the full stack — React/TypeScript frontends, Java/AWS backend services, CDK infrastructure — with real ownership, not ticket work The problems are genuinely hard: multi-partition deployments, cost allocation at scale, and UX for data that is inherently complex Our team uses AI tools daily as development partners You'll mentor others, lead design reviews, and influence the team's technical direction — this is a role where your voice shapes the architecture This isn't a maintenance role. We're actively rebuilding and modernizing core billing console experiences while launching net-new dashboard and AI-driven cost insight products. You're joining while the hard decisions are still being made."
We need to ensure readability; maybe split into two paragraphs.
Paragraph1: first two sentences up to "modernized console architectures."
Paragraph2: rest.
Let's craft.
Paragraph1: "Build the full-stack experiences that help millions of AWS customers understand and optimize their cloud spending. We own the console surfaces and services behind AWS Cost Explorer, BCM Dashboards, and AWS Budgets — and we're evolving them fast. As an SDE 2, you'll own features end-to-end — from frontend React components to backend Java services to the operational health of what you ship. You'll design solutions to difficult problems: making cost data intuitive at massive scale, building managed dashboard experiences, and migrating millions of customers to modernized console architectures."
Paragraph2: "You won't just implement specs — you'll work directly with product and UX to understand customer pain, propose approaches, and ship iteratively. What makes this role compelling: You'll work across the full stack — React/TypeScript frontends, Java/AWS backend services, CDK infrastructure — with real ownership, not ticket work. The problems are genuinely hard: multi-partition deployments, cost allocation at scale, and UX for data that is inherently complex. Our team uses AI tools daily as development partners. You'll mentor others, lead design reviews, and influence the team's technical direction — this is a role where your voice shapes the architecture. This isn't a maintenance role. We're actively rebuilding and modernizing core billing console experiences while launching net-new dashboard and AI-driven cost insight products. You're joining while the hard decisions are still being made."
Now company/location paragraph: "Amazon Development Center U.S., Inc. – Seattle, WA"
Now responsibilities list.
Now qualifications.
Basic Qualifications items as given.
Preferred Qualifications items.
Skills: list React, TypeScript, Java, AWS, CDK, AI/GenAI tools.
Benefits: include health insurance details, 401(k) matching, paid time off, parental leave, sign-on payments, RSUs.
We need to preserve the benefits text: "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." Also mention sign-on payments and RSUs earlier: "Your Amazon package will include sign-on payments and restricted stock
- but differentiate with text. Could add Basic Qualifications: then list items, then Preferred Qualifications:. That's okay inside
- ? Might be messy. Better to have two
- each preceded by a
indicating type. But that adds extra
not prohibited. We'll do:
Qualifications
Basic Qualifications:
- ...
Preferred Qualifications:
- ...
Skills
- ...
Benefits
...
ThenPay
...
Make sure no extra whitespace? It's fine. Now craft content precisely. About the role paragraph(s): We'll take the description block: "Build the full-stack experiences that help millions of AWS customers understand and optimize their cloud spending. We own the console surfaces and services behind AWS Cost Explorer, BCM Dashboards, and AWS Budgets — and we're evolving them fast. As an SDE 2, you'll own features end-to-end — from frontend React components to backend Java services to the operational health of what you ship. You'll design solutions to difficult problems: making cost data intuitive at massive scale, building managed dashboard experiences, and migrating millions of customers to modernized console architectures. You won't just implement specs — you'll work directly with product and UX to understand customer pain, propose approaches, and ship iteratively. What makes this role compelling: You'll work across the full stack — React/TypeScript frontends, Java/AWS backend services, CDK infrastructure — with real ownership, not ticket work The problems are genuinely hard: multi-partition deployments, cost allocation at scale, and UX for data that is inherently complex Our team uses AI tools daily as development partners You'll mentor others, lead design reviews, and influence the team's technical direction — this is a role where your voice shapes the architecture This isn't a maintenance role. We're actively rebuilding and modernizing core billing console experiences while launching net-new dashboard and AI-driven cost insight products. You're joining while the hard decisions are still being made." We need to ensure readability; maybe split into two paragraphs. Paragraph1: first two sentences up to "modernized console architectures." Paragraph2: rest. Let's craft. Paragraph1: "Build the full-stack experiences that help millions of AWS customers understand and optimize their cloud spending. We own the console surfaces and services behind AWS Cost Explorer, BCM Dashboards, and AWS Budgets — and we're evolving them fast. As an SDE 2, you'll own features end-to-end — from frontend React components to backend Java services to the operational health of what you ship. You'll design solutions to difficult problems: making cost data intuitive at massive scale, building managed dashboard experiences, and migrating millions of customers to modernized console architectures." Paragraph2: "You won't just implement specs — you'll work directly with product and UX to understand customer pain, propose approaches, and ship iteratively. What makes this role compelling: You'll work across the full stack — React/TypeScript frontends, Java/AWS backend services, CDK infrastructure — with real ownership, not ticket work. The problems are genuinely hard: multi-partition deployments, cost allocation at scale, and UX for data that is inherently complex. Our team uses AI tools daily as development partners. You'll mentor others, lead design reviews, and influence the team's technical direction — this is a role where your voice shapes the architecture. This isn't a maintenance role. We're actively rebuilding and modernizing core billing console experiences while launching net-new dashboard and AI-driven cost insight products. You're joining while the hard decisions are still being made." Now company/location paragraph: "Amazon Development Center U.S., Inc. – Seattle, WA" Now responsibilities list. Now qualifications. Basic Qualifications items as given. Preferred Qualifications items. Skills: list React, TypeScript, Java, AWS, CDK, AI/GenAI tools. Benefits: include health insurance details, 401(k) matching, paid time off, parental leave, sign-on payments, RSUs. We need to preserve the benefits text: "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." Also mention sign-on payments and RSUs earlier: "Your Amazon package will include sign-on payments and restricted stock