Manager Data Engineering AI

We need to output HTML fragment with sections: Overview (maybe not a heading? The overview is prose). Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. The posting includes Overview (maybe treat as About the role). Responsibilities present. Qualifications present. Pay present (Base compensation range). Benefits present (description). Schedule not mentioned (no schedule). Skills? Could be derived from qualifications but we have Qualifications section; maybe we can put Skills as separate if there is explicit skills list. The posting includes qualifications like experience, tools, etc. Could treat that as Qualifications. Could also have Skills section for technical skills? But we should not create thin sections. Better to have sections: About the role (overview), Responsibilities, Qualifications, Pay, Benefits. Possibly also Requirements? The qualifications already cover requirements; but we could split Requirements (like education, years experience) and Qualifications (preferred). However instructions: Use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should include only those with real content. The posting includes: Overview (About the role). Responsibilities. Qualifications (both required and preferred). Pay. Benefits. No explicit Skills separate; but we could treat the technical skills as Skills section. However we already have Qualifications covering required and preferred; maybe we can put Skills as a subsection? But better to follow instruction: If we have content for Skills, we can make a Skills section. The posting lists many specific skills: data engineering, Hadoop, Spark, Databricks, AWS, Snowflake, AI engineering concepts, RAG, Prompt Engineering, Langchain, LangGraph, ML Ops, LLM Ops, Datarobot, software development, database management, Microsoft Office Suite, healthcare data, Agile environment. Those could be Skills. However Qualifications also includes those. To avoid duplication, we could treat Qualifications as the list of requirements (education, years experience) and Skills as technical competencies. But the posting lumps them together. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep all info. We can split into two sections: Qualifications (education, years experience, management experience, project management) and Skills (technical tools). But we must not invent headings that have filler. If we split, we need to ensure each section has real content. We can extract from the text. Let's parse: Overview paragraph: "We are seeking an experienced Manager, Engineering- AI to lead our data engineering team. This individual will play a crucial role in overseeing the development of strategic perspectives regarding IT architecture and business needs. The Manager of Engineering will develop and implement data architecture and engineering strategies leveraging innovations in AI while exemplifying strong software development experience when working in an Agile environment. This individual will provide guidance to employees in accordance with established policies and management directives." That's About the role. Responsibilities: multiple bullet-like sentences. We'll put each as

under

. Qualifications: "Bachelor’s degree or equivalent work experience 7+ years of total data engineering/IT/Project Management experience out of which at least 2 years must be management experience. 2+ years’ experience leading small to mid-size projects through application of Project Management methodologies and artifacts. 4+ years’ experience with data sets, Hadoop, Spark and/or other data integration/ETL tools like databricks, AWS tech stack, snowflake etc 2+ years of experience working on AI engineering concepts and tools like RAG, Prompt Engineering, Langchain, LangGraph etc Familiarity with ML Ops and LLM Ops capabilities and tools like Datarobot 2+ years of hands-on experience in software development and database management. Proficiency in Microsoft Office Suite." Preferred Qualifications: "Experience with healthcare data preferably in a data operations role. Experience working in an Agile environment." Cognitive/Mental Requirements: list of abilities. Could be considered Requirements or Skills? Might be better as Requirements (soft skills). But we already have Qualifications for hard requirements. Could make a Requirements section for cognitive/mental abilities. However the instruction says use headings like Requirements, Qualifications, Skills. We could put cognitive/mental under Requirements. Then Qualifications for education/experience. Skills for technical tools. But we risk duplication. Let's decide: - About the role (overview) - Responsibilities - Requirements (cognitive/mental abilities) - Qualifications (education, years experience, management, project management, software dev, DB, Office) - Skills (technical: data engineering tools, AI/ML Ops, healthcare data, Agile) - Pay - Benefits Check if each has content. Requirements: list of abilities (communicate, summarize, apply knowledge, win trust, lead, motivate, big picture vision, develop skill sets, adjust, manage conflict, break silos, value individuals, deploy techniques, accomplish goals, prioritize tasks, make sound decisions). That's substantive. Qualifications: education, years experience, management, project management, data sets/Hadoop/Spark/etc, AI engineering concepts, ML Ops/LLM Ops, software dev/database mgmt, MS Office. Skills: Could include preferred qualifications (healthcare data, Agile) plus maybe the specific tools listed? But those already in Qualifications. To avoid duplication, maybe we treat Qualifications as the hard requirements (education, years, etc) and Skills as the specific technical tools and preferred qualifications. However the Qualifications already lists those tools. So we might just have Qualifications covering all, and not have Skills. But we need to decide. Given instruction: Prefer a few substantive sections over many thin ones. So better to have fewer sections: About the role, Responsibilities, Qualifications (including education, experience, technical skills, preferred), Pay, Benefits. That's 5 sections. That seems reasonable. We'll not split Requirements or Skills separately. Thus we will output:

