Cloud Data Platform Engineer

We need to output HTML fragment with sections only if content present. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we must not repeat job title as heading. The posting includes sections: Description (About Northern Trust), Position Overview, Key Responsibilities, Qualifications: Education & Experience, Skills & Competencies, Key Success Metrics, Salary Range, Benefits description, Work Authorization, Working with Us, Reasonable Accommodation. We need to map to allowed headings: About the role (maybe Position Overview), Responsibilities (Key Responsibilities), Requirements (maybe Qualifications?), Qualifications (Education & Experience?), Skills (Skills & Competencies), Benefits (benefits description), Pay (Salary Range), Schedule (if present). There's no schedule info, so omit Schedule. We must not include headings with filler. Also we must not include duplicated lines, boilerplate like AI insights, cookie/navigation/legal/EEO etc. Remove those lines. We need to preserve all substantive info. So we need to include content from About Northern Trust (maybe as About the role?), Position Overview (maybe also part of About the role). But we must not repeat job title as heading. We can have

About the role

with paragraph(s) containing Position Overview and maybe About Northern Trust combined? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have those headings exactly. We need to decide what goes under each. - About the role: could include Position Overview and maybe brief about Northern Trust? The posting has "About Northern Trust" separate. Might be considered part of About the role? Probably yes. We'll include both. - Responsibilities: Key Responsibilities bullet list. - Requirements: maybe Qualifications: Education & Experience? Actually Requirements could be qualifications. But we also have Qualifications heading separate. The list includes both Requirements and Qualifications as possible headings. We need to decide which to use. The posting has "Qualifications: Education & Experience" and "Skills & Competencies:" plus "Key Success Metrics". Could map Requirements to Education & Experience, Qualifications to Skills & Competencies? But they also have Skills heading. Let's think: The typical job posting sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map: - About the role: Position Overview + About Northern Trust. - Responsibilities: Key Responsibilities. - Requirements: Education & Experience (Bachelor's degree, 7+ years, etc.) - Qualifications: maybe Key Success Metrics? Not exactly. Or maybe Qualifications could be "Key Success Metrics"? That seems odd. Better to treat Qualifications as Skills & Competencies? But we already have Skills heading. Hmm. We could omit Requirements and Qualifications if content thin? But we have substantive content for both education/experience and skills. We could use Requirements for education/experience, Qualifications for skills & competencies, and Skills maybe for something else? But we have only three headings left: Skills, Benefits, Pay. We have skills content, benefits content, pay content. So we can map: - Requirements: Education & Experience. - Qualifications: Skills & Competencies. - Skills: maybe Key Success Metrics? But that's not skills. Could we omit Skills heading and instead put Key Success Metrics under Skills? Not ideal but maybe acceptable. However the instruction says we should include a section ONLY when posting has real, specific content for it. It does not require us to use all headings. So we can choose to omit Skills if we don't have specific content that matches "Skills". But we do have skills content; we could put it under Skills heading. Then we need another heading for Key Success Metrics; maybe we can put that under Qualifications? But Qualifications already used for skills. Hmm. Alternative: Use Requirements for education/experience, Qualifications for key success metrics, Skills for skills & competencies. That seems plausible: Qualifications often refer to metrics of success? Not typical but could be. However the heading list includes Qualifications as a possible heading; we can put key success metrics there. Skills heading for skills & competencies. Benefits heading for benefits. Pay heading for salary. That leaves us with: - About the role - Responsibilities - Requirements (Education & Experience) - Qualifications (Key Success Metrics) - Skills (Skills & Competencies) - Benefits - Pay We omit Schedule. Now we need to ensure we don't include filler like "commensurate with experience". Not present. We need to output only HTML fragment, no markdown. We'll need to convert lists to

• . For prose, use

  . We must preserve all substantive info: include details about Northern Trust, Position Overview, each responsibility bullet, each qualification bullet, each skill bullet, each success metric bullet, benefits description, salary range. We must remove boilerplate: the AI insights lines, repeated lines, Work Authorization, Working with Us, Reasonable Accommodation (these are not in allowed headings; but they are substantive? They might be considered boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Work Authorization, Working with Us, Reasonable Accommodation are not exactly those categories but could be considered extra info not requested. However we must preserve ALL substantive information; but the instruction says to output only sections with those headings. If we omit those sections, we would be dropping substantive info (work authorization, working with us, accommodation). However those are not among the allowed headings; maybe we should incorporate them into existing sections if relevant? For example, Work Authorization could be placed under Requirements? But it's not a requirement; it's a eligibility. Could be placed under Requirements as a note. Working with Us could go under About the role? Reasonable Accommodation could go under Benefits? Not ideal. But the instruction says: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." It does not say to remove work authorization etc. It says preserve ALL substantive information. So we need to include that info somewhere. Since we cannot add extra headings beyond the allowed list, we must embed them within existing sections. For example, we could add a paragraph under About the role about working culture, under Benefits about accommodation, under Requirements about work authorization. Let's see. We have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We can place: - About the role: include About Northern Trust description, Position Overview, and also "Working with Us" description (flexible culture, etc.) and maybe "Philanthropy" etc. - Requirements: include Education & Experience, plus Work Authorization note. - Benefits: include benefits description, plus Reasonable Accommodation note. - Pay: include Salary Range. - Qualifications: Key Success Metrics. - Skills: Skills & Competencies. - Responsibilities: Key Responsibilities. We must not repeat job title as heading. Now we need to ensure we don't include duplicated lines. The posting has duplicate lines: "The insights provided are generated by AI and may contain inaccuracies. Please independently verify any critical information before relying on it." appears twice at start. We'll remove those. Also duplicate "Proficiency in infrastructure-as-code (Github, Copilot, Terraform, yaml, Azure Devops, devSecops, CloudFormation, Pulumi)." appears twice under Skills & Competencies. We'll keep only one. Now let's extract content. About Northern Trust paragraph: "As a global leader in innovative wealth management, asset servicing, asset management and banking services, Northern Trust (Nasdaq: NTRS) is proud to guide the world's most successful individuals, families, corporations and institutions. Since 1889, we have aligned our efforts with our three guiding Principles That Endure: Service, Expertise, and Integrity. Together, they reflect the three cornerstones of business conduct which we strive to instill in our employees, whom we call partners, and to provide to our clients and the communities we serve worldwide. With more than 135 years of financial experience and over 24,000 partners, we serve the world's most sophisticated clients using leading technology and exceptional service." Position Overview: "The Cloud Data Platform Engineer is responsible for designing, implementing, operating, and evolving a scalable, secure, reliable and high-performance cloud-based data platform that enables data warehousing, analytics, artificial intelligence capabilities, and business-critical data platform services built on a modern Lakehouse architecture. This role partners with architects, product owners, and application teams to deliver modern data platform capabilities that accelerate innovation while ensuring operational excellence, governance, security, and cost efficiency. The engineer drives automation, platform standardization, and continuous improvement to provide reliable and self-service data services across the organization." Working with Us: "As a Northern Trust partner, you will be part of a flexible and collaborative work culture, which has a strong history of financial strength and stability. Movement within the organization is encouraged, senior leaders are accessible, and you can take pride in working for a company committed to an inclusive workplace and assisting the communities we serve. Philanthropy is deeply rooted in Northern Trust's history and is an essential element of our culture. Employees around the world give their time and talent to work for the greater good of their communities." Reasonable Accommodation: "Northern Trust is committed to working with and providing adjustments to individuals with health conditions and disabilities. If you need a reasonable accommodation for any part of the employment process, please email our HR Service Center at MyHRHelp@ntrs.com , or alternatively you can discuss your individual requirements with the recruiter you are working with." Work Authorization: "Applicants must be authorized to work in the U.S. without the need for employment-based visa sponsorship now or in the future. Northern Trust will not sponsor applicants for U.S. work visa status for this opportunity (no sponsorship is available for H-1B, L-1, TN, O-1, E-3, H-1B1, F-1, J-1, OPT, CPT or any other employment-based visa)." Now Responsibilities bullet list: Let's extract each bullet. From "Key Responsibilities" section: - Platform Engineering & Development - Design, implement, operate, and continuously improve cloud-based data platform services and infrastructure supporting enterprise data, analytics, and AI workloads on technologies including Databricks, Snowflake, Azure and AWS. - Support self-service data platform capabilities by developing standardized onboarding, provisioning, and operational processes for platform consumers. - Engineer reusable platform services, templates, and automation patterns that accelerate developer productivity and platform adoption. - Integrate cloud data services with enterprise applications, APIs, and third-party technologies. - Cloud Infrastructure and Automation - Build and maintain scalable Lakehouse architecture capabilities that support structured, semi-structured, and unstructured data at enterprise scale. - Implement CI/CD, Infrastructure as Code (IaC), and configuration management practices using enterprise-standard automation and deployment tools including Terraform and automated provisioning. - Develop and maintain reusable Infrastructure as Code modules, deployment templates, and platform blueprints to ensure standardization and operational consistency. - Develop platform services, automation, and documentation that enable self-service onboarding, provisioning, governance, and operational management. - Design and maintain GitHub-based CI/CD pipelines to automate platform provisioning, application deployment, testing, and operational workflows. - Build reusable frameworks and automation for data workflows, monitoring, and scaling. - Develop and optimize frameworks that enable data ingestion, transformation, orchestration, processing, and AI-powered workloads across the platform ensuring a reliable and efficient data lifecycle. - Data Platform Governance, Security, Reliability, Optimization - Continuously optimize Cloud Data platform performance, cost, and scalability, including providing tools to application teams to support them in this process. - Implement Resiliency solutions including disaster recovery, backup, and failover strategies that meet enterprise standards and take full advantage of automation. - Establish observability, monitoring, alerting, and operational tool