Lead, Technology Solutions

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. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Must preserve all substantive info. We need to parse the posting. The posting text: "Become a part of our caring community The Lead, Technology Solutions devises an effective strategy for executing and delivering on IT business initiatives. The Lead, Technology Solutions works on problems of diverse scope and complexity ranging from moderate to substantial. The Lead, Technology Solutions acts as a liaison and collaborates with the business and functional stakeholders to identify and deliver strategic enablement solutions. Advises executives to develop functional strategies (often segment specific) on matters of significance. Exercises independent judgment and decision making on complex issues regarding job duties and related tasks, and works under minimal supervision, Uses independent judgment requiring analysis of variable factors and determining the best course of action. Required Qualifications Use your skills to make an impact Hands-on software engineering leadership experience, with demonstrated ability to lead multiple engineering teams responsible for designing, building, modernizing, and operating enterprise-scale technology solutions.10+ years of progressive technology experience, including leadership of software engineering, application development, modernization, or technology transformation initiatives within complex enterprise environments.Proven experience leading and developing engineering teams, including engineering managers, technical leads, architects, developers, and other technical professionals, with a strong focus on talent development, accountability, and engineering excellence.Demonstrated ability to establish and execute technology and engineering roadmaps aligned with business strategy, product priorities, architectural direction, and enterprise technology standards.Strong understanding of modern software engineering practices, including Agile delivery, DevSecOps, continuous integration/continuous delivery (CI/CD), automated testing, cloud technologies, APIs, microservices, observability, resiliency, and secure software development.Experience providing technical and architectural leadership, evaluating solution options and making pragmatic technology decisions across scalability, performance, security, maintainability, cost, and speed to market.Proven accountability for end-to-end software delivery, from strategy and solution design through development, testing, implementation, production readiness, and ongoing operational support.Experience managing technology budgets, resources, capacity, vendor relationships, and delivery commitments across multiple concurrent initiatives and engineering teams.Ability to establish and track engineering and delivery performance measures, using data to improve software quality, predictability, productivity, reliability, and overall engineering effectiveness.Strong experience driving continuous improvement and technology modernization, including evaluating legacy platforms, reducing technical debt, improving development processes, and implementing scalable engineering practices.Demonstrated ability to partner closely with Product Management, Business, Architecture, Security, Infrastructure, Data, and Operations teams to translate business outcomes into executable technology solutions.Strong executive presence and communication skills, with the ability to communicate complex technical topics, investment needs, delivery risks, tradeoffs, and recommendations clearly to senior business and technology leaders.Proven ability to manage competing priorities and make independent, risk-informed decisions in complex environments with significant business, technology, regulatory, and operational dependencies.Experience establishing strong production ownership and operational discipline, including application reliability, incident management, root-cause analysis, disaster recovery, performance, availability, and service-level expectations.Demonstrated ability to build a culture of engineering excellence, innovation, collaboration, ownership, and continuous learning, while maintaining a strong focus on customer and consumer outcomes.Bachelor's degree in Computer Science, Software Engineering, Information Technology, Engineering, or a related field, or equivalent relevant professional experience. Preferred Qualifications Master's degree in Computer Science, Engineering, Information Systems, Business Administration, or a related discipline.Experience leading technology teams in a healthcare, health insurance, clinical, or other highly regulated environment.Experience delivering solutions involving clinical platforms, interoperability, enterprise integration, cloud modernization, data platforms, or healthcare technology ecosystems.Experience leading organizations through large-scale platform modernization or transformation, while maintaining the stability and reliability of existing production systems.Demonstrated experience managing a blended workforce of employees, contractors, strategic partners, and technology vendors. Scheduled Weekly Hours 40 Pay Range The compensation range below reflects a good faith estimate of starting base pay for full time (40 hours per week) employment at the time of posting. The pay range may be higher or lower based on geographic location and individual pay will vary based on demonstrated job related skills, knowledge, experience, education, certifications, etc. $117,600 - $161,700 per year This job is eligible for a bonus incentive plan. This incentive opportunity is based upon company and/or individual performance. Description Of Benefits Humana, Inc. and its affiliated subsidiaries (collectively, “Humana”) offers competitive benefits that support whole-person well-being. Associate benefits are designed to encourage personal wellness and smart healthcare decisions for you and your family while also knowing your life extends outside of work. Among our benefits, Humana provides 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 About Humana: Humana Inc. (NYSE: HUM) is a leading U.S. healthcare company. Through our Humana insurance services and our CenterWell healthcare services, we make it easier for the millions of people we serve to achieve their best health – delivering the care and service they need, when they need it. These efforts are leading to a better quality of life for people with Medicare and Medicaid, families, individuals, military service personnel, and communities at large. Learn more about what we offer at Humana.com and at CenterWell.com. Equal Opportunity Employer It is the policy of Humana not to discriminate against any employee or applicant for employment because of race, color, religion, sex, sexual orientation, gender identity, national origin, age, marital status, genetic information, disability or protected veteran status. It is also the policy of Humana to take affirmative action, in compliance with Section 503 of the Rehabilitation Act and VEVRAA, to employ and to advance in employment individuals with disability or protected veteran status, and to base all employment decisions only on valid job requirements. This policy shall apply to all employment actions, including but not limited to recruitment, hiring, upgrading, promotion, transfer, demotion, layoff, recall, termination, rates of pay or other forms of compensation and selection for training, including apprenticeship, at all levels of employment." We need to extract sections: About the role (maybe the initial description), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what content goes where. The posting includes: "Become a part of our caring community The Lead, Technology Solutions devises an effective strategy for executing and delivering on IT business initiatives. The Lead, Technology Solutions works on problems of diverse scope and complexity ranging from moderate to substantial. The Lead, Technology Solutions acts as a liaison and collaborates with the business and functional stakeholders to identify and deliver strategic enablement solutions. Advises executives to develop functional strategies (often segment specific) on matters of significance. Exercises independent judgment and decision making on complex issues regarding job duties and related tasks, and works under minimal supervision, Uses independent judgment requiring analysis of variable factors and determining the best course of action." That seems like a description of role/responsibilities. Could be "About the role" or "Responsibilities". We'll need to split. Then "Required Qualifications" heading appears, then a long list of qualifications (experience, etc). Then "Preferred Qualifications". Then "Scheduled Weekly Hours 40". Then "Pay Range" with salary. Then "Description Of Benefits". Then "About Us". Then EEO boilerplate. We need to produce sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which content belongs to each. Given the posting, we have: - About the role: maybe the initial paragraph describing the role and community. - Responsibilities: could be the bullet list of duties (the same as initial paragraph). But we need to avoid duplication. Perhaps we can treat the initial paragraph as "About the role" and then responsibilities as a list of duties derived from that paragraph? However we must not invent content. We need to preserve all substantive info. If we split the same content into two sections, we would be duplicating info, which is allowed? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid duplication, but better to avoid redundancy. However we need to follow the structure: use headings for sections only when posting has real specific content for it. So we need to decide which sections have content. We have content for: - About the role: maybe the first sentence "Become a part of our caring community" plus description. - Responsibilities: we have explicit duties described: devises strategy, works on problems, acts as liaison, advises executives, exercises independent judgment, etc. That's substantive. - Requirements: maybe the "Required Qualifications" section. - Qualifications: maybe the "Preferred Qualifications" section. - Skills: maybe we can extract skills from the qualifications (like software engineering leadership, Agile, DevSecOps, etc). But we need to avoid inventing. If we create a Skills section, we need to have explicit skills listed in the posting. The posting includes many skill-like items: "Hands-on software engineering leadership experience", "Strong understanding of modern software engineering practices, including Agile delivery, DevSecOps, CI/CD, automated testing, cloud technologies, APIs, microservices, observability, resiliency, and secure software development.", "Experience providing technical and architectural leadership", etc. Those could be considered skills. However the instruction says "Prefer a few substantive sections over many thin ones." So maybe we combine skills into Qualifications or Requirements. But we need to follow the given headings list; we can omit sections if no real specific content. So we could omit Skills if we don't have a distinct list separate from qualifications. However the posting does have a list of skills/experience; but they are under Required Qualifications. So we could treat Required Qualifications as the qualifications section, and Preferred Qualifications as another qualifications section? But we have both Requirements and Qualifications headings. Perhaps we can map: - Requirements: Required Qualifications (mandatory). - Qualifications: Preferred Qualifications (preferred). - Skills: maybe we can extract a list of skills from the qualifications (like software engineering leadership, Agile, DevSecOps, etc). But that would be splitting the same content; risk of duplication but maybe acceptable. However we need to avoid creating thin sections. If we create Skills, we need to have substantive content; we could list the skills explicitly: "Hands-on software engineering leadership experience", "Strong understanding of modern software engineering practices, including Agile delivery, DevSecOps, CI/CD, automated testing, cloud technologies, APIs, microservices, observability, resiliency, and secure software development.", "Experience providing technical and architectural leadership", etc. That is substantive. But we also have Responsibilities section; we could list responsibilities as bullet points derived from the description. We also have About the role: maybe a short paragraph about the community and role. We have Benefits: description of benefits. We have Pay: salary range. We have Schedule: Scheduled Weekly Hours 40. We also have About Us (company description) - not in the list of headings; we could omit or maybe treat as About the role? But we already have About the role. The About Us is company description; not required to include. We can drop it as it's not in the headings list; but we must preserve all substantive information. If we drop About Us, we lose that info. However the instruction says "Preserve ALL substantive information". Does that mean we must include all info from the posting, even if not fitting headings? We could include it as a paragraph under About the role or maybe under a generic section? But we are limited to the headings list; we cannot add arbitrary headings. However we could include it as a

under About the role (since it's about the company, not the role). But that might be misrepresenting. However the instruction says "Use