2027 Summer Intern, Data Management

We need to output HTML fragment with sections: About the role? Actually the posting includes "What You Can Expect" and "How You'll Create Impact" and "What Makes You Stand Out" and "Your Background". Also there is a paragraph at top about Zimmer Biomet mission etc. That could be "About the role" or maybe "About the company". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which sections are present. We have: - Intro paragraph about Zimmer Biomet mission, commitment, etc. Could be "About the role" or maybe "About the company". Since they said "About the role" as example, we can use that for the introductory description. - "What You Can Expect" describes role responsibilities: supports data management group, etc. That could be "Responsibilities". Actually responsibilities are more detailed later in "How You'll Create Impact". So we could treat "What You Can Expect" as a brief overview, maybe "About the role". But we already used that. Let's think: The posting includes sections: "What You Can Expect", "How You'll Create Impact", "What Makes You Stand Out", "Your Background". Also there is a bullet list of technologies etc. We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should include sections only if there is real specific content. We have content for: - About the role: could be the introductory paragraph about Zimmer Biomet and the role's purpose. - Responsibilities: could be the "How You'll Create Impact" list (detailed duties). Also "What You Can Expect" could be part of responsibilities but we can combine. - Requirements: could be "What Makes You Stand Out" (skills/experience) and "Your Background" (education, availability). Could split into Requirements and Qualifications. - Skills: maybe list of technologies (SQL, Snowflake, Python, Cortex AI, dbt, Git, etc.) could be Skills. - Benefits: not mentioned besides generic "development opportunities, robust employee resource groups (ERGs), a flexible working environment, location specific competitive total rewards, wellness incentives and a culture of recognition and performance awards." That's in the intro paragraph after mission. That is benefits. So we can include Benefits section. - Pay: not specified (no salary). So we should NOT include Pay. - Schedule: mentions full-time (40 hours/week) throughout the co-op session. That's schedule info. So we can include Schedule. We must not include headings with filler like "not specified". So we omit Pay. We must not repeat job title as heading. We must not include Job ID etc. We must remove boilerplate like EEO etc. At end there is "EOE/M/F/Vet/Disability". Remove. Also remove duplicated lines. Now craft HTML. Structure:

About the role

Intro paragraph about Zimmer Biomet mission and role purpose.

Responsibilities

• ... list items from "How You'll Create Impact". Also maybe include "What You Can Expect" points.

Requirements

• ... from "What Makes You Stand Out" and "Your Background" (education, availability, work authorization).

Skills

• SQL, Snowflake, Python, Cortex AI, dbt or comparable SQL-based transformation frameworks, Git version control, etc.

Benefits

• Development opportunities
• Robust employee resource groups (ERGs)
• Flexible working environment
• Location‑specific competitive total rewards
• Wellness incentives
• Culture of recognition and performance awards

Schedule

Full‑time (40 hours/week) throughout the co‑op session.

