Software Development Manager, S3 - Simple Storage Service
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. No Job ID etc. Remove boilerplate like EEO, accommodation, etc. Also remove application instructions. Must preserve all substantive info. We need to parse the description. Let's extract sections: - About the role: The initial paragraph describing role: "Amazon S3 handles hundreds of millions of requests per second...". That's description. Could be About the role. - Responsibilities: The bullet list after "Key job responsibilities". Items: Lead, grow, and develop a team...; Own software deployment...; Rewrite and modernize...; Work across multiple S3 teams...; Recruit and retain top engineering talent... - Requirements: Basic Qualifications list. - Qualifications: Preferred Qualifications list. - Skills: Not explicitly listed; maybe we can infer from qualifications? But we should only include if posting has real specific content. There's no separate Skills section. So we omit Skills. - Benefits: The paragraph about benefits: "Amazon also offers comprehensive benefits including health insurance...". Also mention sign-on payments and RSUs. Also mention base salary range? That's Pay. - Pay: The base salary range: "USA, VA, Arlington - 184,900.00 - 250,200.00 USD annually". Also mention sign-on payments and RSUs. So we can include Pay section with that info. - Schedule: Not mentioned. So omit. We also need to include maybe a short paragraph for metadata like location? The location is in the Pay line? Actually location appears with salary range: "USA, VA, Arlington - 184,900.00 - 250,200.00 USD annually". We could include location in About the role or a separate meta paragraph. But instructions: 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 location and maybe company? But we already have location in Pay. Could also include a short paragraph about company: "Company - Amazon Development Center U.S., Inc." Might be considered minor metadata; we could fold into a short
after About the role or before sections. However we need to preserve ALL substantive information. Location is substantive; company name maybe less but still. We'll include a short
after the initial description maybe. We must not include boilerplate: EEO, accommodation, etc. Also remove duplicated lines. Let's craft HTML:
About the role
Amazon S3 handles hundreds of millions of requests per second for customers around the world — and every one of those requests runs on software your team ships. As a Software Development Manager for S3 Foundations, you will own how new S3 software is built, validated, released, and observed across every AWS Region on the planet, at a scale almost no other engineering role can offer. Amazon Simple Storage Service (S3) provides industry-leading scalability, data availability, security, and performance for object storage. Customers of all sizes, from day-one startups to the world's largest enterprises, use Amazon S3 to deliver next-generation applications ranging from data analytics to AI to photo and video archives. While S3 has seen tremendous growth since launch in 2006, we are still in the early stages of realizing its full potential. The S3 Foundations team is the foundation and force multiplier for S3's front-end engineering organization. We own the platform that safely delivers software to the fleet processing every S3 API request worldwide, from pre-production validation and qualification systems that catch problems before customers ever see them, to the post-processing services — metering, API events, and request logging — that power billing, auditing, and analytics for millions of AWS customers. When your team does its job well, customers get new S3 capabilities sooner. This is a hands-on leadership role at the intersection of massive-scale distributed systems, developer experience, and operational excellence. You will: Own the roadmap for one of the highest-leverage platforms in S3 delivering front-end request processing. Drive an ambitious multi-year modernization agenda — increasing release frequency, compressing worldwide deployment times, hardening automated deployment safety, and re-architecting legacy services into modern, independently deployable systems. Build the self-service "builder experience" platform that lets S3 engineers validate, deploy, and observe their changes without waiting on anyone — measured by how much faster and safer they ship. Make AI a central pillar of how your team builds and operates: AI-assisted development as standard practice, spec-driven modernization of legacy services, automated on-call assistants, and create agents that handle routine requests. Success in this role requires a leader who can move fluidly between weighing in on the engineering details of high-throughput distributed systems, prioritizing across a portfolio of platform programs, partnering with senior engineers and leaders across S3, and growing a team of talented builders. Because your platform is on the path of every S3 request worldwide, a passion and discipline around operational excellence, security, and availability is essential. Come build with us and make history with Amazon S3!
But note that the "You will:" list is actually responsibilities; we might want to move that to Responsibilities section. The About the role should be a summary, not include the bullet list. However the instructions: preserve ALL substantive information; we can split. The initial paragraph up to "Come build with us and make history with Amazon S3!" includes the "You will:" list which is actually responsibilities. Better to separate: About the role: description of role and impact. Responsibilities: the bullet list after "Key job responsibilities". Also there is a list earlier in the description that includes "You will:" which duplicates responsibilities. We need to avoid duplication. The posting includes both a narrative and then a "Key job responsibilities" list. We should keep the responsibilities list as is, and maybe keep the narrative without the "You will:" list to avoid duplication. However the narrative includes the "You will:" list; if we remove it we might lose some content that is not duplicated elsewhere? Let's see: The responsibilities list after "Key job responsibilities" includes: - Lead, grow, and develop a team of software engineers, fostering a culture of technical excellence, deep ownership, and customer obsession. - Own software deployment to one of the largest server fleets in the world, driving release velocity and safety for the systems that process every S3 request. - Rewrite and modernize existing software and tune systems to drive efficiencies at massive scale, with outsized impact on AWS's cost, performance, and operations. - Work across multiple S3 teams, coordinating feature validation and delivery for S3's front-end organization. - Recruit and retain top engineering talent, and raise the bar on operational excellence as S3 continues to scale. The earlier "You will:" list includes: - Own the roadmap for one of the highest-leverage platforms in S3 delivering front-end request processing. - Drive an ambitious multi-year modernization agenda — increasing release frequency, compressing worldwide deployment times, hardening automated deployment safety, and re-architecting legacy services into modern, independently deployable systems. - Build the self-service "builder experience" platform that lets S3 engineers validate, deploy, and observe their changes without waiting on anyone — measured by how much faster and safer they ship. - Make AI a central pillar of how your team builds and operates: AI-assisted development as standard practice, spec-driven modernization of legacy services, automated on-call assistants, and create agents that handle routine requests. - Success in this role requires a leader who can move fluidly between weighing in on the engineering details of high-throughput distributed systems, prioritizing across a portfolio of platform programs, partnering with senior engineers and leaders across S3, and growing a team of talented builders. - Because your platform is on the path of every S3 request worldwide, a passion and discipline around operational excellence, security, and availability is essential. - Come build with us and make history with Amazon S3! These are not exactly same as the responsibilities list; they include roadmap, AI, builder experience, etc. So we should keep them as part of responsibilities (maybe as part of the responsibilities section). The "Key job responsibilities" list is a subset; we could combine both lists into one responsibilities section. To avoid duplication, we can merge unique items. Thus responsibilities section will contain a- with items from both lists, ensuring no duplicates.
Let's extract unique responsibilities:
From "You will:" list:
1. Own the roadmap for one of the highest-leverage platforms in S3 delivering front-end request processing.
2. Drive an ambitious multi-year modernization agenda — increasing release frequency, compressing worldwide deployment times, hardening automated deployment safety, and re-architecting legacy services into modern, independently deployable systems.
3. Build the self-service "builder experience" platform that lets S3 engineers validate, deploy, and observe their changes without waiting on anyone — measured by how much faster and safer they ship.
4. Make AI a central pillar of how your team builds and operates: AI-assisted development as standard practice, spec-driven modernization of legacy services, automated on-call assistants, and create agents that handle routine requests.
5. Success in this role requires a leader who can move fluidly between weighing in on the engineering details of high-throughput distributed systems, prioritizing across a portfolio of platform programs, partnering with senior engineers and leaders across S3, and growing a team of talented builders.
6. Because your platform is on the path of every S3 request worldwide, a passion and discipline around operational excellence, security, and availability is essential.
7. Come build with us and make history with Amazon S3! (maybe tagline, could be considered fluff but it's substantive? It's a call to action; we could keep but maybe it's not a responsibility. Might be considered boilerplate? It's a motivational line; but it's part of description. Might keep in About the role.)
From "Key job responsibilities":
1. Lead, grow, and develop a team of software engineers, fostering a culture of technical excellence, deep ownership, and customer obsession.
2. Own software deployment to one of the largest server fleets in the world, driving release velocity and safety for the systems that process every S3 request.
3. Rewrite and modernize existing software and tune systems to drive efficiencies at massive scale, with outsized impact on AWS's cost, performance, and operations.
4. Work across multiple S3 teams, coordinating feature validation and delivery for S3's front-end organization.
5. Recruit and retain top engineering talent, and raise the bar on operational excellence as S3 continues to scale.
Now note some overlap: "Lead, grow, and develop a team" similar to "growing a team of talented builders" in #5 of You will list. Also "Own software deployment" similar to "Own the roadmap"? Not same. We'll keep both but maybe deduplicate similar meaning.
We could keep all items; duplication minor but acceptable? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is okay if it's in original; but we should avoid repeating same sentence exactly. We have similar but not identical. We'll keep both.
Now Basic Qualifications list:
- 3+ years of engineering team management experience
- 7+ years of working directly within engineering teams experience
- 3+ years of designing or architecting (design patterns, reliability and scaling) of new and existing systems experience
- 8+ years of leading the definition and development of multi tier web services experience
- Knowledge of engineering practices and patterns for the full software/hardware/networks development life cycle, including coding standards, code reviews, source control management, build processes, testing, certification, and livesite operations
- Experience partnering with product or program management teams
Preferred Qualifications list:
- Experience in communicating with users, other technical teams, and senior leadership to collect requirements, describe software product features, technical designs, and product strategy
- Experience in recruiting, hiring, mentoring/coaching and managing teams of Software Engineers to improve their skills, and make them more effective, product software engineers
Now Benefits: The paragraph: "Amazon also offers comprehensive benefits including health insurance (medical, dental, vision