Data Engineer - Senior - Consulting - Location OPEN

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the posting. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove location line? The location line "Location: Anywhere in Country" maybe minor metadata; we can fold into short

or drop. Probably drop. We need to preserve all substantive info: description about EY, purpose, opportunity, responsibilities, skills, qualifications, etc. Also pay info: salary ranges given. Benefits: mention medical/dental coverage, pension/401(k), paid time off. Schedule? Not mentioned. So we should not create Schedule section. We need sections: maybe "About the role" (or "About the role" is typical). Could also have "Responsibilities", "Qualifications", "Skills", "Benefits", "Pay". Use

for each. We need to decide what content goes where. The posting includes: - Intro paragraph about EY purpose etc. Could be "About the role" or maybe "About EY". But we can put under "About the role". The instruction: do NOT repeat the job title as a heading (the page already shows it). So we can have heading "About the role". Provide prose. - Responsibilities: bullet list under "Your Key Responsibilities". Also earlier "Your responsibilities will include creating scalable data architecture...". So we can combine. - Skills and Attributes: list under "Skills And Attributes For Success". Also "To qualify for the role, you must have:" (qualifications). Also "Ideally, you’ll also have:" (preferred qualifications). Also "What We Look For" (maybe also qualifications). We need to separate Qualifications vs Skills? The instruction: use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can decide to put qualifications under "Qualifications" (education, experience). Skills under "Skills". Requirements maybe similar to qualifications? But we can combine. We need to avoid filler like "commensurate with experience". Not present. We need to preserve all substantive info: include details like degree required, years experience, specific tech skills, etc. We need to output only HTML fragment, no markdown fences. Let's craft:

About the role

At EY, we’re all in to shape your future with confidence. We’ll help you succeed in a globally connected powerhouse of diverse teams and take your career wherever you want it to go. Join EY and help to build a better working world. At EY, our purpose is to shape the future. The insights and quality services we provide help build trust and confidence in the capital markets and economies all over the world. We develop outstanding leaders who are teamed to deliver our promises to all our stakeholders. In so doing, we play a critical role in building a better working world for our people, for our clients and for our communities. The Products and Platforms Practice specializes in mission-critical, intelligent platforms for the world’s most ambitious organizations. Using our product-driven, AI-centric approach, we empower organizations to build for the intelligent digital future. Our elite team of product leaders, data scientists, designers, and software engineers enable our clients to solve their most complex product challenges and positively impact people and the world. Engineers are problem solvers. While most have deep expertise in specific areas of the technology stack (front end, back end, data, security etc.), all are comfortable swimming across lanes. This is really important in delivering the product and platform outcomes that our customers expect. In this role, you will design and build AI and analytics solutions that deliver significant business value. You will collaborate with other data and analytics professionals, management, and stakeholders to ensure that technical requirements align with business needs. Your responsibilities will include creating scalable data architecture and modeling solutions that support the entire data asset lifecycle.

Responsibilities

• Designing, building, and operating scalable on-premises or cloud data architecture.
• Analyzing business requirements and translating them into technical specifications.
• Optimizing data flows for target data platform designs.

Qualifications

• Bachelor’s degree required (4-year degree) in Data Science, Machine Learning, Computer Science, Statistics, Mathematics, Engineering, Applied Math, Analytics, or related preferred.
• Typically, no less than 2 - 4 years relevant experience.
• Hands-on experience developing scalable data solutions using Python, R, and SQL, with expertise in data engineering, data pipelines, streaming architectures, and big data ecosystems.
• Cloud Computing Architecture
• Data Architecture Design and Modelling
• Data Integration
• Data Security
• Ontology Design
• Software Engineering
• Data Quality
• Database Management
• Semantic Layer
• Building and Managing Relationships
• Client Trust and Value
• Communicating With Impact
• Hybrid Collaboration
• Complex Problem-Solving
• Critical Thinking

