Jobs · Minnesota

Data Engineer - Senior - Consulting - Location OPEN

EY · Minneapolis, MN · 1 mo ago
Hybrid$128k–$193k/yrFull-time
We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must not repeat job title. Remove boilerplate, navigation, EEO, etc. Must preserve all substantive info. We need to parse the posting. Key parts: Location: Anywhere in Country (maybe ignore as metadata). At EY, we’re all in to shape your future with confidence... etc. That's about the company, maybe "About the role"? Actually "About the role" could be the introductory paragraph describing role and company. We'll include that as

About the role

with paragraphs. Then "The opportunity The Products and Platforms Practice specializes..." This is also about role. Could be part of About the role. Then "Your Key Responsibilities As a Senior Data Engineer, you will play a pivotal role..." 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. So responsibilities section:

Responsibilities

with
  • items. 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: 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. That could be Skills section. Then "To qualify for the role, you must have: 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." Then a list of many topics: 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. That seems like qualifications/requirements. Could be Requirements section. Then "Ideally, you’ll also have: 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." That could be Qualifications (preferred) or additional skills. 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." That's maybe Skills or About. 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." Then salary range details. Then benefits: medical and dental coverage, pension and 401(k) plans, wide range of paid time off options. Thus we have Pay section (salary ranges). Benefits section (medical/dental, pension/401k, PTO). Schedule? Not mentioned. So we should not include Schedule. We need to avoid boilerplate like EEO, accommodation, etc. Remove those. We need to preserve all substantive info. Must not invent or summarize away detail. Must not include placeholder text like "commensurate with experience". Not present. We need to output only HTML fragment, no /, no markdown fences. We need to decide sections: About the role, Responsibilities, Skills, Requirements (or Qualifications), Benefits, Pay. We could combine Skills and Attributes with Requirements? But better separate: Skills (attributes) and Requirements (qualifications). The posting has "Skills And Attributes For Success" and then "To qualify for the role, you must have:" and "Ideally, you’ll also have:" So we can have Skills section for the attributes list, Requirements section for the must-have list, and maybe Qualifications for the ideally list? But we can combine ideally into Requirements as "Preferred qualifications". However instructions: Prefer a few substantive sections over many thin ones. So maybe we have Skills, Requirements (including must-have and ideally). But we need to preserve all info; we can include both must and ideally under Requirements with subheadings? But we cannot add extra headings beyond allowed list? The allowed headings are those listed; we cannot add custom headings like "Preferred Qualifications". But we could embed both in a single Requirements section with paragraphs distinguishing. Thus sections: About the role, Responsibilities, Skills, Requirements, Benefits, Pay. Now we need to extract content. About the role: combine introductory paragraphs: "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 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 need to ensure we don't repeat job title. It's fine. Now Responsibilities: list items: - 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. Note: The last two sentences are not bullet but we can include as list items. Now Skills: list from Skills And Attributes For Success: - 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. Now Requirements: combine must-have and ideally. Must-have: - 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. Then list of many topics (maybe these are areas of expertise). We'll treat them as items: - 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 Ideally also have: - 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 can include these as items under Requirements, maybe separate paragraphs for must-have and ideally. Now Benefits: "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." We can list: - Medical and dental coverage - Pension and 401(k) plans - Wide range of paid time off options Now Pay: salary ranges: - New York City, Boston, and Washington DC Metro Areas, Washington State, and Southern California offices – $128,400 to $192,500 - Bay Area California offices – $133,600 to $200,600 - All other offices locations in the US, including Sacramento – $106,900 to $176,500 - Individual salaries within these ranges are determined through a wide variety of factors including but not limited to education, experience, knowledge, skills and geography. We can present as list. Now we must not include Schedule. Now ensure we don't include any boilerplate like EEO, accommodation, etc. Remove those. Now produce HTML:

    About the role

    ... paragraphs ...

    Responsibilities

    • ...
    • ...

    Skills

      ...

    Requirements

      ...
    maybe we need to separate must-have and ideally but we can

Similar jobs

Senior Data Engineer

Summit Global ConsultingBoston, MA· 2 mo ago
Information Technologyapply on summitglobalconsulting.com

Senior Data Engineer

BioSpaceIndianapolis, IN· 2 mo ago
Information Technology$132k–$244k/yrapply on jobs.biospace.com

Senior Data Engineer

LineVisionBoston, MA· 3 mo ago
$145k–$160k/yrapply on recruiting.paylocity.com

Senior Data Engineer

KaiSan Jose, CA· 3 mo ago
Information Technology$125/hrapply on ats.rippling.com

Senior Data Engineer

AdobeSan Jose, CA· 4 mo ago
Information Technology$163k–$236k/yrapply on careers.adobe.com