IT Lead Data Scientist

We need to output HTML fragment with sections: h3 headings for sections present with real content. Must not repeat job title. Must not include Job ID etc. Must include only sections with real specific content. We need to parse the posting. Overview: description about team, mission, etc. That's prose. Responsibilities: bullet list of duties. Qualifications: includes Education, Knowledge, Skills and Abilities Required, Preferred, Licenses And Certifications Preferred. Compensation: includes Minimum rate $202,488 annually, plus description about benefits etc. Also mentions benefits package. Travel: mentions travel 1 full week onsite per quarter and 1 additional onsite day per month. That's schedule? It's schedule info. Should we create a Schedule section? The rule: include a section only when posting has real, specific content for it. Travel schedule is specific. Could be under Schedule heading. But we also have Benefits section: they mention comprehensive benefits package including health, dental, vision, paid leave, tuition reimbursement, retirement benefits. That's specific enough for Benefits. Pay: they have minimum rate $202,488 annually. That's specific. So Pay section. Schedule: travel requirement. Could be Schedule. We also have "Other duties and/or projects as assigned." That's part of responsibilities. We need to remove boilerplate: EEO, equal opportunity, scam-warning, cookie/navigation/legal, duplicated lines, application instructions. Also remove "If you feel that the above description speaks directly to your strengths and capabilities, then please apply today!" (application instruction). Also remove "HACKENSACK MERIDIAN HEALTH (HMH) IS AN EQUAL OPPORTUNITY EMPLOYER ..." etc. Also remove "Our Network Hackensack Meridian Health (HMH) is a Mandatory Influenza Vaccination Facility As a courtesy to assist you in your job search, we would like to send your resume to other areas..." etc. We need to preserve all substantive information. We need to use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we can choose headings that match content. The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings? It says e.g., meaning examples. We can use those headings if appropriate. We have sections: Overview (maybe About the role), Responsibilities, Qualifications (maybe Requirements?), Skills (maybe part of Qualifications), Benefits, Pay, Schedule. We could combine Qualifications and Skills? But better to follow typical: Overview (About the role), Responsibilities, Qualifications (Education, Knowledge, Skills and Abilities), Skills (maybe separate?), Benefits, Pay, Schedule. But we must not create thin sections. Let's decide: - About the role: overview paragraph(s) describing team, mission, role purpose. - Responsibilities: bullet list. - Qualifications: includes education, required experience, skills, preferred qualifications, licenses/certs. Could be one section. - Benefits: bullet list of benefits. - Pay: paragraph with salary. - Schedule: travel requirement. We should not create Skills separate if it's covered in Qualifications. But we could still have Skills if we have specific skill list. However Qualifications already includes skills. To avoid thin sections, maybe combine Qualifications and Skills into one Qualifications section. But the instruction says we can use those headings as examples; not required to use all. So we can choose only those with substantive content. Thus we will output:

About the role

... overview paragraphs ...

Responsibilities

• ... each duty ...

Qualifications

... education, required experience, skills, preferred, licenses/certs ...

Benefits

• ... health, dental, vision, paid leave, tuition reimbursement, retirement benefits ...

Pay

Minimum rate of $202,488.00 annually.

Schedule

Travel requirement: 1 full week onsite per quarter and 1 additional onsite day per month.

