Shop Systems & Continuous Improvement Specialist

or drop it. Location is minor metadata; we could put it in a short p under Requirements or maybe under About the role. Since we have Schedule for in-office days, location could be separate but not required. We'll include location as a short p under Requirements (or maybe under About the role). I'd put it under Requirements as a note. - Skills: list of skills. - Schedule: in-office 4 days per week (Mon-Thurs); Fridays optional remote. - Benefits: none. - Pay: none (skip). Now we need to output HTML fragment with appropriate headings

and content. We must not repeat job title as heading. No job ID. We must preserve all substantive information; do not invent or summarize away detail. We need to convert lists to

• . For prose, use

  . We need to ensure we don't create sections with filler text. Let's extract details. About the role: Paragraph 1: "It's fun to work in a company where people truly believe in what they are doing. At Dutch Bros Coffee, we are more than just a coffee company. We are a fun-loving, mind-blowing company that makes a difference one cup at a time." Paragraph 2 (Position Overview): "The Shop Systems & Continuous Improvement Specialist supports the execution of product, process, and equipment testing within the company’s in-house test kitchen. This role supports the design, execution, and analysis of product, process, and equipment testing within the company’s in-house test kitchen and mock shop environments. The Specialist partners with the Manager of Shop Systems and Continuous Improvement to evaluate operational innovations, interpret test results, and provide insights that inform scalable shop systems, workflows, and equipment solutions for the field." We could combine into one or two

  . Responsibilities: Key Result Areas sections: List them: - Test Kitchen Operations & Support - Maintain operational readiness of the Test Kitchen and Mock Shop to support cross-functional testing initiatives - Execute daily setup, breakdown, and cleanliness standards for the Test Kitchen and Mock Shop - Coordinate test environment setup to accurately replicate field conditions and operational workflows - Monitor equipment functionality and escalate opportunities for improvement or maintenance - Maintain inventories of ingredients, equipment, smallwares, and testing supplies as directed - Follow food safety, test kitchen SOP’s, and OSHA guidelines within the test kitchen - Support scheduled kitchen usage for R&D, Operations, and Training teams - Assist with basic equipment maintenance, coordination, and calibration scheduling - Collaborate with Operations, Product Development, Training, and Equipment teams to support testing and operational innovation - Product And Process Testing Execution - Analyze test outcomes and identify operational implications for shop workflows, equipment, or processes - Synthesize testing observations into structured feedback for Operations, Product, and Training teams - Partner with cross-functional stakeholders to refine testing protocols and evaluation criteria - Identify operational risks, inefficiencies, or scalability challenges discovered during testing - Execute product, process, and workflow tests as outlined - Set up stations to replicate field conditions based on provided guidance - Support time studies, ergonomic observations, and deviations in testing logs - Assist with pre-field validation documentation and photo/video capture - Communicate testing results and insights to stakeholders in clear and actionable formats - Testing & Validation Support For Broista Centric Solutions - Assist with in-kitchen testing of equipment, tools, and layouts - Support voice of the customer efforts by gathering and documenting tester and stakeholder feedback before, during, and after testing following established protocols - Facilitate voice-of-the-customer insights during testing by collecting, synthesizing, and summarizing feedback from testers and stakeholders - Translate field feedback into actionable observations to inform product, equipment, and process decisions - Support mock deployments and controlled trials of equipment and processes - Flag issues, inconsistencies, or safety concerns to leadership - Coordinate with vendors as needed - Operational Insight & Continuous Improvement - Identify opportunities to improve shop workflows, equipment usability, or testing processes based on observations during testing - Provide recommendations that support the evolution of shop systems and operational best practices - Contribute to documentation and knowledge sharing that enables scalable operational improvements We need to output as

  • for each bullet. Should we keep the subheadings (like Test Kitchen Operations & Support) as separate

    ? Not allowed; only headings allowed are

    for section headings. We could treat each subsection as a

    heading? But we cannot add extra headings besides the allowed ones. However we can still include the subsection titles as plain text within

    or ? The instruction: 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 forbid other HTML tags like or

      inside lists. So we can keep the subsection titles as

      or maybe as inside

    • ? But they are not list items; they are category headings. Could we treat each category as a
    • with sublist? That would be nested lists, but still using
      • . That's acceptable: we can have outer
        for responsibilities, each top-level
        • being the category, and inside each
        • we can have a
          for the specific duties. That would preserve structure. Thus:

          Responsibilities

          • Test Kitchen Operations & Support

            • Maintain operational readiness of the Test Kitchen and Mock Shop to support cross-functional testing initiatives
            • Execute daily setup, breakdown, and cleanliness standards for the Test Kitchen and Mock Shop
            ... etc
          ...
          That seems okay. Now Requirements: Required Job Qualifications: "2-4 years of experience in food service operations, product development, or equipment testing. QSR or coffee industry experience preferredExposure to QSR, coffee, or high-volume foodservice environments preferredWorking knowledge of basic equipment operations and innovation processesExperience following testing protocols and documenting results accurately" Note there is no spacing between sentences; we need to parse. It appears as: "2-4 years of experience in food service operations, product development, or equipment testing. QSR or coffee industry experience preferredExposure to QSR, coffee, or high-volume foodservice environments preferredWorking knowledge of basic equipment operations and innovation processesExperience following testing protocols and documenting results accurately" We need to add spaces where missing: after "preferredExposure" -> "preferred. Exposure". after "environments preferredWorking" -> "environments. Preferred working". after "innovation processesExperience" -> "processes. Experience". We'll reconstruct. Thus required qualifications: - 2-4 years of experience in food service operations, product development, or equipment testing. - QSR or coffee industry experience preferred. - Exposure to QSR, coffee, or high-volume foodservice environments preferred. - Working knowledge of basic equipment operations and innovation processes. - Experience following testing protocols and documenting results accurately. We'll put as
          • . Qualifications: Preferred Bachelor's Degree in Culinary Science, Food Technology, Engineering, or related field (or equivalent experience). Also maybe location requirement? But location is minor metadata; we could include as a short p under Qualifications or Requirements. Let's decide: We'll put location under Qualifications as a note? But location is not a qualification. Perhaps better to put location under Requirements