Director, Technology Solutions - Provider Solutions Engineering
Humana · Frisco, TX · 3 wk ago
On-siteConsulting$172k–$237k/yrFull-time
We need to output HTML fragment with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting.
The posting includes:
- Intro: "Become a part of our caring community The Director, Provider Solutions Engineering devises an effective strategy for executing and delivering on IT business initiatives. We ask that you have an in-depth understanding of how organization capabilities interrelate across the function or segment. The Director, Provider Solutions Engineering serves as the strategic technology leader responsible for defining Humana's Provider engagement and engineering. In partnership with business and operational teams, this role is responsible to identify and implement strategic technology solutions that improve provider engagement, associate effectiveness, and business outcomes. The Director collaborates across a highly matrixed organization to establish technology strategy, drive large-scale transformation initiatives, and deliver modern customer relationship management capabilities that support the end-to-end provider experience. This leader is accountable for translating business priorities into actionable roadmaps, driving execution excellence, strengthening engineering discipline, and ensuring technology investments align with enterprise architecture, regulatory requirements, and organizational objectives. The role is responsible for establishing the future-state Provider engagement vision, accelerating AI-enabled capabilities, modernizing technology platforms, and fostering a high-performing engineering culture that consistently delivers measurable business value."
That's about the role. So we can have
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting.
The posting includes:
- Intro: "Become a part of our caring community The Director, Provider Solutions Engineering devises an effective strategy for executing and delivering on IT business initiatives. We ask that you have an in-depth understanding of how organization capabilities interrelate across the function or segment. The Director, Provider Solutions Engineering serves as the strategic technology leader responsible for defining Humana's Provider engagement and engineering. In partnership with business and operational teams, this role is responsible to identify and implement strategic technology solutions that improve provider engagement, associate effectiveness, and business outcomes. The Director collaborates across a highly matrixed organization to establish technology strategy, drive large-scale transformation initiatives, and deliver modern customer relationship management capabilities that support the end-to-end provider experience. This leader is accountable for translating business priorities into actionable roadmaps, driving execution excellence, strengthening engineering discipline, and ensuring technology investments align with enterprise architecture, regulatory requirements, and organizational objectives. The role is responsible for establishing the future-state Provider engagement vision, accelerating AI-enabled capabilities, modernizing technology platforms, and fostering a high-performing engineering culture that consistently delivers measurable business value."
That's about the role. So we can have About the role
with paragraphs.
Then "Key Responsibilities" with subheadings: Technology Leadership, Provider CRM Strategy, Delivery Execution Excellence, Platform Stewardship & Operational Excellence, Financial & Vendor Governance, Talent Development & Culture. Each has bullet points (list items). So we can have Responsibilities
with - each bullet.
Then "Qualifications" section includes "Proven experience leading complex technology organizations..." etc. Then "Required Qualifications" with bullet list. Then "Preferred Qualifications" bullet list (Master's degree). Also "Scheduled Weekly Hours 40" and "Pay Range" with $172,200 - $236,900 per year, plus bonus incentive plan. Also "Description Of Benefits" paragraph.
Also "About Us" about Humana. That could be considered "About the role"? Actually "About Us" is company description; could be separate but not required. The instruction: include a section ONLY when posting has real specific content for it. We have content for About the role (intro). Responsibilities (key responsibilities). Qualifications (both required and preferred). Benefits (description). Pay (range). Schedule (Scheduled Weekly Hours 40). Skills? Not explicitly separate; maybe we can embed skills within qualifications. But we could have a Skills section if there is explicit list of skills; not really. So we may omit Skills.
We must not repeat job title as heading. No Job ID. Remove boilerplate: Equal Opportunity Employer etc. Also remove navigation/legal/EEO etc. Also remove application instructions (none). Remove duplicated lines.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep all bullet points exactly as given? We can keep them but maybe rephrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep the content verbatim (or close) but we can format as list items. Should not omit any bullet.
Let's extract bullet points.
From "Key Responsibilities":
Technology Leadership:
- Serve as the strategic technology leader for Provider engagement and related provider experience capabilities.
- Partner effectively within a matrixed organization to align business priorities, regulatory requirements, architecture standards, and technology investments.
- Provide strategic direction and oversight for implementing new programs, platform enhancements, and large-scale technology initiatives.
- Establish and promote engineering best practices, delivery discipline, operational excellence, and continuous improvement.
Provider CRM Strategy:
- Lead the development and execution of a comprehensive Provider engagement strategy in consideration of the broader provider experience vision.
- Define the end-to-end provider experience target state, roadmap, and investment priorities.
- Drive adoption of modern CRM capabilities, AI-powered solutions, automation, and emerging technologies to improve provider and associate experiences.
Delivery Execution Excellence:
- Lead the delivery and modernization of provider-facing and associate-facing technology solutions.
- Drive execution across multiple teams and technology domains to ensure successful delivery of strategic initiatives and business outcomes.
- Promote Agile, DevSecOps, quality engineering, and AI-assisted delivery practices across the software development lifecycle.
- Ensure effective governance, planning, risk management, and performance reporting for technology initiatives.
Platform Stewardship & Operational Excellence:
- Maintain the health, resiliency, security, compliance, and scalability of supporting platforms and services.
- Ensure solutions are designed for reliability, interoperability, scalability, and long-term sustainability.
Financial & Vendor Governance:
- Manage technology investments, budgets, and resource allocation to maximize business value.
- Build internal engineering capabilities while strategically applying vendors and partners to accelerate delivery and modernization efforts.
- Ensure critical knowledge, intellectual property, and operational ownership remain institutionalized within the organization.
Talent Development & Culture:
- Build, lead, and develop high-performing technology teams focused on partnership, accountability, innovation, and continuous learning.
- Foster a culture of engineering excellence, collaboration, inclusion, and customer-centricity.
Now Qualifications:
"Qualifications Proven experience leading complex technology organizations and large-scale transformation initiatives.
Deep understanding of CRM platforms, digital experiences, enterprise applications, and customer engagement technologies.
Demonstrated success operating within highly matrixed environments and influencing cross-functional stakeholders.
Experience leading technology modernization, cloud adoption, platform engineering, and AI-enabled solutions.
Strong business acumen with the ability to connect technology strategy to business outcomes.
Exceptional leadership, communication, organizational, and relationship management skills."
Then "Required Qualifications Use your skills to make an impact 10+ years of CRM platform engineering experience, including Salesforce, Salesforce Health Cloud, Service Cloud, and large-scale CRM implementations.
Deep expertise in provider engagement technologies within healthcare, payer, or provider organizations.
Experience designing and implementing API-driven integrations across relationship management, provider portals, workflow platforms, and enterprise systems.
Experience with cloud-native architecture, microservices, event-driven integration, and enterprise-scale platform modernization.
Proven experience delivering AI-enabled capabilities, automation, and experienced workflow solutions.
Strong knowledge of healthcare regulatory requirements, including CMS interoperability, provider data, privacy, security, and compliance considerations."
Then "Preferred Qualifications Master's degree"
Also "Scheduled Weekly Hours 40"
Pay Range: "$172,200 - $236,900 per year This job is eligible for a bonus incentive plan. This incentive opportunity is based upon company and/or individual performance."
Benefits: "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 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."
We could include About Us as a section maybe "About the company" but not in list of allowed headings. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not add About Us. Could we incorporate About Us into About the role? Probably not; but we could omit it as it's not required headings. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid omitting sections not in the list. So we can omit About Us.
Now we need to decide about "Requirements" heading. The posting has "Qualifications" and "Required Qualifications" and "Preferred Qualifications". There's no separate "Requirements" section besides qualifications. But we could treat "Qualifications" as the heading for both required and preferred. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Qualifications. We might also have Requirements if there is distinct content; but we don't have separate requirements beyond qualifications. So we can omit Requirements.
Skills: we don't have explicit skills list; we could omit.
Thus final sections: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule.
We need to ensure we include all substantive info from each.
Let's craft HTML.
About the role: combine the intro paragraphs into one or multiple
. We'll keep as
with the text.
Responsibilities:
Responsibilities
then with each bullet as - . Should we group under subheadings? Not required; we can just list all bullets. But to preserve structure maybe we keep as list; subheadings not needed. However we might lose some grouping but still all content present. It's okay.
Qualifications: we need to include the bullet points under "Qualifications" (the first set) and then Required Qualifications and Preferred Qualifications. Could combine all into one list? But we need to preserve distinction? The instruction: preserve all substantive information; not required to keep headings inside. Could just list all bullet points under Qualifications. However there is a phrase "Use your skills to make an impact" preceding Required Qualifications; that's fluff but we can keep as part of the bullet? Actually it's a sentence: "Use your skills to make an impact 10+ years of CRM platform engineering experience..." It seems like a heading but we can treat as part of the bullet. We'll just include the bullet points as given.
Thus Qualifications list will include:
- Proven experience leading complex technology organizations and large-scale transformation initiatives.
- Deep understanding of CRM platforms, digital experiences, enterprise applications, and customer engagement technologies.
- Demonstrated success operating within highly matrixed environments and influencing cross-functional stakeholders.
- Experience leading technology modernization, cloud adoption, platform engineering, and AI-enabled solutions.
- Strong business acumen with the ability to connect technology strategy to business outcomes.
- Exceptional leadership, communication, organizational, and relationship management skills.
- 10+ years of CRM platform engineering experience, including Salesforce, Salesforce Health Cloud, Service Cloud, and large-scale CRM implementations.
- Deep expertise in provider engagement technologies within healthcare, payer, or provider organizations.
- Experience designing and implementing API-driven integrations across relationship management, provider portals, workflow platforms, and enterprise systems.
- Experience with cloud-native architecture, microservices, event-driven integration, and enterprise-scale platform modernization.
- Proven experience delivering AI-enabled capabilities, automation, and experienced workflow solutions.
- Strong knowledge of healthcare regulatory requirements, including CMS interoperability, provider data, privacy, security, and compliance considerations.
- Master's degree
We need to ensure we didn't miss any: The "Required Qualifications" line includes "Use your skills to make an impact" preceding the list; we omitted that phrase. Is that substantive? It's more of a filler; but it's part of the posting. However it's not a requirement; it's just a phrase. The instruction says preserve ALL substantive information; do not invent or summarize away detail. The phrase "Use your skills to make an impact" is not a requirement but it's part of the text. Should we keep it? It's not a bullet; it's a sentence. Could be considered boilerplate? It's not navigation
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Qualifications. We might also have Requirements if there is distinct content; but we don't have separate requirements beyond qualifications. So we can omit Requirements. Skills: we don't have explicit skills list; we could omit. Thus final sections: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule. We need to ensure we include all substantive info from each. Let's craft HTML. About the role: combine the intro paragraphs into one or multiple
. We'll keep as
with the text. Responsibilities:
Responsibilities
then- with each bullet as
- . Should we group under subheadings? Not required; we can just list all bullets. But to preserve structure maybe we keep as list; subheadings not needed. However we might lose some grouping but still all content present. It's okay. Qualifications: we need to include the bullet points under "Qualifications" (the first set) and then Required Qualifications and Preferred Qualifications. Could combine all into one list? But we need to preserve distinction? The instruction: preserve all substantive information; not required to keep headings inside. Could just list all bullet points under Qualifications. However there is a phrase "Use your skills to make an impact" preceding Required Qualifications; that's fluff but we can keep as part of the bullet? Actually it's a sentence: "Use your skills to make an impact 10+ years of CRM platform engineering experience..." It seems like a heading but we can treat as part of the bullet. We'll just include the bullet points as given. Thus Qualifications list will include: - Proven experience leading complex technology organizations and large-scale transformation initiatives. - Deep understanding of CRM platforms, digital experiences, enterprise applications, and customer engagement technologies. - Demonstrated success operating within highly matrixed environments and influencing cross-functional stakeholders. - Experience leading technology modernization, cloud adoption, platform engineering, and AI-enabled solutions. - Strong business acumen with the ability to connect technology strategy to business outcomes. - Exceptional leadership, communication, organizational, and relationship management skills. - 10+ years of CRM platform engineering experience, including Salesforce, Salesforce Health Cloud, Service Cloud, and large-scale CRM implementations. - Deep expertise in provider engagement technologies within healthcare, payer, or provider organizations. - Experience designing and implementing API-driven integrations across relationship management, provider portals, workflow platforms, and enterprise systems. - Experience with cloud-native architecture, microservices, event-driven integration, and enterprise-scale platform modernization. - Proven experience delivering AI-enabled capabilities, automation, and experienced workflow solutions. - Strong knowledge of healthcare regulatory requirements, including CMS interoperability, provider data, privacy, security, and compliance considerations. - Master's degree We need to ensure we didn't miss any: The "Required Qualifications" line includes "Use your skills to make an impact" preceding the list; we omitted that phrase. Is that substantive? It's more of a filler; but it's part of the posting. However it's not a requirement; it's just a phrase. The instruction says preserve ALL substantive information; do not invent or summarize away detail. The phrase "Use your skills to make an impact" is not a requirement but it's part of the text. Should we keep it? It's not a bullet; it's a sentence. Could be considered boilerplate? It's not navigation