We must ensure we preserve all substantive information from overview, responsibilities, qualifications, benefits, pay, schedule. Let's extract overview text: "Overview Our team members are the heart of what makes us better. At Hackensack Meridian Health we help our patients live better, healthier lives — and we help one another to succeed. With a culture rooted in connection and collaboration, our employees are team members. Here, competitive benefits are just the beginning. It’s also about how we support one another and how we show up for our community. Together, we keep getting better - advancing our mission to transform healthcare and serve as a leader of positive change. The Information Technology (IT) Lead Data Scientist will join a collaborative team of extremely talented Analysts, Engineers, Designers, and Managers across the Hackensack Meridian Health (HMH) network. This role requires using data analysis, applied mathematics, machine learning (ML), and large language models to build next-generation predictive solutions and artificial intelligence (AI) tools that enable clinicians and other end-users within the organization to perform their work more efficiently and effectively. In this role, there is a strong emphasis on using the agile development methodology to rapidly iterate and deploy impactful solutions within the healthcare organization. This position will require you to travel 1 full week onsite per quarter and 1 additional onsite day per month." We need to separate travel sentence maybe for Schedule section, but overview can include role description without travel? We could keep overview without travel sentence, moving travel to Schedule. That's okay; we still preserve all info. Thus overview paragraph(s) will be everything except the travel sentence. Let's craft overview: "Our team members are the heart of what makes us better. At Hackensack Meridian Health we help our patients live better, healthier lives — and we help one another to succeed. With a culture rooted in connection and collaboration, our employees are team members. Here, competitive benefits are just the beginning. It’s also about how we support one another and how we show up for our community. Together, we keep getting better - advancing our mission to transform healthcare and serve as a leader of positive change. The Information Technology (IT) Lead Data Scientist will join a collaborative team of extremely talented Analysts, Engineers, Designers, and Managers across the Hackensack Meridian Health (HMH) network. This role requires using data analysis, applied mathematics, machine learning (ML), and large language models to build next-generation predictive solutions and artificial intelligence (AI) tools that enable clinicians and other end-users within the organization to perform their work more efficiently and effectively. In this role, there is a strong emphasis on using the agile development methodology to rapidly iterate and deploy impactful solutions within the healthcare organization." Now Responsibilities: list each duty from the responsibilities block. Let's extract bullet points: - Work with HMH stakeholders to document and understand their objectives and ideate how AI/ML solutions might achieve those objectives. - Perform exploratory data analysis to understand the data available related to a particular business objective and if that data lends itself to the creation of an AI/ML solution that might achieve that business objective. - Optimizing Large Language Model (LLM) output with prompt engineering; building (RAG) pipelines. - Build AI/ML models that attempt to address a business objective given the data available; explore the model space to understand the optimal model for the particular use case and what the performance characteristics are. - Create repeatable, interpretable, and scalable models that can be seamlessly incorporated into analytic data products. - Engineer features by using business acumen to find new ways to combine data sources. - Write production-quality pipeline code used to load data, execute the AI/ML model, and store the results. - Perform analyses of AI/ML models and systems, such as fairness, bias, and equity audits; performance analyses; impact assessments; and interpretability reports. - Develop and commit Python code in such a way that it works in harmony with the code and systems being developed by the team's data engineers, software engineers, and data analysts. - Play a key role in communicating ML/AI methodology and impact to senior management to inform strategic decision-making. - Demonstrate strong communication and interpersonal skills that will be used in leading and motivating team members. - Proactively communicate with stakeholders about areas of concern regarding changes in work schedules. - Track and mentor individual team members about time and work management. - Develop and implement ML/AI strategies that align with business objectives. - Manage multiple projects. - Establish thought leadership within the organization. - Create a culture of collaboration, innovation, and continuous improvement within the team. - Ensure overall team performance in the delivery of ML/AI solutions. - Other duties and/or projects as assigned. - Adheres to HMH Organizational competencies and standards of behavior. We need to keep them as list items. Now Qualifications: includes Education, Knowledge, Skills and Abilities Required, Preferred, Licenses And Certifications Preferred. Let's extract required: Education, Knowledge, Skills and Abilities Required: - Bachelor's degree in STEM or another related/relevant field of study; and Master's degree in data science-related area. - Minimum 6+ years of experience working in a data science role. - Expert-level Python development experience. - Expert-level SQL experience. - Proficient in developing and interpreting complex statistical models. - Deep expertise in at least one aspect or area of data acquisition, cleaning, and curation; EDA; or statistical analysis. - Excellent understanding of most aspects of clinical data; Very proficient with querying and using clinical data; Deep expertise in at least one aspect or area of clinical data. - Excellent understanding of a wide range of ML models. - Able to improve model performance with complex feature engineering and hyperparameter tuning. - Ability to design and implement complex machine learning pipelines. - Deep expertise in at least one aspect of machine learning. - Expertise in prompt engineering methodology, model fine-tuning, and ability to create RAG pipelines. - Can create custom monitoring solutions as needed. - Deep expertise in at least one area of ML Ops. - Work effectively with team members and technical and non-technical stakeholders. - Excellent written and verbal communication skills. - Proficient computer skills including but not limited to Microsoft Office and Google Suite platforms. Preferred: - PhD degree. - Minimum of 6+ years of data analysis experience in healthcare. - Proficiency in Epic Clarity clinical data models. - Experience with Google Cloud Platform (Big Query, VertexAI, etc). - Experience with Git and GitHub - Experience with Docker. Licenses And Certifications Preferred: - Epic Clarity Data Model. - Epic Clarity Clinical Data Model. - Google Machine Learning Engineer Certification. We need to preserve all that. Could be a paragraph or list. Since it's a list of qualifications, we can use

• for each item. But the instruction says use
  • for any list of duties/requirements/benefits. So we should use list for qualifications as well. Thus Qualifications section will have
    • items. But we have subcategories (Required, Preferred, Licenses And Certifications Preferred). We could keep them as separate paragraphs with headings? But we cannot add extra headings besides

      sections. We could embed the categorization within list items text, e.g., "Required: Bachelor's degree..." etc. That's fine. Thus Qualifications

      with each bullet representing a qualification item. Might be many items; that's okay. Now Benefits: they mention "comprehensive benefits package, including health, dental, vision, paid leave, tuition reimbursement, and retirement benefits." Also earlier they said "competitive benefits are just the beginning." But we should list the specific benefits: health, dental, vision, paid leave, tuition reimbursement, retirement benefits. Thus Benefits
      • Health insurance
      • Dental insurance
      • Vision insurance