Process Engineer

indicating required vs preferred. Or we can combine into one list with labels. Better to separate:

Required:

... then

Preferred:

... That's okay. Responsibilities: we have Key Responsibilities with subpoints. We'll extract bullet points. About the role: description paragraph(s) before Responsibilities. Pay: compensation range. Schedule: Full Time. Benefits: list. We must not include boilerplate like Application Deadline, Department, Employment Type, Location, Reporting To (these are metadata). We can fold minor metadata into a short

or drop it. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we could include a short

with location, department, reporting to? But they said fold minor metadata into a short

or drop it. Probably we can include a

with location and department etc. But we already have Schedule section for full time. Location maybe not needed. Could include a short

at top: "Location: Maple Grove, MN | Department: Network Planning and Operational Structure | Reporting To: Operations Manager". That's minor metadata. We'll include that as a

. We must not repeat job title as heading. The title is Process Engineer (or Senior). Not used. Now produce HTML. Structure:

Location: Maple Grove, MN | Department: Network Planning and Operational Structure | Reporting To: Operations Manager

About the role

... description paragraphs ...

Responsibilities

• ...
...

Requirements

Required:

...

Preferred:

...

Skills

... maybe from Skills, Knowledge and Expertise? Actually that section includes both skills and qualifications. But we already have Requirements. The Skills section could list skills like "Strong safety mindset", "Ability to translate complex processes", etc. But those are already in Required. Might be redundant. However we can still include Skills as a separate section with bullet points from that section that are not captured elsewhere. But risk duplication. The instruction: Prefer a few substantive sections over many thin ones. Maybe we can combine Skills into Requirements. But we have a separate Skills heading allowed. Could we omit Skills section? The posting has a "Skills, Knowledge and Expertise" heading with content. That is substantive. So we should include Skills section. We'll put the bullet points from that section (the list of required and preferred? Actually that section includes both required and preferred? It says "This position is offered at two levels..." then lists Required and Preferred. That's more qualifications. So maybe Skills section is not separate; the "Skills, Knowledge and Expertise" is essentially qualifications. So we could treat that as Requirements. But we already have Requirements. To avoid duplication, we could make Requirements contain the required and preferred qualifications, and Skills could be omitted or we could combine. However the instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So they expect possibly both Requirements and Skills sections. But we can decide to include Skills with the bullet points from the "Skills, Knowledge and Expertise" that are not already captured as required/preferred? Actually the required and preferred are under that heading. So maybe we should treat that as Skills section, and Requirements could be omitted or we could put required qualifications there. But we need to capture all substantive info. Let's think: The posting has a section titled "Skills, Knowledge and Expertise" with subbullets: Required and Preferred. That's the main qualifications. There's no separate "Requirements" section elsewhere. So we could map that to either Requirements or Skills. Since both headings are allowed, we need to choose one. The instruction: "Prefer a few substantive sections over many thin ones." So we should not split into both Requirements and Skills if they cover same content. Better to put all qualifications under one heading, either Requirements or Skills. Which is more appropriate? The content includes required education, experience, etc. That's more like Requirements. Skills could be things like "Strong safety mindset", "Ability to translate...". Those are also in required. So I'd put everything under Requirements. Then we can omit Skills section. But we must ensure we don't miss any content that is purely skill-like not captured elsewhere. The required list includes: Bachelor’s degree, 5 years experience, experience in technology transfer, sound knowledge of fermentation fundamentals, experience in data analysis systems, strong safety mindset, demonstrated ability to communicate technical concepts, ability to translate complex processes, comfortability to lead client interactions. Preferred list includes Master’s degree, 8+ years experience, downstream expertise, prior CDMO experience, experience writing fermentation scripts, experience with Factory Talk/Ignition. All these are qualifications/skills. So we can put them under Requirements. Thus we will have sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. We'll also include a short metadata p. Now extract About the role description: The paragraph(s) after "Description" up to before "Key Responsibilities". Let's copy: "The Process Engineer will be part of BioMADE’s Maple Grove pilot plant operations team. This pilot plant will help bridge a gap in the domestic biotech industry (non-pharma), providing clients with emerging fermentation technologies the ability to demonstrate upstream and downstream processes at a scale which supports future commercial scale design. This position is responsible for translating customer fermentation and downstream process requirements into operational procedures, batch documentation, and technical guidance that enable the Operations team to successfully execute production campaigns. Compensation and title (Process Engineer or Senior Process Engineer) will be determined based on candidate’s experience. Working closely with the Projects Lead, Operations Manager, Shift Supervisors, and Technical Laboratory Manager, the Process Engineer serves as the primary technical interface between customers and production facility operations during process technology transfer, campaign preparation, production execution, and post-production technology transfer closure. The role requires strong knowledge of fermentation processes and downstream processing unit operations, with particular emphasis on downstream separations and purification systems. The Process Engineer will actively promote and exemplify a “zero harm” safety culture." That's the About the role. Now Responsibilities: Under "Key Responsibilities" there are three subheadings: Technology Transfer and Process Implementation, Bench-Scale Trials and Process Validation, Operations Support, Safety Leadership. We'll combine all bullet points into a single list under Responsibilities. Let's extract bullet points: Technology Transfer and Process Implementation: - Work with Projects Lead to translate client technology transfer packages into executable production processes. - Understand, communicate, and convert client process expectations into: batch records, batch recipes, operating procedures, process control parameters, process flow summaries, and operational guidance including operator training documents - Ensure process documentation and training positions the Operations team to execute production campaigns safely and effectively. - At the conclusion of client campaigns, prepare process summary reports and data packages for client representatives to include, but not limited to, items such as fermentation performance (titer, rate, yield) against expectations, downstream unit operation performance (to include yields), analytical results. Process deviations should be summarized for the client. Bench-Scale Trials and Process Validation: - With the Technical Lab Manager, support planning and assessment of laboratory trials as required using bench-scale fermentation and downstream equipment to: - Demonstrate the viability of client technology transfer packages - Identify and close potential gaps prior to running the process at pilot scale. - This may include generating data related to: fermentation performance, downstream separation performance, product recovery yields Operations Support: - Serve as primary technical expert for process unit operations, training shift supervisors and operations team on fundamental principles of operation, modes of operation, programming sequences, equipment safeguards, alarms (purpose and response), and troubleshooting. - At the direction of the Operations Manager, prepare standard operating procedures, troubleshooting guides, and other reference documents that provide a foundation for consistent operation and understanding. - Collaborate with shift supervisors and process operators to address process observations, concerns, and recommendations. Use these to develop and execute action plans. - Foster an environment of open communication and continuous improvement. - Utilize plant process data as well as in process analytical data to create dash boards and metrics that the Operations Manager deems to provide value for team performance. - Work with Operations Manager and Maintenance Manager to provide troubleshooting support for fermentation and downstream equipment, recommending corrective action and improvements as needed. - May provide hands-on operational support during critical campaigns, startup activities, commissioning efforts, or periods of limited staffing. Safety Leadership: - Actively support the facility’s “zero harm” safety culture by: - Leading by example - Ensuring process procedures include safety considerations - Work with the team to identify and address potential hazards in fermentation and downstream operations - Engaging plant personnel in proactive safety discussions We'll turn each bullet into