About the role

Overview paragraph...

Responsibilities

• ...
...

Qualifications

• Bachelor’s degree or equivalent work experience
• 7+ years of total data engineering/IT/Project Management experience, with at least 2 years management experience
• 2+ years’ experience leading small to mid-size projects using Project Management methodologies and artifacts
• 4+ years’ experience with data sets, Hadoop, Spark and/or other data integration/ETL tools (e.g., Databricks, AWS tech stack, Snowflake)
• 2+ years of experience working on AI engineering concepts and tools (e.g., RAG, Prompt Engineering, Langchain, LangGraph)
• Familiarity with ML Ops and LLM Ops capabilities and tools (e.g., Datarobot)
• 2+ years of hands‑on experience in software development and database management
• Proficiency in Microsoft Office Suite
• Preferred: Experience with healthcare data preferably in a data operations role
• Preferred: Experience working in an Agile environment
But we need to preserve all substantive information, not lose any. The cognitive/mental requirements are also substantive; if we omit them, we lose info. So we need to include them somewhere. Could include them under Qualifications as well, but they are not qualifications per se; they are abilities. However we could incorporate them into Qualifications as bullet points. That would preserve all info. The instruction says use headings like Requirements, Qualifications, Skills. But we can still put them under Qualifications if we want fewer sections. However the instruction says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It's examples, not mandatory to use all. It says "include a section ONLY when the posting has real, specific content for it". So we can choose which headings to use. We could use Requirements for cognitive/mental abilities, and Qualifications for education/experience/technical. That would be two sections, preserving all info. That seems better: we have Requirements (soft skills) and Qualifications (hard). Then we still have About the role, Responsibilities, Pay, Benefits. That's 6 sections. All have real content. Let's do that. Now extract cognitive/mental requirements list: From text: "Cognitive/Mental Requirements Ability to communicate simple and complex messages to the team in a manner that is clear, persuasive, and sincere. Ability to summarize complex and/or technical information into easy-to-understand pieces, distinguishing message delivery from analysis. Ability to apply organizational, industry knowledge to facilitate process improvement that optimizes functional area to positively impact strategic initiatives of the department and organization. Ability to win trust and confidence of team members even when dealing with unpopular decisions. Ability to lead and motivate team through day to day as well as during unclear or challenging conditions. Ability to provide big picture vision, align goals with larger department and organizational ones. Ability to develop well rounded skill sets regarding business, technical and interpersonal skills. Ability to adjust quickly to changing assignments, processes and people while identifying opportunities to further growth and development of self and processes. Ability to proactively manage and resolve conflict, help team find a ‘win-win’ solution. Ability to break down silos that impact cooperations and partnership. Ability to value team members as individuals while embraces differences. Ability to deploy variety of techniques to establish rapport, gain commitment from and adapt to the decision-making styles of executives, department leaders and outside groups. Ability to accomplish goals by setting appropriate objectives and planning effectively while monitoring plans and adjusting as needed to keep plans realistic and focused. Ability to prioritize tasks against business prioritize, effectively manage time against priorities to accomplish them and allocate resources affectively to meet deadlines. Ability to make sound situational decisions even in absence of precedent or experience." We need to split into list items. Each sentence starts with "Ability to". We'll make each as

. Now Qualifications: we need to include both required and preferred. We'll list as

each. Now Pay: "Base compensation ranges from $145,000.00 to $175,000.00. Specific offers are determined by various factors, such as experience, education, skills, certifications, and other business needs. This role is eligible for discretionary bonus consideration." We'll put that in

under Pay heading. Benefits: "Cotiviti offers team members a competitive benefits package to address a wide range of personal and family needs, including medical, dental, vision, disability, and life insurance coverage, 401(k) savings plans, paid family leave, 9 paid holidays per year, and 17-27 days of Paid Time Off (PTO) per year, depending on specific level and length of service with Cotiviti. For information about our benefits package, please refer to our Careers page." We'll put that in

under Benefits heading. We must exclude boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove lines like "Date of posting: 9/21/2026 Applications are assessed on a rolling basis. We anticipate that the application window will close on 11/21/2026 but the application window may change depending on the volume of applications received or close immediately if a qualified candidate is selected." That's application instructions/boilerplate; remove. Also remove "Since this job will be based remotely, all interviews will be conducted virtually." That's also maybe considered application instruction; remove. Now ensure we preserve all substantive info: overview, responsibilities, cognitive/mental requirements, qualifications (including preferred), pay, benefits. Now produce HTML fragment. We'll need to wrap each section in

and then content. Let's craft. Overview paragraph: combine the two sentences? Actually there are three sentences: "We are seeking an experienced