Full Stack Developer

We need to output HTML fragment with sections: headings using

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. The posting includes: - Job Description (intro) - could be "About the role" maybe. - Must Have Technical/Functional Skills (list) - Initial Project Scope (description) - Required Qualifications (list) - Preferred Qualifications (list) - Roles & Responsibilities (maybe not listed? Actually after Preferred Qualifications there is "Roles & Responsibilities Salary Range: $140,000 to $155,000 per year Qualifications: BACHELOR OF COMPUTER SCIENCE". That seems odd: "Roles & Responsibilities Salary Range: $140,000 to $155,000 per year Qualifications: BACHELOR OF COMPUTER SCIENCE". Likely they intended separate sections: Roles & Responsibilities, Salary Range, Qualifications (education). But the text is garbled. We need to preserve substantive info. We need to extract: - About the role: The initial paragraph: "Seeking a full-stack developer to take a prototype built in GitHub Copilot or Kiro and transform it into a secure, scalable, and supportable enterprise application deployed in AWS. This role will be responsible for designing, developing, testing, deploying, and operationalizing the solution in alignment with enterprise architecture, technology, and information security standards. The ideal candidate will bring experience across front-end and back-end development, AWS cloud services, CI/CD pipelines, infrastructure as code, identity and access management, observability, and production support, with a strong emphasis on building solutions that are resilient, maintainable, and compliant in an enterprise environment." - Initial Project Scope: "Build a modern Learning Experience Platform (LXP) from the ground up to deliver a personalized, engaging, and scalable learning experience for employees and learners. Work closely with Product team to align with the product vision, core user journeys, and cross-functionally with design, engineering, content, and analytics teams to create a platform that supports discovery, recommendations, social learning, and measurable skill development." - Required Qualifications: list bullet points. - Preferred Qualifications: list bullet points. - Salary Range: "$140,000 to $155,000 per year" - Education Qualification: "BACHELOR OF COMPUTER SCIENCE" (maybe under Qualifications). Could be part of Required Qualifications? It's separate. - Roles & Responsibilities: Not explicitly listed separate; maybe the initial description covers responsibilities. But we have a heading "Roles & Responsibilities" in the posting but then directly followed by salary and education. Could treat that as a section with content: maybe the responsibilities are the earlier description? However we should not invent. The posting says "Roles & Responsibilities Salary Range: $140,000 to $155,000 per year Qualifications: BACHELOR OF COMPUTER SCIENCE". That seems like they omitted line breaks. We could interpret that the Roles & Responsibilities section is empty (just salary and qualifications). But we should not create a section with filler. Better to not include Roles & Responsibilities heading if no specific responsibilities listed beyond what we already have in About the role. However the instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". We need to map content. We have: - About the role: intro paragraph. - Responsibilities: maybe the bullet list of duties? The posting didn't have explicit responsibilities list; but we could treat the "Initial Project Scope" as responsibilities? Or the role responsibilities are designing, developing, testing, deploying, operationalizing. That's in About the role. Could create a Responsibilities section with those actions. - Requirements: maybe the Required Qualifications. - Qualifications: maybe the Preferred Qualifications? Or education. - Skills: maybe the technical skills list (Must Have Technical/Functional Skills). That could be Skills. - Pay: Salary Range. - Schedule: not mentioned. - Benefits: not mentioned. Thus we will include sections: About the role, Responsibilities, Requirements, Skills, Pay, Qualifications (education). We must not include empty sections. Let's extract content precisely. **About the role**: The paragraph after "Job Description Must Have Technical/Functional Skills Full-Stack Developer for Enterprise Operationalization Seeking a full-stack developer..." Actually the posting starts: "Job Description Must Have Technical/Functional Skills Full-Stack Developer for Enterprise Operationalization Seeking a full-stack developer to take a prototype built in GitHub Copilot or Kiro and transform it into a secure, scalable, and supportable enterprise application deployed in AWS. This role will be responsible for designing, developing, testing, deploying, and operationalizing the solution in alignment with enterprise architecture, technology, and information security standards. The ideal candidate will bring experience across front-end and back-end development, AWS cloud services, CI/CD pipelines, infrastructure as code, identity and access management, observability, and production support, with a strong emphasis on building solutions that are resilient, maintainable, and compliant in an enterprise environment." We'll put that as

. **Responsibilities**: Could be the list of duties: designing, developing, testing, deploying, operationalizing the solution; aligning with enterprise architecture; building resilient, maintainable, compliant solutions; working with product team; cross-functionally with design, engineering, content, analytics; creating platform supporting discovery, recommendations, social learning, measurable skill development. We can combine. But we must not invent; we can pull from text: "designing, developing, testing, deploying, and operationalizing the solution", "Work closely with Product team to align with the product vision, core user journeys, and cross-functionally with design, engineering, content, and analytics teams to create a platform that supports discovery, recommendations, social learning, and measurable skill development." Also "building solutions that are resilient, maintainable, and compliant". We'll put those as

• . **Requirements**: Required Qualifications list: - Experience taking a prototype or proof of concept and transforming it into a production-ready enterprise application - Strong proficiency in full-stack development across front-end and back-end technologies - Proficiency with cloud infrastructure, ideally AWS, including services such as Amazon S3, Lambda, and Bedrock - Experience with containerization and orchestration technologies such as Docker and Kubernetes - Experience with infrastructure as code, such as Terraform, and CI/CD pipelines - Experience implementing enterprise authentication, authorization, and security controls - Experience with automated testing on both backend and UI layers - Familiarity with observability tools and practices, including logging, monitoring, and alerting - Strong experience using Git for version control, code review, and collaboration - Ability to translate business problems into technical solutions and communicate complex concepts clearly - Strong communication skills with a proactive, collaborative, and solution-oriented mindset We'll put each as
• . **Skills**: Must Have Technical/Functional Skills (the heading). Likely same as Required Qualifications? Actually the posting begins: "Job Description Must Have Technical/Functional Skills Full-Stack Developer for Enterprise Operationalization". Might be a heading. The list after that is the Required Qualifications? Actually the "Must Have Technical/Functional Skills" could be a section heading, then the following paragraph is the job description. But we already used that for About the role. However we could treat the technical skills as a separate section: list of skills like full-stack development, AWS, Docker/Kubernetes, Terraform, CI/CD, IAM, observability, Git, etc. But that overlaps with Required Qualifications. To avoid duplication, we could combine. But instruction: preserve ALL substantive information; do not invent or summarize away detail. If we duplicate, that's okay as long as we preserve. But better to not duplicate same content. However the "Must Have Technical/Functional Skills" might be a heading that introduces the list of skills (which is the Required Qualifications). The Required Qualifications list includes those skills. So we could make a Skills section with the same list. But that would be duplicate. The instruction says preserve ALL substantive information; duplication is not prohibited but could be considered redundant. However they said "Prefer a few substantive sections over many thin ones." So we should avoid thin duplicate sections. So we can merge Skills into Requirements or treat Required Qualifications as Skills. But we need a section for Requirements (maybe qualifications). Let's decide: - About the role: intro paragraph. - Responsibilities: duties list. - Requirements: Required Qualifications list. - Qualifications: Education (BACHELOR OF COMPUTER SCIENCE) plus maybe Preferred Qualifications? Actually Preferred Qualifications could be under Qualifications as well. But we have a separate section for Preferred Qualifications maybe as "Preferred Qualifications". However the allowed headings list includes Qualifications (generic). We could split into Required Qualifications and Preferred Qualifications both under Qualifications? But we need to preserve detail. Could have two subsections? Not allowed; only headings list. Could use Qualifications for both required and preferred, but we need to differentiate. Could use "Requirements" for required, "Qualifications" for preferred, and maybe also education under Qualifications. But education is also a qualification. Might be okay. Let's map: - Requirements: Required Qualifications list. - Qualifications: Preferred Qualifications list + Education requirement. But education is a qualification; we can include it in Qualifications section. Thus: Qualifications section will contain: - Preferred Qualifications bullet list. - Also note: BACHELOR OF COMPUTER SCIENCE (maybe as a separate line). We need to ensure we don't lose any info. Preferred Qualifications list: - Proficient in AI-assisted coding tools such as GitHub Copilot, Claude Code, and Kiro - Good understanding of GenAI building blocks, including prompting techniques, agentic frameworks, evals, guardrails, RAG, embeddings/vector databases, model fine-tuning, graph databases with LLMs, MCP, and reasoni ng models (note typo "reasoni ng". We'll preserve as is.) - Knowledge of MLOps best practices - Experience modernizing prototypes into enterprise-grade applications in regulated or large enterprise environments - Prior experience supporting production applications through monitoring, incident response, and operational handoff - Experience documenting technical solutions, support procedures, and operational runbooks Education: BACHELOR OF COMPUTER SCIENCE. Pay: Salary Range: $140,000 to $155,000 per year. Schedule: none. Benefits: none. Now we need to output HTML fragment only, with

  headings and

  or

  • . We must not include any extra text like explanations. Let's craft:

    About the role

    Seeking a full-stack developer to take a prototype built in GitHub Copilot or Kiro and transform it into a secure, scalable, and supportable enterprise application deployed in AWS. This role will be responsible for designing, developing, testing, deploying, and operationalizing the solution in alignment with enterprise architecture, technology, and information security standards. The ideal candidate will bring experience across front-end and back-end development, AWS cloud services, CI/CD pipelines, infrastructure as code, identity and access management, observability, and production support, with a strong emphasis on building solutions that are resilient, maintainable, and compliant in an enterprise environment.

    Responsibilities

    • Designing, developing, testing, deploying, and operationalizing the solution
    • Aligning with enterprise architecture, technology, and information security standards
    • Building solutions that are resilient, maintainable, and compliant
    • Working closely with the Product team to align with product vision and core user journeys
    • Collaborating cross‑functionally with design, engineering