. Some have sub-bullets; we can flatten them. Now Requirements: We'll list required and preferred. Required: - Bachelor’s degree in one of the following fields: Chemical Engineering, Biochemical Engineering, Bioprocess Engineering, or other related disciplines. - 5 years experience as process engineer in fermentation or bioprocess development or manufacturing environments. - Experience in technology transfer, process development, or production support (commercial or CDMO scale) - Sound knowledge of Fermentation fundamentals and downstream separation technologies - Experience in Data analysis systems, process monitoring, and process troubleshooting acumen - Strong safety mindset with demonstrated commitment to safe work practices - Demonstrated ability to effectively communicate technical concepts to operations, laboratory, maintenance personnel, and customers/clients. - Ability to translate complex processes into operational procedures and guidelines. - Comfortability to lead client interactions and project coordination. Preferred: - Master’s degree in one of the following fields: Chemical Engineering, Biochemical Engineering, Bioprocess Engineering, or other related disciplines. - 8 or more years experience as process engineer in fermentation or bioprocess development or manufacturing environments. - Downstream expertise preferred with unit operations such as, but not limited to, centrifuges (disc stack, decanter), ultrafiltration, microfiltration, ion exchange, evaporators, spray dryers, and homogenizers. - Prior experience within CDMO environment (preferably with food-safe quality standards), bench-to-pilot scale up, pilot-to-commercial scale up. - Experience writing and modifying fermentation scripts and recipes utilizing a variety of programming methodologies and languages - Experience with Factory Talk and/or Ignition automation and programming environments Now Benefits: extract list. Benefits paragraph includes many items. We'll make a list. - 100% Employer paid options for medical insurance for BioMADE employees. - Low-cost buy-up options also available. - Generous cost