Data Engineer - Senior - Consulting - Location OPEN

We need to output only HTML fragment, using

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We need to extract content. Let's parse the posting. Location: Anywhere in Country (maybe not needed). The posting includes: - Intro paragraphs about EY purpose etc. Could be "About the role" or maybe "About EY". The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections are present. We have: - "The opportunity" paragraph describing Products and Platforms Practice etc. Could be "About the role". Also "The opportunity" maybe as about the role. - "Your Key Responsibilities" list: bullet points. - "Skills And Attributes For Success": list of attributes. - "To qualify for the role, you must have:" list of qualifications. - "Ideally, you’ll also have:" list of preferred qualifications. - "What We Look For": paragraph about adaptable etc. - "What We Offer You At EY": paragraph about benefits, plus salary range details, plus Total Rewards package includes medical and dental coverage, pension and 401(k) plans, and a wide range of paid time off options. Thus we have sections: About the role (maybe combine intro and opportunity), Responsibilities, Requirements (maybe qualifications), Skills (skills and attributes), Benefits (What We Offer), Pay (salary range), Schedule (not mentioned). No schedule info, so omit Schedule. We must not repeat job title as heading. No Job ID. We must remove boilerplate: cookie/navigation/legal/EEO etc. At end there is EEO statement, accommodation info, etc. Remove those. Also remove application instructions like "Are you ready to shape your future with confidence? Apply today..." etc. Also remove "To make the most of your application experience..." etc. Also remove "EY | Building a better working world" etc. Also remove equal opportunity boilerplate. We need to preserve all substantive information. Let's extract substantive content. Intro: "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 could put that under About the role (or About EY). Since we have heading About the role, we can include that. "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. 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: "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. This role offers the opportunity to work with cutting-edge technologies and stay ahead of industry trends, ensuring you gain a competitive advantage in the market. The position may require regular travel to meet with external clients." We need to format bullet list with

• . The bullet list currently is a sentence with commas; we need to split into items? The instruction: Use
  • for any list of duties/requirements/benefits. The bullet list appears as a sentence with items separated by periods? Actually it's: "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." There's no spaces after periods? It seems missing spaces. We'll treat each as separate item: 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. Also there is additional sentence after that: "This role offers the opportunity to work with cutting-edge technologies and stay ahead of industry trends, ensuring you gain a competitive advantage in the market. The position may require regular travel to meet with external clients." Those could be separate bullet items? They are not in a list but could be part of responsibilities. We'll include them as separate
  • items. Now "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 list: - Ability to work with both technical and business stakeholders. - Prior experience leveraging LLMs or other GenAI tooling. - Proven ability to work across cross-functional teams. - Proven ability to work with ambiguity or when requirements are lacking/changing. - Owns a problem from raw source through pipeline, model/analysis, and production handoff. - Checks bias, leakage, sample size, and whether a metric actually answers the question. - Writes tested, versioned, observable code — not one-off notebooks that only run on a laptop. - Strong analytical and decision-making skills. - Proficiency in cloud computing and data architecture design. - Experience in data integration and security. - Ability to manage complex problem-solving scenarios. We'll put these as
    • under Skills section. Then "To qualify for the role, you must have:" list: - A 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 These appear as a list of qualifications (maybe required). We'll put under Requirements or Qualifications? The instruction includes both Requirements and Qualifications as possible headings. We need to decide which to use. The posting has "To qualify for the role, you must have:" which sounds like Requirements. Then "Ideally, you’ll also have:" which sounds like preferred qualifications (maybe Qualifications). We could have Requirements for mandatory, and Qualifications for preferred. Or we could combine. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine required and preferred into one Qualifications section? But we have both Requirements and Qualifications headings allowed. We could have Requirements for mandatory, and Qualifications for preferred. That seems reasonable. Thus: -

      Requirements

      with list of mandatory items (Bachelor's degree, 2-4 years experience, hands-on experience with Python/R/SQL, etc.) -

      Qualifications

      with list of ideal items (passion for delivering commercial software products, etc.) Let's extract the "Ideally, you’ll also have:" list: - A passion for delivering commercial software products and platforms to market - Deeply technical and constantly in a state of learning - Able to communicate clearly and efficiently with a variety of audiences including developers, clients, customers, partners and executives - Fearless in getting “hands-on” with technology and execution - Strong understanding of modern software engineering processes - Deep understanding and interest in cloud and distributed systems architectures - Comfortable with ambiguity with a drive for clarity - Experience leading and growing technical talent (for software engineering managers) - Experience in managing change effectively. - Experience with data quality management. - Familiarity with semantic layers in data architecture. - Knowledge of emerging technologies in data analytics. We'll put those under Qualifications. Then "What We Look For" paragraph: "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." This could be part of Skills or maybe a separate section? Could be included under Skills or maybe under About the role? But we already have Skills section. Could incorporate into Skills as a paragraph. However instruction: Use

      for prose. So we can add a

      under Skills or maybe under About the role. Since it's about what we look for, maybe it's part of Skills. But we already have a list of skills; we could add a paragraph before the list. That's fine. Then "What We Offer You At EY" paragraph: "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." Then salary range 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." Thus Benefits section: we can include the paragraph about professional growth, personal fulfillment, inclusive culture, plus Total Rewards package details. The salary range goes under Pay section. Thus:

      Benefits

      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. 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.

      Pay section: salary ranges. We need to include the salary range text exactly: "The salary range for this job is:New York City, Boston, and Washington DC Metro Areas, Washington State, and Southern California offices – $128,400 to $192,500Bay Area California offices – $133,600 to $200,600All other offices locations in the US, including Sacramento – $106,900 to $176,500Individual salaries within these ranges are determined through a wide variety of factors including but not limited to education, experience, knowledge, skills and geography." We should maybe add spaces after commas for readability but must preserve all substantive information; we can format but not change meaning. We'll keep as is but maybe add line breaks for readability. It's okay. Schedule: none, omit. Now About the role section: combine the initial paragraphs and The opportunity paragraph up to before "Your Key Responsibilities". Let's extract: "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