Software Development Engineer, Amazon Customer Service
Amazon · Austin, TX · 1 mo ago
ConsultingFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the description.
First, job title is not needed as heading.
We need to include About the role: likely the description paragraph about team and role.
Responsibilities: list of duties.
Requirements: basic qualifications.
Qualifications: maybe preferred qualifications? Actually they have Basic Qualifications and Preferred Qualifications. Could map to Requirements and Qualifications.
Skills: maybe list of technologies? Could be from qualifications.
Benefits: they mention benefits: health insurance, 401(k) matching, paid time off, parental leave, etc. Also mention sign-on payments and RSUs.
Pay: they give salary range: USA, TX, Austin - 143,700.00 - 194,400.00 USD annually.
Schedule: not mentioned. So we should not include Schedule section.
We need to remove boilerplate: EEO, accommodation link, etc. Also remove duplicated lines, application instructions, etc.
We need to preserve all substantive info.
Let's extract sections.
About the role: The first paragraph(s) describing the team and role: "Description On the Customer Service -Aria team, part of Amazon’s Customer Service (CS) organization, we redefine the customer contact experience by exposing a voice-based contact channel (AVA) which using an automated assistant (voicebot) to better understand the customer problem and guide them to resolution via automation. We focus on building scalable platforms and systems for customers and associates to power automation globally across many languages for the millions of customers and thousands of associates that use our products in many marketplaces every day. We also invest in experimentation to identify new and inventive ways to build chat/touch/voice experiences that aim to delight customers. As a SDE on this team, you will collaborate with other Senior Software Engineers to drive improvements to our technology, design and develop new services and solutions, and build and track metrics to ensure high quality results. Your solutions will provide the ultimate customer service experience needed to anticipate and resolve customer's questions using the Chat platform. You will have the opportunity to work with business partners and leadership, influence and drive product vision and lead the design of our systems. As a SDE in CS-Aria, you will take part in the implementation and delivery of contact center systems built on top of our next-generation routing system, leveraging the power of Generative AI (GenAI) and Machine Learning for improved intents and routing signals, and preserving customer contact journey data. You will work cross functionally with partners to take the product from concept to customer release while ensuring the highest level of quality for your deliverables, managing one of the worlds largest and most complex customer service organizations."
That's a lot. We'll put that in
under About the role. Responsibilities: The "Key job responsibilities" bullet list: "Collaborate with experienced cross-disciplinary Amazonians to conceive, design, and bring innovative products and services to market. Design and build innovative technologies in a large distributed computing environment, and help lead fundamental changes in the industry. Ability to design and code the right solutions starting with broadly defined problems. Work in an agile environment to deliver high-quality software. We use SCRUM, test-driven development, and continuous deployment to deliver projects based on realistic timelines and resource constraints. On-call rotation to support the services owned by the Software team". Also "A day in the life" paragraph: "You will work closely with senior leaders across cross-functional stakeholder teams within Amazon to drive collaboration and influence them to prioritize projects, meet objects and adhere to business plans towards shared objectives." Also the encouraging line about qualifications: "If you are not sure that every qualification on the list above describes you exactly, we'd still love to hear from you! At Amazon, we value people with unique backgrounds, experiences, and skillsets. If you’re passionate about this role and want to make an impact on a global scale, please apply!" That's more like encouragement, maybe not responsibility. We'll keep responsibilities as the bullet list and day in the life. We'll format as
- items. Requirements: Basic Qualifications list: "Bachelor's degree or foreign equivalent in Computer Science, Engineering, Mathematics, or a related field", "3+ years of non-internship professional software development experience", "2+ years of non-internship design or architecture (design patterns, reliability and scaling) of new and existing systems experience", "1+ years of software development engineer or related occupational experience", "1+ years of designing and developing large-scale, multi-tiered, multi-threaded, embedded or distributed software applications, tools, systems, and services using: C#, C++, Java, or Perl experience", "1+ years of Object Oriented Design experience". We'll put each as
- . Qualifications: Preferred Qualifications: "3+ years of full software development life cycle, including coding standards, code reviews, source control management, build processes, testing, and operations experience", "Bachelor's degree in computer science or equivalent". We'll put as
- .
Skills: Could be derived from qualifications: maybe list of languages: C#, C++, Java, Perl; also OOD, distributed systems, etc. But we might not need a Skills section if we already have Requirements and Qualifications. However the instruction says to use sections only when posting has real specific content. The posting does mention specific skills: C#, C++, Java, Perl; OOD; distributed systems; SCRUM; TDD; CI/CD; etc. We could create a Skills section with those. But we already have them in Requirements/Qualifications. To avoid duplication, maybe we skip Skills section. However we need to decide: The instruction says prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one? But they asked to use headings for those specific categories. We'll include Requirements and Qualifications as separate sections.
Benefits: They list: "sign-on payments and restricted stock units (RSUs)", "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", "parental leave". Also link to benefits page. We'll include those as bullet list.
Pay: Salary range: "USA, TX, Austin - 143,700.00 - 194,400.00 USD annually". We'll put in
. Schedule: none, so omit. We must not include Job ID, etc. We must not include boilerplate like EEO, accommodation link, etc. We must not repeat job title as heading. We must output only HTML fragment. Let's craft. Structure:
About the role
... (the description paragraph(s) combined into maybe two paragraphs? We'll keep as one paragraph but could split for readability. It's okay.)
Responsibilities
- Collaborate with experienced cross-disciplinary Amazonians to conceive, design, and bring innovative products and services to market.
- Design and build innovative technologies in a large distributed computing environment, and help lead fundamental changes in the industry.
- Ability to design and code the right solutions starting with broadly defined problems.
- Work in an agile environment to deliver high-quality software. We use SCRUM, test-driven development, and continuous deployment to deliver projects based on realistic timelines and resource constraints.
- On-call rotation to support the services owned by the Software team.
- You will work closely with senior leaders across cross-functional stakeholder teams within Amazon to drive collaboration and influence them to prioritize projects, meet objectives and adhere to business plans towards shared objectives.
Requirements
- Bachelor's degree or foreign equivalent in Computer Science, Engineering, Mathematics, or a related field
- 3+ years of non-internship professional software development experience
- 2+ years of non-internship design or architecture (design patterns, reliability and scaling) of new and existing systems experience
- 1+ years of software development engineer or related occupational experience
- 1+ years of designing and developing large-scale, multi-tiered, multi-threaded, embedded or distributed software applications, tools, systems, and services using: C#, C++, Java, or Perl experience
- 1+ years of Object Oriented Design experience
Qualifications
- 3+ years of full software development life cycle, including coding standards, code reviews, source control management, build processes, testing, and operations experience
- Bachelor's degree in computer science or equivalent
Benefits
- Sign-on payments and restricted stock units (RSUs)
- Comprehensive health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance, 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
- Parental leave
Pay
USA, TX, Austin - 143,700.00 - 194,400.00 USD annually
We should not include any extra text. Check for any duplicated lines: we removed the "About The Team" heading? Actually we used About the role; we could incorporate About The Team content into About the role. The About The Team paragraph: "The mission of the CS-Aria team within Customer Service is to create earth’s best customer service solutions through empowering our customers to utilize automation to resolve their issues quickly and efficiently. You will be a key component of our leadership team and will influence our science and engineering teams to deliver World-Wide Self-Service Automation (SSA) products based on generative AI." This is also substantive. Should we include it? It's part of description. We could merge into About the role paragraph. Let's add that after the first description. Thus About the role paragraph will be longer: combine the initial description and the About The Team mission. Let's craft About the role paragraph: "On the Customer Service -Aria team, part of Amazon’s Customer Service (CS) organization, we redefine the customer contact experience by exposing a voice-based contact channel (AVA) which using an automated assistant (voicebot) to better understand the customer problem and guide them to resolution via automation. We focus on building scalable platforms and systems for customers and associates to power automation globally across many languages for the millions of customers and thousands of associates that use our products in many marketplaces every day. We also invest in experimentation to identify new and inventive ways to build chat/touch/voice experiences that aim to delight customers. As a SDE on this team, you will collaborate with other Senior Software Engineers to drive improvements to our technology, design and develop new services and solutions, and build and track metrics to ensure high quality results. Your solutions will provide the ultimate customer service experience needed to anticipate and resolve customer's questions using the Chat platform. You will have the opportunity to work with business partners and leadership, influence and drive product vision and lead the design of our systems. As a SDE in CS-Aria, you will take part in the implementation and delivery of contact center systems built on top of our next-generation routing system, leveraging the power of Generative AI (GenAI) and Machine Learning for improved intents and routing signals, and preserving customer contact journey data. You will work cross