Lead Full Stack Software Engineer
Humana · Texas, United States · 1 mo ago
RemoteRemoteEngineering$129k–$178k/yrFull-time
We need to output HTML fragment with headings for sections present: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. Let's 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 about the role. Could be "About the role" section.
- Key Leadership Responsibilities: list bullet points.
- Engineering and Architecture Excellence: bullet points.
- AI Driven Engineering Efficiency: bullet points.
- DevSecOps and Security: bullet points.
- Member Experience Focus: bullet points.
- 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.
- Required Qualifications: list bullet points.
- Work at Home Requirements: internet speed etc.
- Travel: occasional travel.
- Scheduled Weekly Hours 40
- Pay Range: $129,300 - $177,800 per year. Bonus incentive plan.
- Description Of Benefits: list.
- About Us: about Humana.
- Equal Opportunity Employer: boilerplate to remove.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So remove Equal Opportunity Employer paragraph.
Also remove "About Us"? Not sure if considered boilerplate. It's company description; maybe keep as "About the company"? Not a required heading but could be included as "About the company"? The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings but says "Use
for sections present: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. Let's 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 about the role. Could be "About the role" section.
- Key Leadership Responsibilities: list bullet points.
- Engineering and Architecture Excellence: bullet points.
- AI Driven Engineering Efficiency: bullet points.
- DevSecOps and Security: bullet points.
- Member Experience Focus: bullet points.
- 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.
- Required Qualifications: list bullet points.
- Work at Home Requirements: internet speed etc.
- Travel: occasional travel.
- Scheduled Weekly Hours 40
- Pay Range: $129,300 - $177,800 per year. Bonus incentive plan.
- Description Of Benefits: list.
- About Us: about Humana.
- Equal Opportunity Employer: boilerplate to remove.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So remove Equal Opportunity Employer paragraph.
Also remove "About Us"? Not sure if considered boilerplate. It's company description; maybe keep as "About the company"? Not a required heading but could be included as "About the company"? The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings but says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings; we could also add other headings if needed but better to stick to those.
We need to include sections only when posting has real specific content.
Thus we can have:
About the role
with paragraph summarizing role description.
Responsibilities
with of leadership responsibilities etc. Might combine multiple bullet groups.
We have multiple responsibility categories: Key Leadership Responsibilities, Engineering and Architecture Excellence, AI Driven Engineering Efficiency, DevSecOps and Security, Member Experience Focus. Could combine under Responsibilities.
Alternatively separate sections: maybe "Leadership Responsibilities", "Engineering & Architecture", "AI Driven Engineering", "DevSecOps", "Member Experience". But instruction only gave examples; we can still use other headings but better to keep to given list. However we can still use for any section heading; they gave examples but not exclusive. Safer to stick to those headings.
Thus we need to map content to those headings.
About the role: intro paragraph.
Responsibilities: combine all bullet points under responsibilities.
Requirements: maybe "Required Qualifications" as Requirements.
Qualifications: maybe "Required Qualifications" also? Could be duplicate. Actually "Required Qualifications" is a list of qualifications. Could be under Requirements or Qualifications. We need to decide.
Skills: maybe list of specific skills like programming languages, frameworks.
Benefits: description of benefits.
Pay: pay range.
Schedule: scheduled weekly hours (40) and hybrid office requirement.
We also have work-at-home requirements (internet speed) and travel; could be under Schedule or maybe separate but we can incorporate into Schedule.
We must not include filler like "commensurate with experience". Not present.
Let's extract details.
About the role paragraph: "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."
We need to ensure proper spacing.
Responsibilities bullets:
From Key Leadership Responsibilities:
- 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:
- 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:
- 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:
- 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:
- 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.
Also hybrid role: "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."
That could be under Schedule or maybe under Responsibilities? It's more about work arrangement.
Required Qualifications bullet list:
- Bachelor's Degree
- 8 or more years of experience in software development
- Proficient 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 NodeJS
- Experience with JSON, RESTful web services and client-server interactions
- Experience with highly scalable websites (Vue.js, Angular, React etc.) and web services
- Knowledge of and experience with Azure or equivalent provider
- Environment 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
Also Work at Home Requirements:
- To ensure Home or Hybrid Home/Office employees’ ability to work effectively, the self-provided internet service of Home or Hybrid Home/Office employees must meet the following criteria: At minimum, a download speed of 25 Mbps and an upload speed of 10 Mbps is required; wireless, wired cable or DSL connection is suggested. In certain roles, the minimum recommended internet speed required by Humana may not be sufficient for business needs. Humana reserves the right to require associates to upgrade their internet service if necessary.
- Work from a dedicated space lacking ongoing interruptions to protect member PHI / HIPAA information.
Travel: occasional travel to Humana's offices for training or meetings may be required.
Scheduled Weekly Hours 40
Pay Range: $129,300 - $177,800 per year. Bonus incentive plan.
Benefits: medical, dental and vision benefits, 401(k) retirement savings plan, time off (including paid time off, company and personal holidays, paid parental and caregiver leave), short-term and long-term disability, life insurance and many other opportunities.
About Us: we could maybe include as "About the company" but not required. Might be okay to omit as it's not in the list but could be considered boilerplate? It's company description; maybe keep under "About the role"? But we already have about role. Could add a separate About the company
but not in examples. Safer to omit? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings but says e.g. So we could include About the company but maybe better to stick to given ones. However the About Us is substantive; we could put it under About the role? Might be redundant. Could create a separate section "About the company" but not in list; risk of being considered not following instruction? The instruction says use h3 for section headings (e.g. ...). It doesn't say you cannot use other headings, just give examples. So we could include About the company. But to be safe, we could incorporate it into About the role paragraph? Might be too long. But we can add a separate About the company
as it's substantive.
Nevertheless, the instruction: "Prefer a few substantive sections over many thin ones." So we should not create many thin sections. Adding About the company might be okay.
But we also have "Work at Home Requirements" and "Travel". Could be placed under Schedule or maybe under Responsibilities? Probably Schedule.
Let's craft sections:
About the role
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.
Responsibilities
- 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.
Requirements
This is a hybrid role requiring office presence 1‑2 days per week; candidates must reside within 50 mi of Dallas TX, Chicago Metro, DC Metro, or Louisville area.
About the role
with paragraph summarizing role description.Responsibilities
with- of leadership responsibilities etc. Might combine multiple bullet groups.
We have multiple responsibility categories: Key Leadership Responsibilities, Engineering and Architecture Excellence, AI Driven Engineering Efficiency, DevSecOps and Security, Member Experience Focus. Could combine under Responsibilities.
Alternatively separate sections: maybe "Leadership Responsibilities", "Engineering & Architecture", "AI Driven Engineering", "DevSecOps", "Member Experience". But instruction only gave examples; we can still use other headings but better to keep to given list. However we can still use
- 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.
for any section heading; they gave examples but not exclusive. Safer to stick to those headings.
Thus we need to map content to those headings.
About the role: intro paragraph.
Responsibilities: combine all bullet points under responsibilities.
Requirements: maybe "Required Qualifications" as Requirements.
Qualifications: maybe "Required Qualifications" also? Could be duplicate. Actually "Required Qualifications" is a list of qualifications. Could be under Requirements or Qualifications. We need to decide.
Skills: maybe list of specific skills like programming languages, frameworks.
Benefits: description of benefits.
Pay: pay range.
Schedule: scheduled weekly hours (40) and hybrid office requirement.
We also have work-at-home requirements (internet speed) and travel; could be under Schedule or maybe separate but we can incorporate into Schedule.
We must not include filler like "commensurate with experience". Not present.
Let's extract details.
About the role paragraph: "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."
We need to ensure proper spacing.
Responsibilities bullets:
From Key Leadership Responsibilities:
- 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:
- 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:
- 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:
- 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:
- 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.
Also hybrid role: "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."
That could be under Schedule or maybe under Responsibilities? It's more about work arrangement.
Required Qualifications bullet list:
- Bachelor's Degree
- 8 or more years of experience in software development
- Proficient 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 NodeJS
- Experience with JSON, RESTful web services and client-server interactions
- Experience with highly scalable websites (Vue.js, Angular, React etc.) and web services
- Knowledge of and experience with Azure or equivalent provider
- Environment 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
Also Work at Home Requirements:
- To ensure Home or Hybrid Home/Office employees’ ability to work effectively, the self-provided internet service of Home or Hybrid Home/Office employees must meet the following criteria: At minimum, a download speed of 25 Mbps and an upload speed of 10 Mbps is required; wireless, wired cable or DSL connection is suggested. In certain roles, the minimum recommended internet speed required by Humana may not be sufficient for business needs. Humana reserves the right to require associates to upgrade their internet service if necessary.
- Work from a dedicated space lacking ongoing interruptions to protect member PHI / HIPAA information.
Travel: occasional travel to Humana's offices for training or meetings may be required.
Scheduled Weekly Hours 40
Pay Range: $129,300 - $177,800 per year. Bonus incentive plan.
Benefits: medical, dental and vision benefits, 401(k) retirement savings plan, time off (including paid time off, company and personal holidays, paid parental and caregiver leave), short-term and long-term disability, life insurance and many other opportunities.
About Us: we could maybe include as "About the company" but not required. Might be okay to omit as it's not in the list but could be considered boilerplate? It's company description; maybe keep under "About the role"? But we already have about role. Could add a separate About the company
but not in examples. Safer to omit? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings but says e.g. So we could include About the company but maybe better to stick to given ones. However the About Us is substantive; we could put it under About the role? Might be redundant. Could create a separate section "About the company" but not in list; risk of being considered not following instruction? The instruction says use h3 for section headings (e.g. ...). It doesn't say you cannot use other headings, just give examples. So we could include About the company. But to be safe, we could incorporate it into About the role paragraph? Might be too long. But we can add a separate About the company
as it's substantive.
Nevertheless, the instruction: "Prefer a few substantive sections over many thin ones." So we should not create many thin sections. Adding About the company might be okay.
But we also have "Work at Home Requirements" and "Travel". Could be placed under Schedule or maybe under Responsibilities? Probably Schedule.
Let's craft sections:
About the role
About the company
as it's substantive. Nevertheless, the instruction: "Prefer a few substantive sections over many thin ones." So we should not create many thin sections. Adding About the company might be okay. But we also have "Work at Home Requirements" and "Travel". Could be placed under Schedule or maybe under Responsibilities? Probably Schedule. Let's craft sections:About the role
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.
Responsibilities
Requirements
This is a hybrid role requiring office presence 1‑2 days per week; candidates must reside within 50 mi of Dallas TX, Chicago Metro, DC Metro, or Louisville area.