Business Process Engineer II

We need to output HTML fragment with sections: About the role? Actually we have Overview, Responsibilities, Qualifications, Benefits & Perks, Physical Demands maybe? The instructions: 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. Do NOT repeat the job title as a 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 decide which sections to include. The posting includes Overview (intro), Responsibilities (detailed), Qualifications (Requirements, Essential Qualifications, Preferred Qualifications, Physical Demands), Benefits & Perks, Where You'll Be (location description), Who We Are (company description), etc. Also there is a YouTube link and Meet the Recruiter line; those are not needed? The instructions: remove duplicated lines, application instructions. The "Meet the Recruiter: Danielle Lomeli" maybe not needed? It's not a duty/requirement; could be considered metadata. Probably drop it. The YouTube link is external reference; maybe drop as not substantive. The "Job Summary" is part of Overview? Could be included in Overview. We need to produce sections: maybe About the role (Overview), Responsibilities, Qualifications (maybe split into Requirements and Preferred?), Benefits, Physical Demands? The instructions say use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They gave examples but we can use those that match content. We have Qualifications (Required and Preferred). We have Skills maybe implied. We have Benefits & Perks. We have Physical Demands (maybe could be under Requirements? but it's separate). The instructions: include a section ONLY when posting has real, specific content for it. Physical Demands is specific content (percentages, lifting). So we should include a section for Physical Demands. Could label it "Physical Demands" as heading

  . Not in the example list but allowed? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not exclusive. So we can add Physical Demands. We must not include Pay or Schedule because not stated. We must not include Skills unless we have explicit skills list; we have many skill-like items in Qualifications; but we could combine them under Qualifications. We need to use

  • for any list of duties/requirements/benefits. So for Responsibilities we should list each duty as
  • . For Qualifications we should list each requirement as
  • . For Benefits we list each benefit as
  • . For Physical Demands we could list as
    • but it's more like a table; but we can still list each bullet. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details from the posting, but we can format them as lists. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At the end there is EEO statement etc; we should drop that. Also "Supplemental Information Pre-employment drug testing is required." maybe keep? It's a condition; could be considered substantive. It's not EEO; it's a requirement. Might keep as a short paragraph. Also "All candidates must have valid authorization to work in the U.S. without restriction." Keep? It's a requirement; could be included under Qualifications maybe. We need to ensure we don't repeat the job title as heading. The job title is Business Process Engineer II; we should not put that as heading. We need to output only HTML fragment, no /, no markdown fences. Let's structure:

      About the role

      Overview paragraph(s) from Overview and Job Summary.

      Responsibilities

      • ... each duty ...

      Qualifications

      Maybe split into Required and Preferred? Could have two subheadings? But instruction says use

      for section headings; we could have

      Required Qualifications

      and

      Preferred Qualifications

      . That's okay. But we also have Physical Demands; could be its own

      Physical Demands

      . Benefits:

      Benefits & Perks

      . We also have "Where You'll Be" and "Who Are". Those are descriptive about company and location; could be included under About the role or separate sections like "Location" and "Company Overview". But we need to avoid thin sections. Could merge them into About the role? The About the role currently is overview; we could add location and company description there. However we need to preserve all substantive info; we can include them in About the role paragraph. Let's extract Overview text: "Overview Do you want to join a team that's changing the world? Do you have a strong background as a Business Process Engineer II? Then we're looking for you! Check out the job description and apply now! Put your skills to meaningful use, gain unique experience, and work with world-class team members with diverse backgrounds and expertise who share the same vision. Join the PECNA team today!" Then there is a YouTube link and "Meet the Recruiter: Danielle Lomeli". Then "Job Summary The Business Process Engineer II independently leads small-to-medium business process improvement initiatives that align material flow, data flow, system logic, and operational logic with business objectives. This role facilitates stakeholder alignment, develops future-state processes, applies process simulation and data analytics tools, and evaluates opportunities to improve equipment utilization and reduce downtime in a high-speed, high-volume manufacturing environment. Coaches Business Process Engineer I team members on methods and execution discipline." We can combine Overview and Job Summary into About the role paragraph. Now Responsibilities: The posting lists sections: Functional Operations, Performance Optimization & Continuous Improvement, Training & Team Support, Cross-Functional Collaboration & Communication, Quality, Safety, & Compliance, Personal Protective Equipment (PPE) Requirements. Under each there are bullet-like sentences. We need to extract each duty as list items. Let's list them: Functional Operations: - Lead current-state and future-state process analysis for assigned business areas, projects, or value streams - Facilitate stakeholder workshops to identify business requirements, process gaps, interdependencies, risks, and improvement opportunities - Coordinate with Operations, IT, Industrial Engineering, Finance, Procurement, Planning, and system owners to integrate process changes - Identify change impacts, training needs, adoption risks, and control mechanisms required to sustain implemented improvements - Provide technical advice on processing technology, capability, risks, and costs to internal customers - Communicate recommendations, risks, decisions, and results to management and cross-functional stakeholders - Support evaluation and integration of new technologies (e.g., automation, IoT-enabled systems) into assigned process areas, partnering with Engineering and IT Performance Optimization & Continuous Improvement: - Develop and implement process designs that align people, process, technology, system logic, and operational requirements - Build project plans, action trackers, decision logs, process-control plans, and implementation support materials for assigned initiatives - Use process metrics, KPI development, Excel, Power BI, SQL fundamentals, and system data to evaluate performance and validate improvements - Use process simulation/modeling software and data analytics tools to evaluate current-state performance and validate improvement recommendations - Identify opportunities to improve equipment utilization, reduce downtime, and shorten cycle times within assigned processes - Support and complete cost-benefit analysis, ROI calculations, business cases, and value-realization tracking for process improvements Training & Team Support: - Coach Business Process Engineer I team members on process methods, stakeholder management, analysis quality, and project execution discipline - Mentor and conduct hands-on training, providing process guidance and technical support to others at same or lower level within functional area - No authority to hire, transfer, suspend, lay off, recall, promote, discharge, reward, or discipline other employees Cross-Functional Collaboration & Communication: - Communicate technical and process complexity in clear business language to stakeholders at multiple levels - Build trust and influence stakeholders toward consensus without formal authority Quality, Safety, & Compliance: - Follow safety, quality, customer, data-handling, and company standards Personal Protective Equipment (PPE) Requirements: - To ensure the health and safety in the workplace and for the protection of our employees, wearing PPE is a possibility and may include equipment such as a full Tyvek suit, safety shoes, gloves, safety glasses, face mask, bump cap, and a full hazmat suit that includes a respirator. - The foregoing description is not intended and should not be construed to be an exhaustive list of all responsibilities, skills and efforts or work conditions associated with the job. It is intended to be an accurate reflection of the general nature and level of the job. We might drop the last two sentences as boilerplate? They are generic disclaimer; maybe considered boilerplate. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This disclaimer might be considered boilerplate; but it's part of responsibilities description. However it's a generic statement; we could keep it? It says "The foregoing description is not intended..." That's typical boilerplate. Safer to drop it. Now Qualifications: We have "Qualifications Requirements - Required and/or Preferred Education, Certifications, And Licenses Required: Bachelor's degree in Industrial Engineering, Computer Science, Information Technology, or a closely related engineering/technical field; OR 4 years of relevant business process engineering or manufacturing analysis experience in lieu of a degree Preferred Master's degree in Industrial Engineering, Computer Science, Information Technology, or a closely related engineering/technical field" Then "Essential Qualifications" list bullet points. Then "Preferred Qualifications" list. Then "Physical Demands" section. Then "Benefits & Perks" section. Then "Where You'll Be" and "Who We Are" descriptive. We also have "Supplemental Information Pre-employment drug testing is required." and EEO statement etc. We need to keep drug testing requirement. Now let's extract Essential Qualifications bullet points (they are sentences separated by line breaks). Let's list: - 2-4 years of professional experience in business process engineering or a related field - Previous experience in semi-conductor, automotive, or other high-volume manufacturing field - Hands-on experience in the application of business process analysis tools, including current-state process analysis, current-state performance and metrics, issue identification, root-cause analysis, business case development, cost-benefit analysis, future-state design, roles and responsibilities, metrics, and process control and management - Ability to plan and deploy business process initiatives with moderate complexity and cross-functional involvement - Able to apply business process principles to business solutions - Able to recognize functional interdependencies, structural issues, redundancies, and process-control needs - Able to assimilate and correlate disconnected business information and articulate its collective relevance to the organization - Able to develop metrics, collect data, and analyze data to identify cause and measure performance against process requirements - Strong communication, facilitation, and influence skills across multiple levels of the organization - Self-starter with demonstrated project management skills, including the ability to prioritize tasks, manage timelines,