Senior Big Data Engineer - Chicago Hybrid

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 if posting has real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO, legal, application instructions. We need to preserve all substantive info. We need to parse the job description. Content: - Job title: Senior Associate Data Engineering - Chicago Hybrid (but we don't repeat as heading) - About the role: The description includes "As a Senior Associate Data Engineer, you will be responsible for designing, developing, and maintaining scalable Big Data solutions..." plus "Your Impact:" bullet points. We can treat "About the role" as a section with prose summarizing responsibilities? Actually responsibilities are listed later. The posting includes "Your Impact:" with bullet points describing responsibilities. Also there is a list of responsibilities after "Your Impact:"? Let's parse: Paragraphs: "As a Senior Associate Data Engineer, you will be responsible for designing, developing, and maintaining scalable Big Data solutions. You will work with large datasets, real-time processing frameworks, and cloud-based data platforms to enable data-driven decision-making for our clients." Then "Your Impact:" then bullet points: - Combine your technical expertise and problem-solving passion to work closely with clients, turning complex ideas into end-to-end data solutions that transform our clients’ business. - Translate client requirements into system design and develop solutions that deliver measurable business value. - Lead, design, develop and deliver large-scale data systems, data processing, data transformation, and data platform modernization initiatives. - Build and optimize batch and streaming data pipelines across modern cloud data platforms and distributed processing frameworks. - Support AI-enabled engineering use cases by designing high-quality data foundations, retrieval patterns, context engineering approaches, and scalable data services that power agentic and machine learning solutions. - Automate data platform operations and manage post-production systems, observability, quality, reliability, and operational processes, including telemetry pipelines that capture prompt, response, trace, latency, token, and cost data for AI-enabled services in a query able form. - Conduct technical feasibility assessments and provide project estimates for the design and development of solutions. - Mentor, support, and grow junior team members while contributing hands-on to delivery. Then "Qualifications" heading. Under Qualifications: "Your Skills & Experience:" then bullet list of skills/experience. Then "AI Engineering & Modern Data Platform Experience:" bullet list. Then "Set Yourself Apart With:" bullet list. Then "Additional Information" includes Salary Range, Benefits Of Working Here, etc. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for About the role (intro paragraph). Responsibilities (the "Your Impact:" bullet list). Requirements? Could be the qualifications? But we have Qualifications and Skills sections separate. The instruction says use headings for those specific names. We need to be used if content exists. We have Qualifications content (Your Skills & Experience, AI Engineering & Modern Data Platform Experience, Set Yourself Apart With). Could split into Qualifications and Skills? But we have both headings available. We need to decide how to map. The posting includes "Qualifications" heading already. Under that, there is "Your Skills & Experience:" then bullet list. Then separate "AI Engineering & Modern Data Platform Experience:" and "Set Yourself Apart With:" which could be considered part of Qualifications or Skills. Since we have both Qualifications and Skills headings, we could put the skill/experience bullet list under Skills, and the qualifications (like experience, education?) but there is no explicit education requirement. The "Your Skills & Experience:" is basically skills. The AI Engineering & Modern Data Platform Experience and Set Yourself Apart With are also skills/experience. So maybe we just have one Skills section containing all those bullet points. Qualifications could be empty? But we must not emit a heading with filler/placeholder. So we should only include Qualifications if there is real specific content. The posting does have a "Qualifications" heading but the content under it is skill/experience. If we treat that as Qualifications, we could put that content there and not have a separate Skills section. However we also have "Skills" heading available; we could split but risk duplication. Better to follow the posting: Use "Qualifications" as heading for the skill/experience content. Then we may not need a separate Skills section unless there is distinct skills content separate from qualifications. The posting also has "Your Skills & Experience:" which is essentially qualifications. So we can put that under Qualifications. Thus we will have sections: - About the role (intro paragraph) - Responsibilities (Your Impact bullet list) - Qualifications (Your Skills & Experience bullet list, AI Engineering & Modern Data Platform Experience bullet list, Set Yourself Apart With bullet list) - Benefits (Benefits Of Working Here bullet list) - Pay (Salary Range) - Schedule? Not mentioned; there is "Chicago Hybrid" indicating hybrid work schedule but not explicit schedule details. The instruction: never create Schedule section unless posting actually states them. It mentions hybrid but not schedule details like "full-time", "flexible hours". Might be considered schedule? It says "Chicago Hybrid". That indicates hybrid work arrangement. Could be considered schedule? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state hybrid location but not schedule like "full-time" or "part-time". I'd argue schedule not explicitly stated, so omit Schedule section. Thus we output HTML with

About the role

...

etc. We need to preserve all substantive information, not invent or summarize away detail. So we need to keep the bullet points exactly as given (maybe rephrase? Must preserve all info, not summarizing away detail. We can keep the bullet points as

• ...
. Must not omit any bullet. We need to include the intro paragraph about responsibilities as prose under About the role. We need to include the bullet list under Responsibilities exactly as given. We need to include bullet list under Qualifications: combine three bullet groups? Could keep them as separate
under same heading? Probably we can have one
containing all bullet points from those three sections. Must preserve all bullet points. We need to include Benefits bullet list. We need to include Pay: Salary Range: $136,000 - $160,000 annual salary plus note about range may vary. Must preserve that. We must not include boilerplate like EEO, legal, application instructions, company description? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also "Company Description" maybe considered boilerplate? It's not explicitly listed but could be considered part of job description but not required? The instruction says preserve ALL substantive information; does company description count as substantive? It's about the company, not the role. Might be considered boilerplate? It's not EEO/legal but still generic. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." It does not say to remove company description. However earlier: "Preserve ALL substantive information; do NOT invent or summarize away detail." The company description is substantive about the employer, but maybe not needed for the job posting? The instruction didn't explicitly say to remove it. However typical job posting reformatting often excludes company description as it's not about the role. But the instruction says preserve ALL substantive information; that could be interpreted to include company description. However they also said "Prefer a few substantive sections over many thin ones." Including company description would add another section maybe "About the company". But we don't have a heading for that. Could embed as a paragraph under About the role? Might be okay. But the instruction also says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So only those headings allowed. So we cannot add a custom heading like About the company. So we could incorporate company description into About the role paragraph as prose. That would preserve it. Thus About the role section will contain the initial paragraph about role responsibilities plus the company description paragraph(s). We need to ensure we don't miss any substantive info. Let's extract company description paragraph: "Publicis Sapient is a digital transformation partner helping established organizations get to their future, digitally enabled state, both in the way they work and the way they serve their customers. We help unlock value through a start-up mindset and modern methods, fusing strategy, consulting, and customer experience with agile engineering and problem-solving creativity. United by our core values and our purpose of helping people thrive in the brave pursuit of next, our 20,000+ people in 53 offices around the world combine experience across technology, data sciences, consulting, and customer obsession to accelerate our clients’ businesses through designing the products and services their customers truly value." We'll include that as a paragraph after the role description. Now we need to ensure we don't include duplicated lines. There may be duplicated bullet about "Support AI-enabled engineering use cases by designing high-quality data foundations..." appears both in Your Impact and also later in AI Engineering & Modern Data Platform Experience? Actually the bullet "Support AI-enabled engineering use cases by designing high-quality data foundations, retrieval patterns, context engineering approaches, and scalable data services that power agentic and machine learning solutions." appears in Your Impact list and also appears again in AI Engineering & Modern Data Platform Experience bullet list (first bullet). That is duplicated content. We need to remove duplicated lines. So we should include each unique bullet only once. Let's list all bullets from Your Impact: 1. Combine your technical expertise and problem-solving passion to work closely with clients, turning complex ideas into end-to-end data solutions that transform our clients’ business. 2. Translate client requirements into system design and develop solutions that deliver measurable business value. 3. Lead, design, develop and deliver large-scale data systems, data processing, data transformation, and data platform modernization initiatives. 4. Build and optimize batch and streaming data pipelines across modern cloud data platforms and distributed processing frameworks. 5. Support AI-enabled engineering use cases by designing high-quality data foundations, retrieval patterns, context engineering approaches, and scalable data services that power agentic and machine learning solutions. 6. Automate data platform operations and manage post-production systems, observability, quality, reliability, and operational processes, including telemetry pipelines that capture prompt, response, trace, latency, token, and cost data for AI-enabled services in a query able form. 7. Conduct technical feasibility assessments and provide project estimates for the design and development of solutions. 8. Mentor, support, and grow junior team members while contributing hands-on to delivery. Now AI Engineering & Modern Data Platform Experience bullets: - Exposure to AI engineering patterns, including context engineering, retrieval-augmented generation support patterns, agent architectures, and production data services that support AI-enabled experiences. - Experience building and maintaining the pipelines behind retrieval systems, including document parsing, chunking, metadata extraction, embedding generation, and incremental reindexing, alongside the vector databases, graph databases, semantic search, and knowledge retrieval structures they feed. - Exposure to agentic platforms or cloud AI services such as Vertex AI, Azure AI services, AWS AI services, or comparable platforms; specific platform experience is less important than understanding how AI engineering differs from traditional data engineering. - Practical experience deploying agents, integrating agent frameworks, or supporting agentic workflows in production or near-production environments is a plus. - Experience building evaluation data infrastructure for AI systems, including ground-truth and golden datasets, offline evaluation pipelines, and the data scaffolding behind LLM-as-judge and regression testing. - Experience modeling and persisting agent state, including session context, conversation history, and memory stores, treating them as a durable storage and data modeling problem rather than an application detail. - Support AI-enabled engineering use cases by designing high-quality data foundations, retrieval patterns, context engineering approaches, and scalable data services that power agentic and machine learning solutions, applying the same lineage, provenance, and data contract rigor to context and retrieval sources that you would to a production warehouse. - Experience with agentic