Software Development Engineer, AWS Lambda

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 must not repeat job title. Must not include Job ID. Must remove boilerplate like EEO, accommodations, etc. Must preserve substantive info. Let's parse description: - Intro paragraph about serverless, Lambda, data plane team looking for software engineer, collaborative team, grow Lambda service tenfold, secure, performant, observable. Traits: creativity, empathy, optimism. Thrive if interested in large scale fault-tolerant distributed systems, low latency request processing, p100 anomalies. Capable in one or more programming languages, open to learning new ones. Include customer experience when discussing engineering alternatives, value creating APIs that make "The right thing, the easy thing." Value operational sustainability, advocate for eliminating flaky tests. Think having fun goes together with tackling hard problems like supercomputing, high availability, building loosely coupled gRPC-based microservices while securely and reliably handling massive traffic with millisecond latency. That's description of role/responsibilities. 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 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 benefits paragraph: Amazon is equal opportunity employer... (we must remove EEO boilerplate). Then inclusive culture... (maybe keep? It's generic but maybe considered boilerplate. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove EEO statements. The inclusive culture statement maybe also boilerplate but not explicitly EEO. Might be considered part of company culture but could be kept? Safer to remove as it's generic. However we need to preserve benefits: they mention base salary range, sign-on payments and RSUs, final compensation determined based on experience, qualifications, location. Amazon also offers comprehensive benefits including health insurance (list), 401(k) matching, paid time off, parental leave. Learn more about benefits at URL. Also location: USA, WA, Seattle - salary range. We need sections: About the role (maybe intro), Responsibilities (maybe the traits and tasks), Requirements (basic qualifications), Qualifications (preferred qualifications?), Skills (maybe programming languages?), Benefits, Pay, Schedule. We need to decide which sections have real specific content. - About the role: we have introductory paragraph describing team and mission. Could be About the role. - Responsibilities: we have description of what you'll do: work on Lambda data plane, grow service tenfold, secure, performant, observable, creativity, empathy, optimism, interest in large scale fault-tolerant distributed systems, low latency request processing, p100 anomalies, capable in programming languages, open to learning new ones, include customer experience when discussing engineering alternatives, value creating APIs that make "The right thing, the easy thing.", value operational sustainability, advocate for eliminating flaky tests, think having fun goes together with tackling hard problems like supercomputing, high availability, building loosely coupled gRPC-based microservices while securely and reliably handling massive traffic with millisecond latency. That's responsibilities. - Requirements: Basic Qualifications list. - Qualifications: Preferred Qualifications list. - Skills: maybe we could list programming languages: C#, C++, Java, Perl, plus ability to learn new ones. Could be a Skills section. - Benefits: comprehensive benefits list. - Pay: base salary range, sign-on payments, RSUs. - Schedule: not mentioned; we should not create Schedule section if not present. We must not include placeholder text like "commensurate with experience". We have specific salary range. We must not repeat job title. We must not include Job ID. We must not include application instructions. We must not include EEO boilerplate. We must not include navigation etc. Thus produce HTML with sections:

About the role

...

etc. For lists: use

• for any list of duties/requirements/benefits. We need to decide what goes into each section. About the role: maybe a paragraph summarizing the team and mission. Responsibilities: bullet list of duties. Requirements: bullet list of basic qualifications. Qualifications: bullet list of preferred qualifications. Skills: maybe bullet list of programming languages and ability to learn new ones. Benefits: bullet list of benefits. Pay: maybe paragraph with salary range and sign-on payments/RSUs. Schedule: omit. Let's extract specifics. About the role paragraph: "Serverless technologies are dramatically changing the business landscape for AWS customers large and small. AWS Lambda launched the serverless movement and is at the heart of AWS’s serverless portfolio enabling customers to run everything from Alexa commands to massively scaled services driving Fortune 100 companies. AWS Lambda's data plane team is looking for software engineer who wants to work on a global scale service with a collaborative team. We will work together to grow the Lambda service tenfold and provide increasingly secure, performant, and observable serverless technology." That's good. Responsibilities bullet list: - Exhibit creativity, empathy, and optimism as we push the boundaries of serverless computing in the cloud. - Thrive in large scale, fault-tolerant distributed systems, low latency request processing, and p100 anomalies. - Be capable in one or more programming languages and open to learning new ones. - Include customer experience when discussing engineering alternatives and value creating APIs that make "The right thing, the easy thing." - Value operational sustainability and advocate for eliminating flaky tests as soon as possible. - Think having fun goes together with tackling hard problems like supercomputing, high availability, and building loosely coupled gRPC-based microservices while securely and reliably handling massive traffic with millisecond latency. We could also include "Work together to grow the Lambda service tenfold and provide increasingly secure, performant, and observable serverless technology." but that's more about role. Maybe keep responsibilities as above. Requirements bullet list (basic qualifications): - 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 - 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 Preferred Qualifications bullet list: - 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 Skills bullet list: maybe programming languages: C#, C++, Java, Perl; ability to learn new languages; experience with OOD; distributed systems; gRPC-based microservices; low latency request processing; etc. But we could keep skills minimal: "C#, C++, Java, Perl; ability to learn new programming languages". However we already have those in requirements. Might be redundant. But we can still include a Skills section highlighting technical skills: "C#, C++, Java, Perl; distributed systems; low latency request processing; gRPC-based microservices; object-oriented design". But we must not invent details not in posting. The posting mentions those in responsibilities and qualifications. It's okay to extract. Benefits bullet list: from paragraph: "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? Those are compensation, not benefits. We'll keep benefits as health insurance etc. Pay paragraph: "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. USA, WA, Seattle - 143,700.00 - 194,400.00 USD annually" We need to include that. We must not include the URL for benefits. We must not include the equal opportunity employer paragraph. We must not include the accommodation link. We must not include the company name? It's okay to keep maybe but not required. The instruction: do not put Job ID/requisition numbers as headings — fold minor metadata into a short

  or drop it. So we could include company name in a short p maybe but it's minor metadata. Could drop it. Safer to drop. Thus final HTML:

  About the role

  Serverless technologies are dramatically changing the business landscape for AWS customers large and small. AWS Lambda launched the serverless movement and is at the heart of AWS’s serverless portfolio enabling customers to run everything from Alexa commands to massively scaled services driving Fortune 100 companies. AWS Lambda's data plane team is looking for a software engineer who wants to work on a global scale service with a collaborative team. We will work together to grow the Lambda service tenfold and provide increasingly secure, performant, and observable serverless technology.

  Responsibilities

  • Exhibit creativity, empathy, and optimism as we push the boundaries of serverless computing in the cloud.
  • Thrive in large scale, fault‑tolerant distributed systems, low latency request processing, and p100 anomalies.
  • Be capable in one or more programming languages and open to learning new ones.
  • Include customer experience when discussing engineering alternatives and value creating APIs that make “The right thing, the easy thing.”
  • Value operational sustainability and advocate for eliminating flaky tests as soon as possible.
  • Think having fun goes together with tackling hard problems like supercomputing, high availability, and building loosely coupled gRPC‑based microservices while securely and reliably handling massive traffic with millisecond latency.

  Requirements

  • 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
  • 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

  Qualifications

  • 3+ years of full software development life cycle, including coding standards, code reviews, source control management,