Lead Full Stack Software Engineer
for each heading. Use - for any list of duties/requirements/benefits. Use
for prose. Do NOT repeat job title as heading. Do NOT include Job ID etc. Remove boilerplate. Include sections only when posting has real specific content.
We need to parse the posting.
Content:
- Intro: "Become a part of our caring community The Lead Full Stack Engineer performs software engineering activities across all layers of the technology stack, including cloud infrastructure, APIs, microservices, GraphQL services, databases, and modern web and mobile experiences. This role provides technical leadership for the Member Experience Portal and is responsible for delivering scalable, secure, reliable, and high-performing digital solutions while driving Engineering Excellence and Operational Excellence across Agile Scrum teams. You will report to the Associate Director of Software Engineering."
That's prose about role. Could be "About the role" section.
- "Key Leadership Responsibilities" list: Mentor, coach, and develop engineers across Agile teams. Foster a growth mindset, accountability, ownership, continuous learning, and technical excellence. Lead architecture reviews, code reviews, technical design sessions, and career development discussions. Influence teams and stakeholders to align on reusable business capabilities and shared engineering objectives.
- "Engineering and Architecture Excellence" list: Champion modern software engineering practices, reusable architecture patterns, omni channel micro frontends, API-first development, GraphQL and REST services, test automation, CI/CD, observability, performance engineering, and platform reusability. Establish standards for code quality, reliability, maintainability, and scalability.
- "AI Driven Engineering Efficiency" list: Lead the adoption of AI-assisted engineering tools such as GitHub Copilot, Claude, and Agentic AI solutions to improve developer productivity, code generation, documentation, testing, and delivery efficiency while maintaining security and quality standards.
- "DevSecOps and Security" list: Champion security-first and compliance-by-design development practices. Embed threat modeling, secure coding, vulnerability scanning, security automation, OWASP controls, identity management, compliance validation, and governance controls from the beginning of the SDLC.
- "Member Experience Focus" prose: Collaborate closely with Product Managers, Product Owners, UX teams, architects, and business stakeholders to deliver highly personalized and seamless member experiences. Demonstrate deep understanding of Member Experience Portal architecture, customer journeys, and enterprise integrations.
- "This is a hybrid role, and you will be required to come into the office 1-2 per week. Candidates should reside or be within 50 miles of Dallas TX, Chicago Metro, DC Metro or Louisville area." This is schedule/location info. Could be Schedule section (hybrid, office days) and maybe location not needed.
- "Required Qualifications" heading then bullet list: Use your skills to make an impact Bachelor's Degree8 or more years of experience in software developmentProficient understanding tech-lead level experience in one or more programming languages like Javascript, Python, Typescripts etc.Experience building backend technology like; .Net, Java, Spring/Spring Boot or NodeJSExperience with JSON, RESTful web services and client-server interactionsExperience with highly scalable websites (Vue.js, Angular, React etc.) and web servicesKnowledge of and experience with Azure or equivalent providerEnvironment management/orchestration systems (Kubernetes, Docker, AKS, etc.)React-Native, Mobile app experience and AI/Agentic AI, Leveraging Code generation tools like Claude and Co-pilot is preferred
It seems the formatting is messed up: "Bachelor's Degree8 or more years of experience in software development" likely means Bachelor's Degree, 8+ years experience. We'll parse as separate items.
We need to extract qualifications list.
- "Work at Home Requirements:" includes internet speed, dedicated space. This is maybe part of Requirements or maybe not needed? It's a requirement for remote/hybrid. Could be included under Requirements.
- "Travel: While this is a remote position, occasional travel to Humana's offices for training or meetings may be required."
- "Scheduled Weekly Hours 40" -> schedule.
- "Pay Range" with $129,300 - $177,800 per year. Also mention bonus incentive plan.
- "Description Of Benefits" paragraph about benefits.
- "About Us" about Humana. Could be omitted? It's not required sections but could be included under About the role? Probably not needed; we can ignore as boilerplate? It's not EEO but it's company description; maybe we can keep as part of About the role? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. About Us is not necessarily boilerplate but could be considered company overview; but we might keep it under About the role? However they said "Prefer a few substantive sections over many thin ones." So we could combine About the role and About Us into About the role? But About Us is not about the role. Might be considered filler. Safer to omit About Us as not required section.
- Equal Opportunity Employer boilerplate: remove.
Thus sections we will include:
- About the role (intro paragraph + maybe Member Experience Focus? Could combine.)
- Responsibilities (Key Leadership Responsibilities, Engineering and Architecture Excellence, AI Driven Engineering Efficiency, DevSecOps and Security, Member Experience Focus). Could be multiple lists but we can combine into one
with items.
- Requirements (Qualifications list + Work at Home Requirements + Travel). Could be separate sub-sections? But we only have headings: Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The posting uses "Required Qualifications". We could treat that as Qualifications section. Skills maybe separate? Could extract skills from qualifications: programming languages, backend, front-end, cloud, DevOps, mobile, AI. Could put under Skills.
But we need to follow instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should create those headings only if there is real specific content.
Thus we need to map content to these headings.
Let's extract:
About the role: Intro paragraph describing role, plus maybe Member Experience Focus? But Member Experience Focus could be part of Responsibilities. We'll keep About the role as the introductory paragraph.
Responsibilities: All the bullet points under Key Leadership Responsibilities, Engineering and Architecture Excellence, AI Driven Engineering Efficiency, DevSecOps and Security, Member Experience Focus. We'll combine into a list.
Requirements: Could be the "Work at Home Requirements" (internet speed, dedicated space) and Travel? Or maybe we treat Requirements as general eligibility (location, hybrid). But we have also "Candidates should reside or be within 50 miles of Dallas TX, Chicago Metro, DC Metro or Louisville area." That's location requirement.
Qualifications: The list under "Required Qualifications". We'll parse into items.
Skills: Could be derived from qualifications but maybe we separate technical skills: programming languages, backend, front-end, cloud, DevOps, mobile, AI. However the qualifications already list many of those; we could treat Qualifications as the list and Skills as maybe a subset? But to avoid duplication, maybe we skip Skills if content overlaps heavily. But instruction: include a section ONLY when posting has real specific content for it. If we put Skills, we need specific content not already covered elsewhere. We could extract skills like "JavaScript, Python, TypeScript, .NET, Java, Spring/Spring Boot, NodeJS, JSON, RESTful web services, Vue.js, Angular, React, Azure, Kubernetes, Docker, AKS, React-Native, Mobile app experience, AI/Agentic AI, Code generation tools (Claude, Copilot)". That is specific. Could be separate.
Benefits: The Description Of Benefits paragraph.
Pay: Pay Range and bonus incentive plan.
Schedule: Hybrid role office 1-2 per week, Scheduled Weekly Hours 40, maybe travel occasional.
We must not include placeholder text like "commensurate with experience". Not present.
Now we need to format.
We'll output HTML fragment with sections in order: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
Each heading then content.
For lists: use - .
For prose:
.
We need to ensure we don't repeat content unnecessarily.
Let's craft each section.
About the role: combine intro paragraph and maybe Member Experience Focus? But Member Experience Focus is more responsibility. We'll keep About the role as:
Become a part of our caring community. The Lead Full Stack Engineer performs software engineering activities across all layers of the technology stack, including cloud infrastructure, APIs, microservices, GraphQL services, databases, and modern web and mobile experiences. This role provides technical leadership for the Member Experience Portal and is responsible for delivering scalable, secure, reliable, and high-performing digital solutions while driving Engineering Excellence and Operational Excellence across Agile Scrum teams. You will report to the Associate Director of Software Engineering.
That's good.
Responsibilities: combine all bullet points.
We'll create a with items:
- Mentor, coach, and develop engineers across Agile teams; foster a growth mindset, accountability, ownership, continuous learning, and technical excellence.
- Lead architecture reviews, code reviews, technical design sessions, and career development discussions.
- Influence teams and stakeholders to align on reusable business capabilities and shared engineering objectives.
- Champion modern software engineering practices, reusable architecture patterns, omni-channel micro frontends, API-first development, GraphQL and REST services, test automation, CI/CD, observability, performance engineering, and platform reusability.
- Establish standards for code quality, reliability, maintainability, and scalability.
- Lead the adoption of AI-assisted engineering tools such as GitHub Copilot, Claude, and Agentic AI solutions to improve developer productivity, code generation, documentation, testing, and delivery efficiency while maintaining security and quality standards.
- Champion security-first and compliance-by-design development practices; embed threat modeling, secure coding, vulnerability scanning, security automation, OWASP controls, identity management, compliance validation, and governance controls from the beginning of the SDLC.
- Collaborate closely with Product Managers, Product Owners, UX teams, architects, and business stakeholders to deliver highly personalized and seamless member experiences; demonstrate deep understanding of Member Experience Portal architecture, customer journeys, and enterprise integrations.
That covers.
Requirements: This could include Work at Home Requirements and Travel and location? But we have also location requirement. Let's put under Requirements:
- Must reside or be within 50 miles of Dallas TX, Chicago Metro, DC Metro, or Louisville area.
- Hybrid role: required to come into the office 1-2 days per week.
- Work-from-home requirements: minimum download speed 25 Mbps, upload speed 10 Mbps (wireless, wired cable or DSL suggested); dedicated workspace free of interruptions to protect member PHI/HIPAA information.
- Occasional travel to Humana's offices for training or meetings may be required.
We'll format as .
Qualifications: list from Required Qualifications.
We need to parse the messy line:
"Bachelor's Degree8 or more years of experience in software developmentProficient understanding tech-lead level experience in one or more programming languages like Javascript, Python, Typescripts etc.Experience building backend technology like; .Net, Java, Spring/Spring Boot or NodeJSExperience with JSON, RESTful web services and client-server interactionsExperience with highly scalable websites (Vue.js, Angular, React etc.) and web servicesKnowledge of and experience with Azure or equivalent providerEnvironment management/orchestration systems (Kubernetes, Docker, AKS, etc.)React-Native, Mobile app experience and AI/Agentic AI, Leveraging Code generation tools like Claude and Co-pilot is preferred"
We need to split into sensible items:
- Bachelor's degree.
- 8 or more years of experience in software development.
- Proficient understanding/tech-lead level experience in one or more programming languages such as JavaScript, Python, TypeScript, etc.
- Experience building
for prose. Do NOT repeat job title as heading. Do NOT include Job ID etc. Remove boilerplate. Include sections only when posting has real specific content. We need to parse the posting. Content: - Intro: "Become a part of our caring community The Lead Full Stack Engineer performs software engineering activities across all layers of the technology stack, including cloud infrastructure, APIs, microservices, GraphQL services, databases, and modern web and mobile experiences. This role provides technical leadership for the Member Experience Portal and is responsible for delivering scalable, secure, reliable, and high-performing digital solutions while driving Engineering Excellence and Operational Excellence across Agile Scrum teams. You will report to the Associate Director of Software Engineering." That's prose about role. Could be "About the role" section. - "Key Leadership Responsibilities" list: Mentor, coach, and develop engineers across Agile teams. Foster a growth mindset, accountability, ownership, continuous learning, and technical excellence. Lead architecture reviews, code reviews, technical design sessions, and career development discussions. Influence teams and stakeholders to align on reusable business capabilities and shared engineering objectives. - "Engineering and Architecture Excellence" list: Champion modern software engineering practices, reusable architecture patterns, omni channel micro frontends, API-first development, GraphQL and REST services, test automation, CI/CD, observability, performance engineering, and platform reusability. Establish standards for code quality, reliability, maintainability, and scalability. - "AI Driven Engineering Efficiency" list: Lead the adoption of AI-assisted engineering tools such as GitHub Copilot, Claude, and Agentic AI solutions to improve developer productivity, code generation, documentation, testing, and delivery efficiency while maintaining security and quality standards. - "DevSecOps and Security" list: Champion security-first and compliance-by-design development practices. Embed threat modeling, secure coding, vulnerability scanning, security automation, OWASP controls, identity management, compliance validation, and governance controls from the beginning of the SDLC. - "Member Experience Focus" prose: Collaborate closely with Product Managers, Product Owners, UX teams, architects, and business stakeholders to deliver highly personalized and seamless member experiences. Demonstrate deep understanding of Member Experience Portal architecture, customer journeys, and enterprise integrations. - "This is a hybrid role, and you will be required to come into the office 1-2 per week. Candidates should reside or be within 50 miles of Dallas TX, Chicago Metro, DC Metro or Louisville area." This is schedule/location info. Could be Schedule section (hybrid, office days) and maybe location not needed. - "Required Qualifications" heading then bullet list: Use your skills to make an impact Bachelor's Degree8 or more years of experience in software developmentProficient understanding tech-lead level experience in one or more programming languages like Javascript, Python, Typescripts etc.Experience building backend technology like; .Net, Java, Spring/Spring Boot or NodeJSExperience with JSON, RESTful web services and client-server interactionsExperience with highly scalable websites (Vue.js, Angular, React etc.) and web servicesKnowledge of and experience with Azure or equivalent providerEnvironment management/orchestration systems (Kubernetes, Docker, AKS, etc.)React-Native, Mobile app experience and AI/Agentic AI, Leveraging Code generation tools like Claude and Co-pilot is preferred It seems the formatting is messed up: "Bachelor's Degree8 or more years of experience in software development" likely means Bachelor's Degree, 8+ years experience. We'll parse as separate items. We need to extract qualifications list. - "Work at Home Requirements:" includes internet speed, dedicated space. This is maybe part of Requirements or maybe not needed? It's a requirement for remote/hybrid. Could be included under Requirements. - "Travel: While this is a remote position, occasional travel to Humana's offices for training or meetings may be required." - "Scheduled Weekly Hours 40" -> schedule. - "Pay Range" with $129,300 - $177,800 per year. Also mention bonus incentive plan. - "Description Of Benefits" paragraph about benefits. - "About Us" about Humana. Could be omitted? It's not required sections but could be included under About the role? Probably not needed; we can ignore as boilerplate? It's not EEO but it's company description; maybe we can keep as part of About the role? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. About Us is not necessarily boilerplate but could be considered company overview; but we might keep it under About the role? However they said "Prefer a few substantive sections over many thin ones." So we could combine About the role and About Us into About the role? But About Us is not about the role. Might be considered filler. Safer to omit About Us as not required section. - Equal Opportunity Employer boilerplate: remove. Thus sections we will include: - About the role (intro paragraph + maybe Member Experience Focus? Could combine.) - Responsibilities (Key Leadership Responsibilities, Engineering and Architecture Excellence, AI Driven Engineering Efficiency, DevSecOps and Security, Member Experience Focus). Could be multiple lists but we can combine into one
- with items.
- Requirements (Qualifications list + Work at Home Requirements + Travel). Could be separate sub-sections? But we only have headings: Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The posting uses "Required Qualifications". We could treat that as Qualifications section. Skills maybe separate? Could extract skills from qualifications: programming languages, backend, front-end, cloud, DevOps, mobile, AI. Could put under Skills.
But we need to follow instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should create those headings only if there is real specific content.
Thus we need to map content to these headings.
Let's extract:
About the role: Intro paragraph describing role, plus maybe Member Experience Focus? But Member Experience Focus could be part of Responsibilities. We'll keep About the role as the introductory paragraph.
Responsibilities: All the bullet points under Key Leadership Responsibilities, Engineering and Architecture Excellence, AI Driven Engineering Efficiency, DevSecOps and Security, Member Experience Focus. We'll combine into a list.
Requirements: Could be the "Work at Home Requirements" (internet speed, dedicated space) and Travel? Or maybe we treat Requirements as general eligibility (location, hybrid). But we have also "Candidates should reside or be within 50 miles of Dallas TX, Chicago Metro, DC Metro or Louisville area." That's location requirement.
Qualifications: The list under "Required Qualifications". We'll parse into items.
Skills: Could be derived from qualifications but maybe we separate technical skills: programming languages, backend, front-end, cloud, DevOps, mobile, AI. However the qualifications already list many of those; we could treat Qualifications as the list and Skills as maybe a subset? But to avoid duplication, maybe we skip Skills if content overlaps heavily. But instruction: include a section ONLY when posting has real specific content for it. If we put Skills, we need specific content not already covered elsewhere. We could extract skills like "JavaScript, Python, TypeScript, .NET, Java, Spring/Spring Boot, NodeJS, JSON, RESTful web services, Vue.js, Angular, React, Azure, Kubernetes, Docker, AKS, React-Native, Mobile app experience, AI/Agentic AI, Code generation tools (Claude, Copilot)". That is specific. Could be separate.
Benefits: The Description Of Benefits paragraph.
Pay: Pay Range and bonus incentive plan.
Schedule: Hybrid role office 1-2 per week, Scheduled Weekly Hours 40, maybe travel occasional.
We must not include placeholder text like "commensurate with experience". Not present.
Now we need to format.
We'll output HTML fragment with sections in order: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
Each heading
- .
For prose:
. We need to ensure we don't repeat content unnecessarily. Let's craft each section. About the role: combine intro paragraph and maybe Member Experience Focus? But Member Experience Focus is more responsibility. We'll keep About the role as:
Become a part of our caring community. The Lead Full Stack Engineer performs software engineering activities across all layers of the technology stack, including cloud infrastructure, APIs, microservices, GraphQL services, databases, and modern web and mobile experiences. This role provides technical leadership for the Member Experience Portal and is responsible for delivering scalable, secure, reliable, and high-performing digital solutions while driving Engineering Excellence and Operational Excellence across Agile Scrum teams. You will report to the Associate Director of Software Engineering.
That's good. Responsibilities: combine all bullet points. We'll create a- with items:
- Mentor, coach, and develop engineers across Agile teams; foster a growth mindset, accountability, ownership, continuous learning, and technical excellence.
- Lead architecture reviews, code reviews, technical design sessions, and career development discussions.
- Influence teams and stakeholders to align on reusable business capabilities and shared engineering objectives.
- Champion modern software engineering practices, reusable architecture patterns, omni-channel micro frontends, API-first development, GraphQL and REST services, test automation, CI/CD, observability, performance engineering, and platform reusability.
- Establish standards for code quality, reliability, maintainability, and scalability.
- Lead the adoption of AI-assisted engineering tools such as GitHub Copilot, Claude, and Agentic AI solutions to improve developer productivity, code generation, documentation, testing, and delivery efficiency while maintaining security and quality standards.
- Champion security-first and compliance-by-design development practices; embed threat modeling, secure coding, vulnerability scanning, security automation, OWASP controls, identity management, compliance validation, and governance controls from the beginning of the SDLC.
- Collaborate closely with Product Managers, Product Owners, UX teams, architects, and business stakeholders to deliver highly personalized and seamless member experiences; demonstrate deep understanding of Member Experience Portal architecture, customer journeys, and enterprise integrations.
That covers.
Requirements: This could include Work at Home Requirements and Travel and location? But we have also location requirement. Let's put under Requirements:
- Must reside or be within 50 miles of Dallas TX, Chicago Metro, DC Metro, or Louisville area.
- Hybrid role: required to come into the office 1-2 days per week.
- Work-from-home requirements: minimum download speed 25 Mbps, upload speed 10 Mbps (wireless, wired cable or DSL suggested); dedicated workspace free of interruptions to protect member PHI/HIPAA information.
- Occasional travel to Humana's offices for training or meetings may be required.
We'll format as
- .
Qualifications: list from Required Qualifications.
We need to parse the messy line:
"Bachelor's Degree8 or more years of experience in software developmentProficient understanding tech-lead level experience in one or more programming languages like Javascript, Python, Typescripts etc.Experience building backend technology like; .Net, Java, Spring/Spring Boot or NodeJSExperience with JSON, RESTful web services and client-server interactionsExperience with highly scalable websites (Vue.js, Angular, React etc.) and web servicesKnowledge of and experience with Azure or equivalent providerEnvironment management/orchestration systems (Kubernetes, Docker, AKS, etc.)React-Native, Mobile app experience and AI/Agentic AI, Leveraging Code generation tools like Claude and Co-pilot is preferred"
We need to split into sensible items:
- Bachelor's degree.
- 8 or more years of experience in software development.
- Proficient understanding/tech-lead level experience in one or more programming languages such as JavaScript, Python, TypeScript, etc.
- Experience building