We need to ensure we preserve all substantive information. Let's extract details. Intro paragraph: "At Zimmer Biomet, we believe in pushing the boundaries of innovation and driving our mission forward. As a global medical technology leader for nearly 100 years, a patient’s mobility is enhanced by a Zimmer Biomet product or technology every 8 seconds. As a Zimmer Biomet team member, you will share in our commitment to providing mobility and renewed life to people around the world. To support our talent team, we focus on development opportunities, robust employee resource groups (ERGs), a flexible working environment, location specific competitive total rewards, wellness incentives and a culture of recognition and performance awards. We are committed to creating an environment where every team member feels included, respected, empowered and recognised." That's the intro. Now "What You Can Expect": paragraph: "The Data Management Intern supports the data management group which includes Data Engineering, Master Data Management, Data Pipelines, Data Visualization and Agentic Based solutions. The role will support Data Engineering in the design, development, and maintenance of reliable data pipelines, transformations, and models. These objects support analytics, reporting, and operational workflows. The role will also be involved in creating AI Agents for the department and its stakeholders. The role works closely with architects, analysts, and business stakeholders to translate requirements into secure, scalable, and high-quality data solutions. The intern is expected to partner with team members while owning assigned deliverables. The desired candidate should communicate clearly, bring structure to day-to-day technical work, and contribute to timely team outcomes. Key technologies will be SQL, Snowflake, Python and Cortex AI. The intern will be hands-on in contributing to real world solutions and will build job skills and experience that cannot be achieved in academia alone." We can incorporate some of that into Responsibilities or About the role. But we already used About the role for company mission. Maybe better to put "What You Can Expect" as part of About the role? But we already used About the role for mission. Could rename About the role to "About the role" containing both mission and role description. That's okay. But we need to avoid duplication. We'll include the mission paragraph plus the "What You Can Expect" paragraph in About the role. Then Responsibilities: the detailed list from "How You'll Create Impact". Let's extract each bullet: - Design, build, test, and maintain SQL-based data pipelines, transformations, and data models in Snowflake and other approved cloud data environments. - Develop Python-based data processing, automation, and integration workflows. - Ingest and process structured and semi-structured data from databases, APIs, files, SaaS applications, and cloud storage. - Implement ETL/ELT processes using SQL, Python, dbt or equivalent transformation frameworks, Snowflake capabilities, and orchestration tools (such as Dagster or similar). - Participate actively in Agile ceremonies and deliver assigned sprint commitments with quality and urgency. - Use version control and established CI/CD practices to develop, review, test, and deploy data solutions. - Apply data-quality, data-governance, security, and privacy practices to the design and operation of data products. - Troubleshoot data-pipeline issues, investigate root causes, and make performance and reliability improvements. - Maintain clear technical documentation, monitoring, alerting, and operational procedures for supported pipelines. - Collaborate with cross-functional partners to clarify requirements, communicate progress and risks, and deliver fit-for-purpose technical solutions. Also note: "This is not an exhaustive list of duties or functions and might not necessarily comprise all of the essential functions for purposes of the Americans with Disabilities Act." That's boilerplate; we should remove. Now Requirements: from "What Makes You Stand Out" and "Your Background". What Makes You Stand Out bullet list: - SQL and data modeling; Snowflake or a comparable cloud data warehouse preferred. - Some form of development experience is helpful, Python strongly preferred - dbt or comparable SQL-based transformation frameworks is helpful - Version control experience, preferably Git-supported - Ability to work effectively with cross-functional teams - Strong analytical, problem-solving, organizational, and critical-thinking skills. - Clear written and verbal communication skills - Ability to work independently and deal with ambiguity - Ability to collaborate across teams and geographies - Curious, proactive and ready to learn Your Background: - Pursuing a degree in Computer Science, Computer Engineering, Information Systems, Mathematics or other highly technical degree - Must be actively enrolled in an academic program for the entire duration of the assignment. - Must be available to work full-time (40 hours/week) throughout the co-op session - Must be authorized to work in the U.S. without requiring employer sponsorship - Travel Expectations None (we can drop as minor metadata) We could combine these into Requirements. Or split into Requirements and Qualifications. But we have limited headings; we can use Requirements for the background/eligibility, and Skills for technical skills. However the instruction says we can use Qualifications as heading. But we need to decide. We have sections: About the role, Responsibilities, Requirements, Skills, Benefits, Schedule. That seems fine. We need to ensure we don't include filler like "not specified". We have all specific. Now we need to output only HTML fragment, no /, no markdown fences. Let's craft. We'll need to escape any HTML special characters? Not needed. We'll produce:

About the role

At Zimmer Biomet, we believe in pushing the boundaries of innovation and driving our mission forward. As a global medical technology leader for nearly 100 years, a patient’s mobility is enhanced by a Zimmer Biomet product or technology every 8 seconds. As a Zimmer Biomet team member, you will share in our commitment to providing mobility and renewed life to people around the world. To support our talent team, we focus on development opportunities, robust employee resource groups (ERGs), a flexible working environment, location specific competitive total rewards, wellness incentives and a culture of recognition and performance awards. We are committed to creating an environment where every team member feels included, respected, empowered and recognised.

The Data Management Intern supports the data management group which includes Data Engineering, Master Data Management, Data Pipelines, Data Visualization and Agentic Based solutions. The role will support Data Engineering in the design, development, and maintenance of reliable data pipelines, transformations, and models. These objects support analytics, reporting, and operational workflows. The role will also be involved in creating AI Agents for the department and its stakeholders. The role works closely with architects, analysts, and business stakeholders to translate requirements into secure, scalable, and high-quality data solutions. The intern is expected to partner with team members while owning assigned deliverables. The desired candidate should communicate clearly, bring structure to day-to-day technical work, and contribute to timely team outcomes. Key technologies will be SQL, Snowflake, Python and Cortex AI. The intern will be hands-on in contributing to real world solutions and will build job skills and experience that cannot be achieved in academia alone.

Responsibilities

• Design, build, test, and maintain SQL-based data pipelines, transformations, and data models in Snowflake and other approved cloud data environments.
• Develop Python-based data processing, automation, and integration workflows.
• Ingest and process structured and semi-structured data from databases, APIs, files, SaaS applications, and cloud storage.
• Implement ETL/ELT processes using SQL, Python, dbt or equivalent transformation frameworks, Snowflake capabilities, and orchestration tools (such as Dagster or similar).
• Participate actively in Agile ceremonies and deliver assigned sprint commitments with quality and urgency.
• Use version control and established CI/CD practices to develop, review, test, and deploy data solutions.
• Apply data-quality, data-governance, security, and privacy practices to the design and operation of data products.
• Troubleshoot data-pipeline issues, investigate root causes, and make performance and reliability improvements.
• Maintain clear technical