Principal QA Engineer

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate like EEO, etc. Must not invent or summarize away detail. Must not include sections with filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes salary range: $150,000- $215,000. Also mentions discretionary incentive award, Minnesota Sick and Safe Leave accruals. Those are benefits? Could be considered Benefits. Also mentions compensation varies etc. So we can include Pay section with salary range. Benefits section could include discretionary incentive award and sick leave accruals. Schedule? Not mentioned. So we should not include Schedule. About the role: we have job purpose and impact paragraph. That could be About the role. Responsibilities: Key Accountabilities bullet list. Requirements: maybe Qualifications? Actually Qualifications section includes minimum requirement of 6 years, typical 10 years, preferred qualifications. Could be Requirements and Qualifications separate? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what content goes where. Likely: About the role = Job Purpose and Impact. Responsibilities = Key Accountabilities (list). Requirements = Minimum requirement of 6 years etc? Or maybe Requirements = Minimum requirement? Qualifications = Preferred Qualifications? Skills = maybe programming languages etc? Could combine. But we must not create thin sections. Let's see content: - Job Purpose and Impact: paragraph about leading design etc. That's substantive. - Key Accountabilities: list of bullet points (SOFTWARE DEVELOPMENT, TECHNICAL GUIDANCE, QUALITY ASSURANCE, TESTING & DEBUGGING, COLLABORATION, CONTINUOUS IMPROVEMENT, DOCUMENTATION, TECHNICAL SUPPORT). Each has description. That's responsibilities. - Qualifications: Minimum requirement of 6 years of relevant work experience. Typically reflects 10 years or more of relevant experience. Preferred Qualifications: Professional experience as QA Software Engineer with proficiency programming in C++, Javascript or similar languages. Demonstrated experience in Cloud & DevOps integration and practices, including code management, CI/CD, and deployment strategies. We could treat "Qualifications" heading for both minimum and preferred. Or split into Requirements (minimum) and Qualifications (preferred). The instruction includes both Requirements and Qualifications headings. So we can put minimum experience under Requirements, and preferred qualifications under Qualifications. Skills maybe not explicitly listed; but we have programming languages etc could be under Skills. However we already used programming languages in Qualifications. Could still have Skills section for languages, Cloud & DevOps, etc. But that may be thin. Better to keep Qualifications include both. But we have both headings available; we could put minimum under Requirements, preferred under Qualifications, and maybe Skills empty -> we should not include Skills if no specific content. So we omit Skills. Benefits: discretionary incentive award, Minnesota Sick and Safe Leave accruals. Also maybe mention "This position is eligible for a discretionary incentive award." and sick leave. So we can include Benefits. Pay: salary range $150,000- $215,000. Also note compensation varies etc. That's Pay. Schedule: none -> omit. Now we need to format: Use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. So we must keep the details exactly as given, but we can format into lists. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we must remove lines like "Equal Opportunity Employer, including Disability/Vet." and "To apply using chat/text, please click Apply Now button OR use this link to create a login to apply." Also remove the introductory paragraph about Cargill? That's generic company description; is that considered boilerplate? It's not about the job; it's company overview. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The company overview might be considered not boilerplate but it's not specific to the job; but it's substantive? It's about Cargill's mission. Might be considered generic but not prohibited. However we might keep it as part of About the role? The About the role heading expects job purpose and impact; the company overview could be considered extra but not required. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The company overview is substantive about the company but not about the job. It might be considered boilerplate? Not sure. Usually such intros are considered boilerplate but not explicitly listed. Safer to keep it? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It does not say remove company overview. So we can keep it. However the About the role section could include that overview plus job purpose. But we must not repeat job title as heading. We'll put the company overview in a

  under About the role before the job purpose paragraph. Now we need to format lists. Key Accountabilities: each heading like SOFTWARE DEVELOPMENT: then description. We could make each as

• with strong heading? But we need to preserve detail. Could do
• SOFTWARE DEVELOPMENT: Leads and advises the design and implementation ...
. That preserves. Similarly for others. Requirements: Minimum requirement of 6 years of relevant work experience. Typically reflects 10 years or more of relevant experience. Could be two sentences; we can put in

or

