Software Development Engineer, Lambda Developer Experience

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must not repeat job title as heading. No Job ID. Remove boilerplate like EEO, legal, etc. Keep substantive info. Let's parse the description. First paragraph: "Does making mobile and web developers lives better intrigue you? Have you felt like you're not appreciated at your current team? Come join the AWS Amplify team! At AWS Amplify, we're working to build a set of tools and services that can be used together or on their own, to help front-end web and mobile developers build scalable, full stack applications, powered by AWS. With Amplify, you can configure app backends and connect your app in minutes, deploy static web apps in a few clicks, and easily manage app content outside the AWS console. We're right at the start of a comprehensive roadmap to deliver the functionality and features our customers are asking for and delight them with functionality they couldn't even imagine. We're passionate about what our customers are building, so we can offer them the right tools to be successful. If you are as passionate as us about app development and providing developers with the latest and greatest tools to build and host their apps, join the AWS Amplify team!" That's about the role/team description. Could be "About the role". Then "As a Member Of The Team, You Will" bullet list: Work closely with product team and other AWS teams to deliver on the team’s technical vision; Influence technical strategy to build products developers will love; Drive team discussions on system architecture and component design; Lead development and launch of core features and products; Participate in all stages of the software development cycle, including design and development of significant new architectures and features; Participate in estimation and sprint planning; Mentor junior team members; Conduct interviews and help hire great talent for the team; Mentor (duplicate). That's responsibilities. Then "Mentor" section: "We have a formal mentor search application that lets you find a mentor that works best for you based on location, job family, job level etc. Your manager can also help you find a mentor or two, because two is better than one. In addition to formal mentors, we work and train together so that we are always learning from one another, and we celebrate and support the career progression of our team members." This could be part of Benefits or maybe "Mentorship" but not a required heading; we can incorporate into Benefits or maybe "Benefits". But we have a Benefits heading later. Then "Inclusion" section: talk about inclusion, employee-led affinity groups, benefit offerings, learning experiences, CORE, AmazeCon, Leadership Principles. This is more about culture; could be part of Benefits or maybe separate but we only have headings defined. Could put under Benefits? But Benefits is for compensation/benefits. Inclusion maybe not a standard heading; but we could include under Benefits? Might be better to include under Benefits as part of culture benefits. However we must only include sections when posting has real specific content. It does have inclusion content. But we don't have a heading for Inclusion in allowed list. The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map inclusion content to one of these, maybe Benefits (since it's about employee benefits and culture). Or we could create a separate section but not allowed. So we should incorporate inclusion content into Benefits section. Then "Work-Life Balance": talk about flexible schedule. That could go under Benefits or Schedule. Since Schedule heading is allowed, we could put schedule info there. The posting says: "Our team also puts a high value on work-life balance. Striking a healthy balance between your personal and professional life is crucial to your happiness and success here, which is why we aren’t focused on how many hours you spend at work or online. Instead, we’re happy to offer a flexible schedule so you can have a more productive and well-balanced life—both in and outside of work." That's schedule info. So we can put under Schedule. Then "Amazon is committed to a diverse and inclusive workplace. Amazon is an equal opportunity employer..." That's boilerplate EEO, should be removed. Then "Basic Qualifications" list: 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; Bachelor's degree or foreign equivalent in Computer Science, Engineering, Mathematics, or a related field; Experience programming with at least one software programming language. That's Requirements/Qualifications. The headings: Requirements and Qualifications both allowed. We need to decide what goes where. Usually Requirements = basic qualifications, Qualifications = preferred qualifications. So we can put basic qualifications under Requirements, and preferred qualifications under Qualifications. Then "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. Then later: "Amazon is an equal opportunity employer and does not discriminate on the basis of protected veteran status, disability, or other legally protected status." That's boilerplate, remove. Then: "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 accommodation info, could be considered part of Benefits? Might be considered part of Benefits (accommodation). But it's more legal/EEO; but we can keep as part of Benefits? Might be considered boilerplate but it's about accommodation. The instruction says remove EEO/equal-opportunity/... boilerplate. This is accommodation info, maybe still considered EEO? It's about disability accommodation. Might be considered boilerplate. Safer to remove. Then: "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." That's Pay and Benefits. So we need Pay section with salary range and sign-on payments, RSUs. Benefits section with health insurance, 401(k) matching, paid time off, parental leave, plus maybe inclusion and accommodation? We'll keep benefits as described. Then location: "USA, WA, Seattle - 143,700.00 - 194,400.00 USD annually". That's Pay. Then "Company - Amazon Development Center U.S., Inc. Job ID: A10539315". Remove Job ID. Now we need to output HTML fragment with headings

