AI/ML Battery Manufacturing Technologist

We need to output HTML fragment with sections: headings

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Preserve all substantive info. Include a section only when posting has real specific content for it. Avoid filler like "commensurate with experience". Pay/Schedule/Benefits only if posting actually states them. We need to parse the job description. Content: - Intro paragraph: "We made history and now we work to transform the future – for our customers, our communities and our families. You'll see your work on the road every day, helping people move freely and pursue their dreams. At Ford, you can build more than vehicles. Come build what matters. Do you believe data tells the real story? We do! Redefining mobility requires quality data, metrics and analytics, as well as insightful interpreters and analysts. That's where Global Data Insight & Analytics makes an impact. We advise leadership on business conditions, customer needs and the competitive landscape. With our support, key decision makers can act in meaningful, positive ways. Join us and use your data expertise and analytical skills to drive evidence-based, timely decision making., Ford Energy is a newly formed, wholly-owned subsidiary of Ford Motor Company dedicated to accelerating U.S. energy independence. Leveraging Ford’s century of manufacturing excellence and world-class battery energy storage systems (BESS) technology, Ford Energy designs, manufactures, and services grid-scale and commercial DC battery energy storage systems (BESS). Ford Energy is uniquely positioned to capture the growing demand for reliable, US-built energy storage systems. We are not just building batteries; we are building the infrastructure for the next generation of the American grid. Why Ford Energy? At Ford Energy, you have the backing of an industrial manufacturing powerhouse with the agility of a dedicated energy startup offering industry leading technology. We offer a competitive compensation package including performance-based bonuses, Ford vehicle discounts, and the opportunity to shape the energy strategy of one of the world's most iconic brands. Learn more at https://fordenergy.com . In this position... You will stay at the frontier of AI for battery manufacturing. Work up front in process and launch, evaluate and pilot new methods, keep a living internal and external benchmark, and turn it into a pipeline of future ideas the plants can adopt." Then sections: Responsibilities: bullet list under "What you'll do..." with items: - Own the AI roadmap for battery manufacturing: what to pilot, what to scale, what to retire, tied to yield, quality, cost, and launch speed. - Run continuous benchmarking, internal across Ford battery sites and external across cell makers, suppliers, semiconductor, and coatings, and translate it into concrete next steps. - Build proofs of concept and reference architectures for the highest-value use cases: formation and aging optimization, inline coating and defect vision, yield genealogy, and predictive maintenance. - Set the data, labeling, and model standards so work done at one plant is reusable at the next. - Act as the center of excellence for battery manufacturing AI: evaluate vendors, guide the embedded engineers, and align with IT and OT on security and scale. - Where it fits, apply generative and agentic AI (copilots and workflow agents) to engineering and plant workflows. Qualifications: bullet list under "You'll have...": - Bachelor's in Engineering (Electrical or Mechanical preferred) or Bachelor's in Science (Computer Science) - 10+ years of experience, with several years in applied AI or ML on real production or process systems. - Depth in manufacturing or process data: multivariate and time-series, SPC, design of experiments, and inline vision. - Fluent enough in the physics to earn credibility with process and controls engineers, and fluent enough in ML to lead the technical direction. - Even better, you may have... - Master's in AI, ML, data science, or computer science preferred. - Battery cell, semiconductor fab, or roll-to-roll coating background; cloud ML (GCP or Azure); familiarity with agentic frameworks (LangGraph, ADK, AutoGen, MCP) for workflow automation. - You may not check every box, or your experience may look a little different from what we've outlined, but if you think you can bring value to Ford Motor Company, we encourage you to apply! Then benefits: list after "As an established global company, we offer the benefit of choice. You can choose what your Ford future will look like: ... No matter what you choose, we offer a work life that works for you, including:" List: - Immediate medical, dental, vision and prescription drug coverage - Flexible family care days, paid parental leave, new parent ramp-up programs, subsidized back-up child care and more - Family building benefits including adoption and surrogacy expense reimbursement, fertility treatments, and more - Vehicle discount program for employees and family members and management leases - Tuition assistance - Established and active employee resource groups - Paid time off for individual and team community service - A generous schedule of paid holidays, including the week between Christmas and New Year’s Day - Paid time off and the option to purchase additional vacation time. Pay: "This position is leadership level 6 and ranges from $132,800-$250,800. Final determination of salary grade will be based on candidate's skills and experience, and base salary will be set within the applicable range according to job scope, responsibility and competitive market value." Schedule: "This position is hybrid with a requirement to be onsite four or more days per week." Also there is mention of Visa sponsorship not available, legal authorization, EEO, accommodation phone number, etc. Those are boilerplate to remove. Also there is "About Us", "About The Team" sections at end; those are generic and could be considered boilerplate? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About Us" and "About The Team" might be considered generic but not necessarily boilerplate; they are substantive about company. However they might be considered filler? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep them if they are substantive. However they are generic but still about the company. The instruction: "Prefer a few substantive sections over many thin ones." Might combine them into an "About the company" section? But we have headings limited to specific list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. There's no "About the company" heading allowed. So we cannot create a heading not in list. So we must either omit those paragraphs or incorporate them into existing allowed sections if relevant. The "About Us" and "About The Team" are not about the role, responsibilities, qualifications, etc. They could be considered "About the role"? Not really. The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we can use those headings; we shouldn't create other headings. So we should not include "About Us" or "About The Team" as separate headings. We could possibly include that content under "About the role" as a description? But "About the role" is supposed to describe the role, not the company. However we could incorporate some of that descriptive content into the role description paragraph at top (which already includes some company info). The "About Us" and "About The Team" are generic and could be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It does not explicitly say to remove generic "About Us" sections. But to preserve ALL substantive information. However we cannot create a heading for it; we could embed it as a paragraph under maybe "About the role" or just as a paragraph without heading? The instruction says output ONLY the HTML fragment, using headings for sections. It doesn't forbid having paragraphs outside of sections? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

  • for any list of duties/requirements/benefits, and

    for prose. It doesn't say we cannot have stray paragraphs not under a heading, but likely they expect sections with headings. Safer to include them under a heading like "About the role" if we can reinterpret. But "About the role" could include a brief description of the role and the team. The initial paragraph already covers role context. The "About Us" and "About The Team" are more about company; maybe we can omit them as they are not specific to the role and could be considered boilerplate? The instruction says preserve ALL substantive information; but if we consider them boilerplate (generic company description) maybe they are not substantive for the job posting. However they are not explicitly listed as boilerplate types to remove. Yet they are generic and could be considered filler. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine them into a brief paragraph under "About the role" or just omit. I'd lean to omit them to avoid extra sections not in allowed list. The initial paragraph already mentions Ford, Ford Energy, etc. That may be enough. Thus sections we will include: - About the role (maybe we can use that heading for the introductory descriptive paragraphs). We'll put the introductory paragraphs (the first big paragraph) under

    About the role

    as prose

    . - Responsibilities:

    Responsibilities

    with
    • items. - Qualifications:

      Qualifications

      with
      • items (including the "Even better, you may have..." as sub-items? Could be nested but we can just list them as separate
      • .) - Benefits:

        Benefits

        with
        • items. - Pay:

          Pay

          with

          containing salary range and note. - Schedule:

          Schedule

          with

          about hybrid requirement. We should not include Requirements or Skills sections unless there is specific content. There's no separate "Requirements" beyond qualifications; we could treat Qualifications as requirements. The instruction says use headings like Requirements, Qualifications, Skills. We have Qualifications; we could omit Requirements and Skills if no specific content. The posting does not have a separate "Skills" list; qualifications cover skills. So we omit Requirements and Skills. Now we need to ensure we don't include boilerplate like visa sponsorship, EEO, accommodation phone number, etc. Also remove duplicated lines. Also remove application instructions like "click here: https://fordcareers.co/LL6" (that's a link for salary and benefits). That's application instruction? It's a link for more info on salary and benefits; could be considered ancillary but maybe we keep it as part of Pay section? The instruction says remove application instructions. That link is not exactly an application instruction but a reference. Safer to omit it. Also remove "Learn more at https://fordenergy.com ." That's a link; could be considered extra but it's part of description about Ford Energy. Might be considered substantive? It's a link to learn more; maybe we can keep as part of prose but not essential. The instruction says preserve ALL substantive information; a link is not substantive info but a reference. Could be omitted. However the description about Ford Energy includes that link; removing it may lose some info but not essential. I'd keep the link as part of prose? The instruction says remove application instructions; not necessarily all links. But to be safe, I'd keep the link as part of