Director, Technology Solutions - Provider Solutions Engineering
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job posting. Key parts: - 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 a description; could be "About the role". We'll put that in
. 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 (some are sentences). We need to output
- for any list of duties/requirements/benefits. So we can treat each bullet as
- . The subheadings maybe not needed as headings; we can just list them as items. But we could also group under a heading "Responsibilities". According to instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have
Responsibilities
then a- with items.
Similarly "Qualifications" includes "Proven experience leading complex technology organizations..." etc. That's a list of qualifications. Then there is "Required Qualifications" with bullet list. Also "Preferred Qualifications" with "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" with paragraph about benefits.
We need sections: About the role (intro), Responsibilities, Qualifications (maybe combine Required and Preferred?), Benefits, Pay, Schedule. Also maybe Skills? Not explicit separate skills section; qualifications cover skills. We could include Skills if present but not needed.
We must not repeat job title as heading. Do not put Job ID etc.
We must not include boilerplate like Equal Opportunity Employer, About Us, etc. Remove those.
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all bullet points exactly as given (maybe slight rephrase? Should preserve meaning). We'll copy the bullet points.
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.
Qualifications (general):
- 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.
Required Qualifications (list):
- 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.
Preferred Qualifications:
- Master's degree
Scheduled Weekly Hours: 40
Pay Range: $172,200 - $236,900 per year. Also note bonus incentive plan.
Description Of Benefits: paragraph.
We need to output sections only when there is real specific content. So we will have:
- for any list,
for prose. It doesn't forbid other tags like . But to be safe, we can just put the required qualifications as a list, and then after that a paragraph for preferred qualifications. But we need to preserve the bullet points exactly. So we can do:
Qualifications
Required Qualifications:
- 10+ years of CRM platform engineering experience, including Salesforce, Salesforce Health Cloud, Service Cloud, and large-scale CRM implementations. ...
Preferred Qualifications:
- Master's degree
for headings inside Qualifications; still okay. Alternatively we could have separate
Required Qualifications
andPreferred Qualifications
. But the instruction says usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we stick to those. However, "Required Qualifications" is a subsection of Qualifications; we could treat it as part of Qualifications section. Similarly, we need Benefits section: we have paragraph about benefits. Pay section: we have pay range and bonus incentive plan. Schedule section: we have Scheduled Weekly Hours 40. We must not include filler like "commensurate with experience". Not present. Now we need to remove boilerplate: Equal Opportunity Employer, About Us, etc. Also remove "Description Of Benefits" heading? We'll keep the benefits paragraph under Benefits heading. We need to ensure we don't include duplicated lines. Let's craft the HTML. First, intro paragraph: combine the introductory sentences into one or multiple paragraphs? We'll put as
with the whole block. Intro text: "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." We need to ensure spacing; but it's fine. Now Responsibilities: list all bullets as above. We'll produce
Responsibilities
- ...
Qualifications
then maybe aRequired Qualifications:
then- required list. Then
Preferred Qualifications:
then- preferred list.
Now Benefits:
Benefits
... benefits paragraph ...
Pay:Pay
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. $172,200 - $
About the role
...intro paragraph...
Responsibilities
- ... list all responsibility bullets ...
Qualifications
maybe we split into Required and Preferred? But instruction says use headings like Qualifications. Could have one Qualifications section with sublist? Could also have Required Qualifications and Preferred Qualifications as subheadings? But they said usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have
Qualifications
and then within that we could have- for required and maybe a note for preferred. But we need to preserve all info. Could do two
- under same heading: one for Required Qualifications, one for Preferred Qualifications. Or we could make separate headings: Required Qualifications and Preferred Qualifications, but those are not in the list of example headings but could be considered under Qualifications. The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., not exclusive. So we could add more headings if needed, but better to stick to those. We'll put Qualifications heading and then inside we can have Required Qualifications: then
- etc. But that adds extra tags not prohibited. The instruction only says use
for section headings,
- for any list,