for each section, and

• for lists,

  for prose. We must not include empty sections. Let's decide sections: - About the role: intro paragraph(s) describing team and mission. - Responsibilities: the bullet list under "As a Member Of The Team, You Will". - Requirements: basic qualifications list. - Qualifications: preferred qualifications list. - Benefits: include health insurance, 401(k) matching, paid time off, parental leave, plus maybe inclusion and work-life balance? But we have Schedule separate. - Pay: salary range, sign-on payments, RSUs. - Schedule: flexible schedule info. We might also include Inclusion content under Benefits or maybe as part of Benefits. But we already have Benefits with health etc. Could add inclusion as part of Benefits bullet list. But we need to avoid duplication and boilerplate. Let's extract inclusion content: "We have ten employee-led affinity groups, reaching 40,000 employees in over 190 chapters globally. We have innovative benefit offerings, and we host annual and ongoing learning experiences, including our Conversations on Race and Ethnicity (CORE) and AmazeCon (gender diversity) conferences. Amazon’s culture of inclusion is reinforced within our 14 Leadership Principles, which remind team members to seek diverse perspectives, learn and be curious, and earn trust." That's substantive; we can include under Benefits as bullet points. Work-Life Balance / Schedule: "Our team also puts a high value on work-life balance. Striking a healthy balance between your personal and professional life is crucial to your happiness and success here, which is why we aren’t focused on how many hours you spend at work or online. Instead, we’re happy to offer a flexible schedule so you can have a more productive and well-balanced life—both in and outside of work." We'll put under Schedule as a paragraph. Now Benefits: we have health insurance details, 401(k) matching, paid time off, parental leave, plus inclusion items. We need to format as

  • for list items. We must not include "Learn more about our benefits at https://amazon.jobs/en/benefits." That's a link; could be included as a paragraph? It's not boilerplate; it's a reference. Could keep as a

    with link? But we are to output only HTML fragment, we can include maybe. The instruction didn't forbid links. It's okay. But we need to preserve all substantive information; we can include that sentence as a

    . Now Pay: "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." plus the salary range line. We can make a

    for the prose, and maybe a

    for the salary range. Now let's craft HTML. We'll start with

    About the role

    then

    ... (the intro paragraph(s)). Might need to split into multiple paragraphs but we can combine. Intro text: "Does making mobile and web developers lives better intrigue you? Have you felt like you're not appreciated at your current team? Come join the AWS Amplify team! At AWS Amplify, we're working to build a set of tools and services that can be used together or on their own, to help front-end web and mobile developers build scalable, full stack applications, powered by AWS. With Amplify, you can configure app backends and connect your app in minutes, deploy static web apps in a few clicks, and easily manage app content outside the AWS console. We're right at the start of a comprehensive roadmap to deliver the functionality and features our customers are asking for and delight them with functionality they couldn't even imagine. We're passionate about what our customers are building, so we can offer them the right tools to be successful. If you are as passionate as us about app development and providing developers with the latest and greatest tools to build and host their apps, join the AWS Amplify team!" That's one paragraph. Now Responsibilities:

    Responsibilities

    then
    • items. List items: - Work closely with the product team and other AWS teams to deliver on the team’s technical vision - Influence technical strategy to build products developers will love - Drive team discussions on system architecture and component design -