• . Since it's not a list but we can use

  . The instruction: Use

  • for any list of duties/requirements/benefits. So if we treat requirements as list, we could use
    • . But it's not a list of items; it's just statements. Safer to use

      . Qualifications: Preferred Qualifications: Professional experience as QA Software Engineer with proficiency programming in C++, Javascript or similar languages. Demonstrated experience in Cloud & DevOps integration and practices, including code management, CI/CD, and deployment strategies. Could be two sentences; we can put in

      or list. Benefits: discretionary incentive award, Minnesota Sick and Safe Leave accruals. Could be list. Pay: salary range $150,000- $215,000. Also note compensation varies depending on factors etc. Could be two sentences. Now produce HTML fragment. Let's craft:

      About the role

      Cargill is committed to providing food and agricultural solutions to nourish the world in a safe, responsible, and sustainable way. Sitting at the heart of the supply chain, we partner with farmers and customers to source, make and deliver products that are vital for living. Our 155,000 team members innovate with purpose, providing customers with life’s essentials so businesses can grow, communities prosper, and consumers live well. With over 160 years of experience as a family company, we look ahead while remaining true to our values. We put people first. We reach higher. We do the right thing—today and for generations to come.

      The Advisor, Trading Engineering job leads and advises the design, development and delivery of trading software initiatives that drive the trading operations. As a recognized subject matter expert in trading engineering, this job provides technical thought leadership for the co-creation and maintenance of sophisticated software applications vital to organizational trading activities, leading cross functional teams to conceptualize, design and adopt best in class industry standards and emerging technologies to improve the performance and capabilities of the trading systems and advance business objectives. This job also leads code reviews and insights and knowledge sharing to uphold the standards of excellence and advance trading engineering team's capabilities.

      Responsibilities

      • SOFTWARE DEVELOPMENT: Leads and advises the design and implementation of robust trading systems, applying appropriate technologies to write clean, efficient and maintainable code, integrating market data feeds from financial providers and exchanges to process real time data, and customizing solutions to align with trading strategies and regulatory requirements.
      • TECHNICAL GUIDANCE: Applies expertise in software development and deployment automation to mentor and support the software engineering team, improving trading applications' performance, scalability and reliability, and validating software architecture to support high frequency trading, real time data processing and low latency communications.
      • QUALITY ASSURANCE: Leads and advises adherence to the highest standards of quality and performance in all trading software applications through rigorous testing, comprehensive code reviews, and strict adherence to best in class industry standards to prevent system failures that lead to significant financial losses.
      • TESTING & DEBUGGING: Leads the development of comprehensive test plans, including unit and integration tests, to validate functionality and performance, applying mastery debugging skills to resolve software defects and maintain system integrity, performing highly complex testing to ensure the system handles high transaction volumes, and engaging with quality assurance teams members to ensure software meets standards before deployment.
      • COLLABORATION: Reviews to align technical solutions with business goals, engaging with traders, analysts, and other teams to gather requirements and deliver needed solutions, influencing agile practices like standups and sprint planning for effective communication, leading knowledge sharing through code reviews to foster learning and best in class industry standard, and articulating technical concepts clearly to nontechnical team members.
      • CONTINUOUS IMPROVEMENT: Advocates the commitment to improving system performance, scalability and reliability to ensure systems evolve with changing needs, influencing teams to stay current with industry trends and best in class industry practices, leading continuous improvements to development processes and tools, and integrating users and stakeholders feedback to refine software solutions.
      • DOCUMENTATION: Leads establishing and maintaining technical documentation of system architecture and development processes, ensuring clear technical guides and operation manuals to facilitate ease of use, maintaining compliance with regulations and policies, and building the knowledge base for delivering onboarding and training new team members.
      • TECHNICAL SUPPORT: Leads and mentors monitoring live trading systems for optimal performance, including addressing real time issues promptly, responding quickly to resolve highly complex operational problems, minimizing downtime and risk, mentoring routine maintenance to keep systems secure and efficient, and leading disaster recovery planning to ensure business continuity during system failures or crises.

      Requirements

      Minimum requirement of 6 years of relevant work experience. Typically reflects 10 years or more of relevant experience.

      Qualifications

      Preferred Qualifications: Professional experience as QA Software Engineer with proficiency programming in C++, Javascript or similar languages. Demonstrated experience in Cloud & DevOps integration and practices, including code management, CI/CD, and deployment strategies.

      Benefits

      • Discretionary incentive award (amount dependent upon company performance and personal performance).
      • Minnesota Sick and Safe Leave accruals of one hour for every 30 worked, up to 48 hours per calendar year unless otherwise provided by law.

      Pay

      The expected salary for this position is $150,000- $215,000. Compensation varies depending on a wide array of factors