Expert Data Scientist (AI)
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content: position summary, responsibilities (list of duties), requirements (list), other (preferred qualifications), pay range, benefits mention, schedule (hybrid role). Also mention not eligible for visa sponsorship (metadata). We need to preserve all substantive info, no boilerplate. We need to decide sections: About the role (position summary). Responsibilities (list of duties). Requirements (mandatory). Qualifications (maybe "Other" preferred qualifications). Skills (maybe mention Python etc). Benefits (mention 401k, healthcare, total rewards). Pay (range). Schedule (hybrid). We must not include sections with filler like "not specified". We have actual content for each. We must not repeat job title as heading. No Job ID/requisition as heading; we can fold into short p or drop. Probably drop. We must remove cookie/navigation/legal/EEO etc. So remove EEO paragraphs, accommodations, privacy notice, etc. Also remove "This position is not eligible for Visa Sponsorship." maybe keep as metadata? It's substantive but not a heading; we can include in a p under About the role or separate short p. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So visa sponsorship is minor metadata; we can include in a p. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all bullet points from responsibilities, requirements, other preferred qualifications, skills, benefits, pay, schedule. We must not include duplicated lines. Ensure we don't repeat. Let's extract content. Position Summary paragraph: "Join Nestlé IT & Digital as an Expert AI Data Scientist supporting Nestlé USA (NUSA). You'll sit at the seam between business and technology, framing ambiguous business problems and then owning the AI solution end-to-end, from problem definition through adoption. This is a hybrid role, equal parts product manager and technical engineer. You won't just build models; you'll direct AI agents, build the verification and workflow scaffolding that lets a product team ship reliably, and leave behind reusable assets that make the next project easier. Success is measured by durable impact and adoption, and as agents and the surrounding tooling keep reinventing themselves, you'll help shape how NUSA scales AI responsibly." That's about the role. Responsibilities (list): bullet points after "Serve as a thought leader..." etc. Let's list: - Serve as a thought leader on emerging AI, GenAI, and agentic technologies, translating breakthrough capabilities into scalable applications aligned with Nestlé's business priorities and enterprise value - Partner with stakeholders to translate ambiguous business needs into clear, precise specifications, surfacing data requirements, tradeoffs, and failure modes, and act as an internal consultant who scopes problems, defines success criteria, and drives alignment across the lifecycle - Own AI applications end-to-end, from use-case concept and experimental design through industrialization, deployment, and adoption, staying accountable across the full lifecycle rather than a single phase - Orchestrate AI agents across parallel streams of work, turning repeated tasks into reusable workflows the broader team can leverage, and incorporate agents into new and existing solutions as the technology landscape evolves - Design evaluation frameworks, conformance checks, and monitoring that validate AI output against defined specifications before rollout, including detection of silent errors, and sustain solutions in production through agent-assisted diagnosis of data-quality and pipeline issues - Strengthen the team's collective capability by documenting decisions, learnings, and incidents in shared resources, and coach business users and teammates to elevate performance across projects - Partner across global and regional IT & Digital teams to co-create and scale AI solutions, navigating platform roadmaps and enterprise processes to secure approval for needed features and capabilities - Build solutions with security and resilience in mind, protecting sensitive data and safeguarding the critical business processes they touch, and anticipating failure and misuse so AI systems remain safe, trustworthy, and reliable in production That's responsibilities. Requirements (mandatory): list: - Bachelor's degree in Computer Science, Engineering, Mathematics, Statistics, Data Science, or a related field - 7+ years of experience partnering with cross-functional stakeholders to translate business needs into technical solutions and drive adoption - 5+ years with a demonstrated track record of building and shipping AI/ML solutions that real users adopted - 3+ years of experience deploying and scaling solutions at enterprise scale, including MLOps and cloud platforms such as Databricks and Snowflake - 3+ years of experience delivering production solutions with emerging technologies, advanced data and automation capabilities, or machine learning, with a recent focus on AI, GenAI, LLMs, agentic workflows Other (preferred qualifications): list: - Master's or PhD in Computer Science, Engineering, Mathematics, Statistics, Data Science, or a related discipline is preferred - Experience directing AI agents or agentic workflows to do substantive work, not just single-prompt usage, is preferred - Experience driving AI concepts from idea to enterprise-scale adoption, ideally in consumer products, CPG, Supply Chain, or Commercial environments is preferred - Strong hands-on engineering fluency in Python (or similar) for building, deploying, and integrating AI solutions, including modern LLM and agent patterns such as prompt interaction, tool/function calling, retrieval, and handling non-determinism, is preferred - Don't meet all the qualifications listed under "Other"? These are preferred, but not required. (This is a note; we can keep as a p maybe.) Skills: maybe we can extract from "Strong hands-on engineering fluency in Python..." but that's already in Other. Could create Skills section for Python, LLM, agent patterns, etc. But we might combine with Other as Qualifications. The instruction: Use headings for sections like Skills if there is real specific content. We have specific skills: Python, LLM, agent patterns, prompt interaction, tool/function calling, retrieval, handling non-determinism. Also maybe experience with Databricks, Snowflake, MLOps, cloud platforms. Those are in requirements. Could create Skills section for technical skills: Python, LLM, agent patterns, MLOps, Databricks, Snowflake, etc. But we must not invent or summarize away detail; we can list them as they appear. Benefits: "Nestlé offers performance-based incentives and a competitive total rewards package, which includes a 401k with company match, healthcare coverage and a broad range of other benefits. Incentives and/or benefit packages may vary depending on the position." Also maybe mention "Learn more at https://nestlejobs.com/nestle-in-the-us." That's a link; we can keep as p. Pay: "The approximate pay range for this position is $140,000 to $196,000 per year. Please note that the pay range provided is a good faith estimate for the position at the time of posting. Final compensation may vary based on factors including but not limited to knowledge, skills and abilities as well as geographic location." Schedule: "This is a hybrid role, equal parts product manager and technical engineer." Already mentioned in summary; but schedule is hybrid. Could create Schedule section with "Hybrid role (remote and on-site)". We have that. We must not repeat content unnecessarily but preserve all. Might be okay to have some overlap but better to avoid duplication. We can keep schedule mention only in Schedule section, not repeat in About the role. However the summary includes hybrid role; we could keep it there and not have separate Schedule section, but we need to include Schedule section only if posting has real specific content for it. It does: hybrid role. So we can include Schedule section with that detail, and maybe not repeat in About the role (but we could keep brief summary without hybrid mention). However we must preserve ALL substantive information; if we remove hybrid mention from summary, we lose that detail. So we need to keep it somewhere. Could keep in About the role a brief summary without hybrid, and then Schedule section with hybrid detail. But the summary currently includes hybrid; we could edit to remove hybrid phrase but that would be summarizing away detail (removing). The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we cannot remove the hybrid mention from the summary if it's substantive. However we could keep it in both places; that's duplication but not summarizing away. Duplication is allowed? The instruction says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." It says remove duplicated lines. So we should avoid duplicated lines. So we need to avoid repeating the same sentence. So we need to decide where to place hybrid mention only once. Could place it in Schedule section and not in About the role. But then About the role would lose that detail, which is substantive. However we could rephrase About the role to not include hybrid but still convey the role description; but that would be summarizing away detail (removing the hybrid aspect). The hybrid aspect is substantive; removing it would be losing detail. So we need to keep hybrid mention somewhere. If we put it only in Schedule section, we still have the detail present (in Schedule). The About the role section would then lack hybrid mention, but the role description still includes other substantive details. Is the hybrid aspect considered part of the role description? It is a schedule attribute. Could be considered separate. The instruction: "Prefer a few substantive sections over many thin ones." So we could have About the role (position summary without hybrid), Responsibilities, Requirements, Qualifications (Other), Skills, Benefits, Pay, Schedule. That seems okay. The About the role would not mention hybrid; but the hybrid detail is captured in Schedule section. So we are not losing the detail; it's just moved. That's acceptable because we are not summarizing away; we are relocating. The instruction about duplicated lines: we avoid duplication. So we will not repeat hybrid in About the role. Thus we need to rewrite About the role paragraph without the hybrid phrase. Let's extract the summary without hybrid: "Join Nestlé IT & Digital as an Expert AI Data Scientist supporting Nestlé USA (NUSA). You'll sit at the seam between business and technology, framing ambiguous business problems and then owning the AI solution end-to-end, from problem definition through adoption. You won't just build models; you'll direct AI agents, build the verification and workflow scaffolding that lets a product team ship reliably, and leave behind reusable assets that make the next project easier. Success is measured by durable impact and adoption, and as agents and the surrounding tooling keep reinventing themselves, you'll help shape how NUSA scales AI responsibly." That retains all other details. Now schedule section: "This is a hybrid role, equal parts product manager and technical engineer." Now responsibilities list as above. Requirements list as above. Qualifications (Other) list as above. Skills: we could list specific technical skills: Python, LLM, agent patterns, prompt interaction, tool/function calling, retrieval, handling non-determinism, MLOps, Databricks, Snowflake, cloud platforms. But note that some of these are already in requirements (Databricks, Snowflake, MLOps). To avoid duplication, we could create Skills section focusing on hands-on engineering fluency: Python, LLM, agent patterns, prompt interaction, tool/function calling, retrieval, handling non-determinism. The Databricks/Snowflake/MLOps are more experience requirements; could stay in Requirements. We'll keep Skills as mentioned. Benefits: list: performance-based incentives, competitive total rewards package including 401k with company match, healthcare coverage, broad range of other benefits. Also link to learn more. Pay: range and note. Now we need to output HTML fragment only, no markdown fences. We'll structure:
About the role
...
Responsibilities
- ... ...
Requirements
- ...