Amazon Connect Developer || AWS LOCAL TO W2

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes Job Summary (which is like About the role). Then responsibilities (list of duties). Then qualifications (list). Also mentions skills (like Node.js, Python, Java, IVR, ACD, etc.) Could be part of Qualifications or separate Skills. The instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Thus we need to decide which sections to include: About the role (Job Summary), Responsibilities, Qualifications (maybe also Requirements). The posting includes "Qualifications" heading with bullet list. Also there is "Job Summary" which is like About the role. There's no explicit "Responsibilities" heading but the job summary includes many duty sentences. We could treat those as Responsibilities. There's no explicit "Skills" separate; but we could include Skills if we want, but we must not create thin sections. The qualifications already list skills like Node.js, Python, Java, IVR, ACD, etc. Could combine Qualifications and Skills into one section? But the instruction says use headings like Skills if there is content. We could have Qualifications and Skills separate if we have distinct content. However the qualifications list includes both education/experience and technical skills. Might be better to have Qualifications (education/experience) and Skills (technical). But we risk thin sections. Let's see content: Job Summary paragraph: "Design, develop, and implement AWS Connect solutions (IVR, routing, ACD, chat) to support enterprise business requirements. Collaborate with stakeholders to gather, review, and document requirements for new and existing processes. Develop enterprise solutions using AWS Cloud services (Lambda, Lex, DynamoDB, Kinesis, etc.) and programming languages such as Node.js, Python, or Java. Enhance and support existing Amazon Connect processes based on new requirements, upgrades, or identified improvements. Recommend and implement updates or modifications to workflows, applications, forms, policies, or interfaces. Create process flow documentation and maintain accurate technical records. Ensure robust access control and integration with other enterprise systems as required. Contribute to designing and developing solutions within the ServiceNow environment as needed. Maintain high standards for system availability, change management, and testing practices. Communicate effectively with team members, stakeholders, and clients. Adapt to a fast-paced, dynamic work environment, managing multiple priorities and deadlines. Perform other duties as assigned or directed." That's responsibilities. Qualifications: "Bachelor s Degree in Computer Science, Mathematics, Engineering, or related field. 7+ years experience with large enterprise frameworks and AWS Cloud platform. 3+ years hands-on experience with Amazon Connect and call routing/messaging design. 3+ years experience in Node.js, Python, or Java development. Strong knowledge of IVR, ACD, skill-based routing, and live chat. Experience with AWS services (Lambda, Lex, Kinesis, DynamoDB, etc.). Excellent communication, documentation, and interpersonal skills." Thus we could have sections: About the role (maybe not needed if we treat Job Summary as About the role). Responsibilities (list). Qualifications (list). Possibly Skills (but qualifications already cover skills). To avoid thin sections, we could combine Qualifications and Skills into one "Qualifications" section that includes both education/experience and technical skills. That seems acceptable. We should not include Benefits, Pay, Schedule as none present. We need to output only HTML fragment, no /, no markdown fences. Thus produce something like:

  About the role

  Design, develop, and implement AWS Connect solutions (IVR, routing, ACD, chat) to support enterprise business requirements. Collaborate with stakeholders to gather, review, and document requirements for new and existing processes. Develop enterprise solutions using AWS Cloud services (Lambda, Lex, DynamoDB, Kinesis, etc.) and programming languages such as Node.js, Python, or Java. Enhance and support existing Amazon Connect processes based on new requirements, upgrades, or identified improvements. Recommend and implement updates or modifications to workflows, applications, forms, policies, or interfaces. Create process flow documentation and maintain accurate technical records. Ensure robust access control and integration with other enterprise systems as required. Contribute to designing and developing solutions within the ServiceNow environment as needed. Maintain high standards for system availability, change management, and testing practices. Communicate effectively with team members, stakeholders, and clients. Adapt to a fast-paced, dynamic work environment, managing multiple priorities and deadlines. Perform other duties as assigned or directed.

  Responsibilities

  • Design, develop, and implement AWS Connect solutions (IVR, routing, ACD, chat) to support enterprise business requirements.
  • Collaborate with stakeholders to gather, review, and document requirements for new and existing processes.
  • Develop enterprise solutions using AWS Cloud services (Lambda, Lex, DynamoDB, Kinesis, etc.) and programming languages such as Node.js, Python, or Java.
  • Enhance and support existing Amazon Connect processes based on new requirements, upgrades, or identified improvements.
  • Recommend and implement updates or modifications to workflows, applications, forms, policies, or interfaces.
  • Create process flow documentation and maintain accurate technical records.
  • Ensure robust access control and integration with other enterprise systems as required.
  • Contribute to designing and developing solutions within the ServiceNow environment as needed.
  • Maintain high standards for system availability, change management, and testing practices.
  • Communicate effectively with team members, stakeholders, and clients.
  • Adapt to a fast-paced, dynamic work environment, managing multiple priorities and deadlines.
  • Perform other duties as assigned or directed.
  But note that the responsibilities list duplicates the About the role paragraph. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we split into About the role (prose) and Responsibilities (list) we are duplicating content. That's okay as long as we preserve all info. However we could avoid duplication by having only one section: either About the role (prose) or Responsibilities (list). But we need to follow instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we must include all; we include only those with real content. The posting has a Job Summary which could be considered About the role. It also has a list of duties that could be Responsibilities. Both are present. So we can include both, but we must not duplicate content? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Duplicating is not inventing or summarizing away; it's repeating. It's allowed but maybe not ideal. However we could restructure: About the role could be a short summary paragraph, and Responsibilities could be the list. The summary paragraph is already present; we could keep it as About the role, and then Responsibilities list the same items but as list. That duplicates but preserves all info. It's okay. Alternatively we could treat About the role as the summary paragraph, and not include Responsibilities separately, but then we would lose the list format (but we still have the prose). The instruction says use

  • for any list of duties/requirements/benefits. The posting does not explicitly have a list; it's a paragraph with sentences separated by periods. However we could convert each sentence into a list item. That would be creating a list from the prose, which is acceptable as we are representing the duties as a list. The instruction says use
    • for any list of duties/requirements/benefits. If we treat the duties as a list, we should use
      • . So we could have a Responsibilities section with list items derived from the sentences. The About the role could be a brief prose summary (maybe one or two sentences). But the posting's Job Summary is already a paragraph of many sentences; we could keep that as About the role (prose). Then Responsibilities list could be the same content but as list; that duplicates. To avoid duplication, we could make About the role a short summary (like "Design, develop, and implement AWS Connect solutions...") but that would be summarizing, which we should avoid. So better to keep the Job Summary as About the role (prose) and not have a separate Responsibilities list, or we could have Responsibilities as list and omit About the role. Which is better? The instruction says prefer a few substantive sections over many thin ones. Having both About the role and Responsibilities might be two sections with similar content; could be considered thin? But each is substantive. However we could combine them: have About the role as prose and not have Responsibilities. But then we are not using
        • for duties, which the instruction says to use for any list of duties/requirements/benefits. If we don't have a list, we are not violating that rule; we just aren't using list where there is no explicit list. The posting does not have a explicit list; it's a paragraph. So we could keep it as prose under About the role. That satisfies using

          for prose. Then we don't need a Responsibilities section. That seems cleaner and avoids duplication. Thus sections: About the role (prose), Qualifications (list). Possibly Skills separate? But qualifications already includes skills. We could keep Qualifications as list covering education/experience and technical skills. That is fine. Thus output:

          About the role

          Design, develop, and implement AWS Connect solutions (IVR, routing, ACD, chat) to support enterprise business requirements. Collaborate with stakeholders to gather, review, and document requirements for new and existing processes. Develop enterprise solutions using AWS Cloud services (Lambda, Lex, DynamoDB, Kinesis, etc.) and programming languages such as Node.js, Python, or Java. Enhance and support existing Amazon Connect processes based on new requirements, upgrades, or identified improvements. Recommend and implement updates or modifications to workflows, applications, forms, policies, or interfaces. Create process flow documentation and maintain accurate technical records. Ensure robust access control and integration with other enterprise systems as required. Contribute to designing and developing solutions within the ServiceNow environment as needed. Maintain high standards for system availability, change management, and testing practices. Communicate effectively with team members, stakeholders, and clients. Adapt to a fast-paced, dynamic work environment, managing multiple priorities and deadlines. Perform other duties as assigned or directed.

          Qualifications

          • Bachelor's Degree in Computer Science, Mathematics, Engineering, or related field.
          • 7+ years experience with large enterprise frameworks and AWS Cloud platform.
          • 3+ years hands-on experience with Amazon Connect and call routing/messaging design.
          • 3+ years experience in Node.js, Python, or Java development.
          • Strong knowledge of IVR,