Agronomist

for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short

or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to parse the posting. Key content: - Position Title: Agronomist (but we don't repeat as heading) - Position Type: Regular - Full-Time - Grade: Grade 04 - Requisition ID: 43969 - Regional Agronomist Burley, Idaho (maybe location) - About The Role: paragraph. - What You'll Be Doing: list of duties (multiple bullet-like sentences) - What You'll Need To Be Successful: list of qualifications/requirements. - About The Team: paragraph. - About McCain: paragraphs (leadership principles, AI & Digital Capabilities, The McCain Experience) - but these are likely boilerplate? Might be considered generic corporate info; but they are not about the role specifics. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About McCain" sections might be considered generic but they are not EEO. However they might be considered filler? The instruction: "Prefer a few substantive sections over many thin ones." Could combine About McCain into a single paragraph? But we need to preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep the content but can we condense? We cannot summarize away detail; we must preserve all substantive information. However we can keep them as prose paragraphs (

) without making separate sections if they are not specific to role? The instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we could have sections: About the role (maybe "About The Role"), Responsibilities (What You'll Be Doing), Requirements/Qualifications (What You'll Need To Be Successful), About the Team, Benefits, Pay. Possibly also "About McCain" but that might be considered generic corporate info; but it's still substantive. However we might combine it into a single "About McCain" section if we want few sections. But we need to preserve all detail; we can put it in a

under that section. We also have Compensation Package: $65,500.00 - $87,400.00 * USD annually + Bonus eligibility. That's Pay. Benefits: described. We have no explicit Schedule info (like full-time). Position Type: Regular - Full-Time could be schedule. But we should not create Schedule section unless posting actually states them. It does state "Regular - Full-Time". That's schedule info. Could we include Schedule section? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state full-time, so we could include Schedule. However we might combine schedule into a short paragraph under About the role or elsewhere. But they said prefer few substantive sections over many thin ones. So maybe we omit Schedule section and just mention full-time in a paragraph elsewhere (like under About the role). But we need to preserve all substantive information; we can include it in a

somewhere. We must not repeat job title as heading. So no

Agronomist>. Use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which to include. We have content for About the role (the paragraph after "About The Role."). We have Responsibilities (What You'll Be Doing). We have Requirements/Qualifications (What You'll Need To Be Successful). We have About The Team. We have Benefits. We have Pay. We have maybe Skills? The "What You'll Need To Be Successful" includes skills; we could treat that as Requirements or Skills. But we should not duplicate. Perhaps we combine Requirements and Skills into one section "Requirements". Or we could have separate sections if content distinct. The list includes education, knowledge, abilities, certifications. That's both requirements and skills. We'll make one section "Requirements". Could also have "Qualifications" but similar. To avoid thin sections, we'll combine. Thus sections: About the role, Responsibilities, Requirements, About the Team, Benefits, Pay. We need to use

for each section heading. Inside each section, we need to use

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

  for prose. Thus: - About the role: prose paragraph(s). Could be multiple paragraphs: The first paragraph about role, maybe also the "About The Team" separate. - Responsibilities: list of duties from "What You'll Be Doing." Each sentence starts with a verb. We'll make each as