But note many of those items are from a long list after "To qualify for the role, you must have:" includes a bulleted list of many items. Some are single words like "Cloud Computing Architecture". We need to preserve them as list items. We also have "Ideally, you’ll also have:" list of preferred qualifications. Could be placed under "Qualifications" as well, maybe separate "Preferred Qualifications". But we only have headings for Qualifications; we could include both required and preferred under same heading, but we need to preserve all info. Could separate into "Qualifications" (required) and "Preferred Qualifications" (maybe under Skills?). However instruction: Use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It didn't forbid adding other headings like "Preferred Qualifications"? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings only; but we could also add other headings if needed? It says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should limit to those examples; but not strictly forbidden to add others? Safer to stick to those. So we need to map content to those headings. We have "Skills And Attributes For Success" which maps to Skills. Also "What We Look For" maybe also Skills or Qualifications. We'll put under Skills. Thus: - About the role: intro paragraphs. - Responsibilities: bullet list. - Qualifications: required qualifications (degree, years experience, hands-on experience, plus the list of specific areas like Cloud Computing Architecture etc.) Might be too many but okay. - Skills: skills and attributes list (ability to work with stakeholders, LLMs, cross-functional, ambiguity, owns problem, checks bias, writes tested code, strong analytical, proficiency in cloud computing, data integration/security, manage complex problem-solving). Also maybe "What We Look For" (adaptable, collaborative, driven). Also "Ideally, you’ll also have:" list (passion for delivering commercial software products, deeply technical, communicate clearly, fearless hands-on, understanding modern software engineering processes, deep understanding of cloud/distributed systems, comfortable with ambiguity, experience leading/growing technical talent, managing change, data quality management, familiarity with semantic layers, knowledge of emerging technologies). We'll put those under Skills as well. - Benefits: medical and dental coverage, pension and 401(k) plans, wide range of paid time off options. - Pay: salary ranges with location-based details. We should not include Schedule. We need to ensure we don't include boilerplate like EEO etc. Remove those paragraphs at end. Also remove duplicated lines like "At EY, we’re all in to shape your future with confidence." appears twice? Actually appears at start and later? We'll keep only once. We need to preserve all substantive info; we must not invent or summarize away detail. So we need to keep the exact phrasing? Not necessarily exact but preserve all info. We'll try to keep the substance. Let's extract sections precisely. First paragraph: "Location: Anywhere in Country At EY, we’re all in to shape your future with confidence. We’ll help you succeed in a globally connected powerhouse of diverse teams and take your career wherever you want it to go. Join EY and help to build a better working world. At EY, our purpose is to shape the future. The insights and quality services we provide help build trust and confidence in the capital markets and economies all over the world. We develop outstanding leaders who are teamed to deliver our promises to all our stakeholders. In so doing, we play a critical role in building a better working world for our people, for our clients and for our communities." We can combine into a paragraph. Next: "The opportunity The Products and Platforms Practice specializes in mission-critical, intelligent platforms for the world’s most ambitious organizations. Using our product-driven, AI-centric approach, we empower organizations to build for the intelligent digital future. Our elite team of product leaders, data scientists, designers, and software engineers enable our clients to solve their most complex product challenges and positively impact people and the world. Engineers are problem solvers. While most have deep expertise in specific areas of the technology stack (front end, back end, data, security etc.), all are comfortable swimming across lanes. This is really important in delivering the product and platform outcomes that our customers expect. In this role, you will design and build AI and analytics solutions that deliver significant business value. You will collaborate with other data and analytics professionals, management, and stakeholders to ensure that technical requirements align with business needs. Your responsibilities will include creating scalable data architecture and modeling solutions that support the entire data asset lifecycle." We could incorporate into About the role or separate. But we already have About the role covering EY purpose etc. Could add this as part of About the role. Then "Your Key Responsibilities As a Senior Data Engineer, you will play a pivotal role in transforming data into actionable insights. Your time will be spent on various responsibilities, including:" then bullet list. We'll output Responsibilities heading with those bullets. Then "Skills And Attributes For Success To thrive in this role, you will need a blend of technical and interpersonal skills. Your ability to communicate effectively and build relationships will be crucial. Here are some key attributes we look for:" then bullet list. Then "To qualify for the role, you must have:" then bullet list (the long list). Then "Ideally, you’ll also have:" then bullet list. Then "What We Look For We seek individuals who are not only technically proficient but also possess the qualities of top performers. You should be adaptable, collaborative, and driven by a desire to achieve excellence in every project you undertake." Then "What We Offer You At EY, we harness our collective strength to empower you to shape your future with confidence through professional growth, personal fulfillment and an inclusive culture. Learn more at ey.com/us/careers. The salary range for this job is: ..." then salary details. Then "In addition, our Total Rewards package includes medical and dental coverage, pension and 401(k) plans, and a wide range of paid time off options." Then after that there is application instructions etc which we need to remove. Thus we need to map: - About the role: combine initial EY purpose and opportunity paragraphs. - Responsibilities: bullet list from "Your Key Responsibilities". - Qualifications: the "To qualify for the role, you must have:" list (including degree, years experience, hands-on experience, and the long list of specific areas). Possibly also include "Ideally, you’ll also have:" as part of Qualifications? But that is "Ideally". Could