• . - Requirements: list from "What You'll Need To Be Successful." Each bullet as
• . - About the Team: prose paragraph(s). - Benefits: list from benefits description. The benefits paragraph includes list: health coverage (medical, dental, vision, prescription drug), retirement savings benefits, leave support including medical, family and bereavement. Well-being programs include vacation and holidays, company-supported volunteering time, and mental health resources. Coverages are aligned with applicable law and can vary... Additional benefit detail available during application process. Your well-being matters... We'll make a
  • for each benefit item? Could combine. We'll list each distinct benefit: health coverage (medical, dental, vision, prescription drug), retirement savings benefits, leave support (medical, family, bereavement), well-being programs (vacation and holidays, company-supported volunteering time, mental health resources). Could also note that coverages vary etc. We'll keep as prose maybe? But instruction: use
    • for any list of duties/requirements/benefits. So we need to make a list. - Pay: prose paragraph with compensation range and bonus eligibility. We also need to include minor metadata like Position Type, Grade, Requisition ID, Location maybe in a short

      somewhere, not as heading. Could place after About the role or at top. We'll include a

      with that info. We must not include Job ID/requisition numbers as headings; we can fold into a short

      . So we can have a

      containing: Position Type: Regular - Full-Time; Grade: Grade 04; Requisition ID: 43969; Location: Burley, Idaho. Now we need to remove boilerplate: EEO, equal opportunity, privacy, AI hiring process, etc. Also remove "Click Here to learn more about McCain..." etc. Also remove "Leadership principles.", "AI & Digital Capabilities.", "The McCain Experience." Those are generic corporate info; but they might be considered not boilerplate? They are still about McCain but not specific to role. 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 corporate description. However "Prefer a few substantive sections over many thin ones." So we could omit those sections to keep thin. But we must preserve ALL substantive information; do NOT invent or summarize away detail. If we omit those paragraphs, we are summarizing away detail (removing content). That would violate "Preserve ALL substantive information". So we must keep them. However we could incorporate them into a section like "About McCain" as prose. That would be a section. But we already have many sections; we could add "About McCain" as a section. That would increase sections but still okay if we keep them. But we need to avoid thin sections; but if we add a section with substantive paragraphs, it's not thin. So we can add About McCain section. Thus sections: About the role, Responsibilities, Requirements, About the Team, About McCain, Benefits, Pay. We need to ensure we don't create Schedule section (we have full-time info in metadata). We'll include that in metadata paragraph. Now we need to format. Let's extract exact prose. About The Role paragraph: "The Regional Agronomist executes the regional agricultural strategy developed with regional leadership and translates McCain's innovation priorities into practical, on-the-ground results. This role leads grower adoption of new potato varieties, regenerative practices, and emerging technologies while providing proactive crop risk intelligence. Working closely with growers, field teams, interns, and internal partners, the Regional Agronomist strengthens grower outcomes in yield, quality, cost, sustainability, and supply reliability." That's one paragraph. What You'll Be Doing list: - Execute the regional innovation strategy to improve yield, quality, cost, sustainability, and supply outcomes. - Lead the regional commercialization and adoption of new potato varieties by validating field and storage performance against McCain standards and demonstrating economic value to growers. - Implement regenerative agriculture initiatives with adoption-ready growers, address agronomic and economic barriers, conduct field trials, and capture grower feedback. - Pilot emerging agronomic technologies and production practices, assess real-world viability, cost-benefit trade-offs, and scalability, and provide field-level insights to leadership. - Translate regional R&D priorities and recommendations into field and storage applications with grower partners, identifying and resolving adoption challenges. - Build trusted grower relationships and serve as McCain's primary technical advisor and problem-solver for assigned grower partnerships. - Lead crop monitoring and intelligence activities, escalating emerging crop, weather, pest, disease, storage, quality, or supply risks with supporting field data. - Evaluate digital agriculture tools such as remote sensing, soil monitoring, predictive analytics, and AI-enabled solutions to improve monitoring and decision support. - Manage and develop assigned interns and support staff through clear expectations, on-the-job training, coaching, and feedback. - Develop subject matter expertise, facilitate peer learning, share regional insights across the Agronomist network, and represent McCain professionally in industry organizations and grower networks. That's 10 items. What You'll Need To Be Successful list: - Bachelor of Science degree in Plant Science, Soil Science, Agricultural Production, or a related agricultural discipline. - Strong agronomic knowledge, including crop production systems and potato production practices. - Demonstrated ability to build productive relationships with growers and agricultural stakeholders and communicate across technical and business audiences. - Sound technical judgment with the ability to assess agronomic risk, interpret field-level data, evaluate trade-offs, and make practical recommendations. - Strong facilitation, project and activity management, stakeholder coordination, and problem-solving skills. - Ability to manage multi-year adoption and monitoring activities, track execution metrics, coordinate resources, and manage multiple priorities across a geographic region. - Curiosity and willingness to adopt AI and digital agriculture tools to improve efficiency, data quality, monitoring, adoption tracking, and decision support. - Valid driver's license and willingness to travel within the assigned region. - Certified McCain Agronomist (CMA) certification within the first year of employment. - Professional Agrologist certification required for Canada-based roles; Certified Crop Advisor (CCA) certification preferred. That's 10 items. About The Team paragraph: "Reporting directly to the Regional Agronomy Manager, the Regional Agronomist is part of McCain's regional Agronomy organization. The role works closely with growers, McCain Field teams, supply chain partners, R&D teams, and regional leadership