Chemical Process Engineer

We need to produce HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: Business Unit, Division, Who are we looking for? (description of purpose). What will you be doing? (list of duties). Who are You? (education/experience). What competencies will you need? (skills). We are Offering... (benefits, bonus, 401k, insurance, holidays, etc). Also salary range given. No schedule info. So we can have sections: About the role (purpose), Responsibilities (duties), Requirements (education/experience), Qualifications (maybe same as requirements? but we can combine? The instruction: use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content. We have content for About the role (purpose). Responsibilities (list of duties). Requirements (education/experience). Qualifications maybe overlapping with requirements; but we could treat "Who are You?" as Requirements (education/experience). "What competencies will you need?" as Skills. Benefits: "We are Offering..." includes benefits: competitive base salary, performance related bonus plan, 401k with company matching, Life Insurance, Medical Insurance, 9 holidays. Also mention innovative, socially responsible, rewarding performance but those are culture not benefits. We'll include Benefits section with those items. Pay: Salary range given: $81,470 to $122,206 DOE and Education. So we can include Pay section. Schedule: none, so omit. We must not repeat job title as heading. No Job ID etc. We need to use

for each section heading. Use

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

  for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate etc. We need to output only HTML fragment. Let's extract details. About the role: "The primary purpose of this position is to participate in chemical process design and testing of new manufacturing technologies, pilot and plant scale-up & troubleshooting process problems. The position is part of the Global Process Engineering Group (GPEG) with the responsibility for effectively scaling-up new Chemical processes & improving current chemical processes and products by optimizing process parameters to improve throughput, investigate cost reduction opportunities, while maintaining or improving product quality." We can put that as

  . Responsibilities: list from "What will you be doing?" bullet points (though not bullet in text). We need to convert each sentence into list items. Let's list them: - Participate in design and implementation of manufacturing processes from the laboratory and concept stage through pilot plant and manufacturing scale-up - Conduct pilot scale experiments and tests needed to develop and/or improve production processes. - Perform validation of new and existing processes/equipment to improve yield, product performance and/or to introduce new materials. - Interfaces with various departments (R&D, Operations, Quality, Marketing) to ensure processes and designs are compatible for new product technology transfer. - Construct, edit and maintain Piping and Instrumentation Diagrams (P&ID’s). - Develop specifications and test methods for new and existing production processes. - Test components of new processes in laboratory setting, and design pilot projects for next step of small-scale testing. - Investigates and troubleshoots process problems - Monitor process capabilities and performance through standard statistical process control and analysis methods. - Improve manufacturing processes by performing comprehensive evaluation of processes, materials and equipment and identifying areas and methods of improvement - Participate in reducing process variability. - Responsible for exhibiting professional behaviour with both internal/external business associates that reflects positively on the company and is consistent with the company’s policies and practices. - Utilizes process simulation software to work out the best production methods/equipment. - Maintain laboratory safety protocols - Perform other duties & projects as assigned. We need to keep as list items. Requirements: "Who are You? A bachelor’s degree required in a STEM field, Chemistry or Chemical Engineering preferred.Minimum of 1 year of experience, 3 years preferred, of relevant manufacturing experiencePilot production or scale up experience is preferredAbility to work in fast paced environment." We can split into list items: - Bachelor’s degree required in a STEM field; Chemistry or Chemical Engineering preferred. - Minimum of 1 year of experience, 3 years preferred, of relevant manufacturing experience. - Pilot production or scale up experience is preferred. - Ability to work in fast‑paced environment. Qualifications: maybe we could treat same as Requirements? But we need a section only if there is real specific content. Could we treat "What competencies will you need?" as Qualifications? Actually that is skills. So Qualifications could be empty; better to omit Qualifications section if no distinct content. However we have "Who are You?" which is requirements; we could also treat that as Qualifications. But we need to avoid duplication. The instruction: use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't say we must use all; we include only those with real content. Thus we can have: - About the role - Responsibilities - Requirements (education/experience) - Skills (competencies) - Benefits - Pay We'll omit Qualifications. Now Skills: list from "What competencies will you need?": - Exceptional written and oral communication skills - Advanced mathematical skills - Ability to read, analyze and interpret scientific journals, reports and documents - Great attention to detail - A self starter while working in a collaborative environment Note there is a typo "wiritten" and "collaboritive". We must preserve as is? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Should we keep the typos? Likely yes, we should keep the exact text. So we keep "Exceptional wiritten and oral communication skills" and "collaboritive". We'll keep them. Benefits: from "We are Offering..." paragraph: "As part of our team here, as well as receiving a competitive base salary, you will also participate in a generous performance related bonus plan. In addition, you will also receive a 401k plan with company matching, Life Insurance, and Medical Insurance as well as 9 holidays." Also there are culture paragraphs but those are not benefits; we can ignore as not specific benefit? The instruction: preserve ALL substantive information; but we can omit boilerplate like culture statements? They are not boilerplate but they are substantive? They are about company values. Might be considered substantive but not a benefit. However we have no section for culture; we could include them in Benefits? But they are not benefits. The instruction says include a section ONLY when the posting has real, specific content for it. It doesn't say we must include culture. We could omit those paragraphs as they are not requested sections. However we must preserve ALL substantive information; but we are allowed to drop sections not requested? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Culture statements are not boilerplate; they are substantive. But we have no heading for culture; we could incorporate them into Benefits? Might be misrepresenting. However the instruction says "Prefer a few substantive sections over many thin ones." So we could add a section like "About the company" but not in allowed headings. The allowed headings list is given as examples; we could still add other headings? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive. But to be safe, we could add a section "Company Overview" with that content. However the instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings. But they said "Prefer a few substantive sections over many thin ones." So we could add a section for company culture/values. However the user didn't ask for that explicitly; they gave a list of possible headings. I'd stick to those headings only, and omit culture paragraphs as they are not covered by those headings. But then we would be dropping substantive information (the culture statements). That might violate "Preserve ALL substantive information". However maybe those are considered boilerplate? They are not legal/EEO etc. They are about company values; could be considered boilerplate? Not sure. Given the typical tasks, they often want to keep the benefits and pay etc, and culture statements can be omitted as they are not requested. I think it's acceptable to omit them as they are not part of the requested sections. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Culture statements are not those. But they also said "Prefer a few substantive sections over many thin ones." So maybe they expect us to include only the sections that have clear content matching the headings. The culture statements could go under "About the role"? Not really. Could go under a generic "About the company" but not in list. I'll assume it's okay to omit them. Thus Benefits section will contain the list: competitive base salary, generous performance related bonus plan, 401k plan with company matching, Life Insurance, Medical Insurance, 9 holidays. We'll put as

  • . Pay section: Salary range: $81,470 to $122,206 DOE and Education. We'll put as

    . Now produce HTML. Structure:

    About the role

    ...

    Responsibilities

    • ...
    ...

    Requirements

    • ...
    ...

    Skills

    • ...
    ...

    Benefits

    • ...
    ...

    Pay

    Salary range for this role is $81,470 to $122,206 DOE and Education.

    Make sure to preserve original phrasing: "Salary range fro this role is $81,470 to $122,206 DOE and Education." There's a typo "fro". We must preserve it. So we keep exactly: "Salary range fro this role is $81,470 to $122,206 DOE and Education." Now check for any other specifics: Nearest Major Market: New Jersey. That's location info. Could be included maybe in About the role? Not required. Could be a separate section? Not in headings. Might be considered metadata; we could fold into a short

    maybe under About the role? But we already have a paragraph. Could add a sentence: "Nearest Major Market: New Jersey." But that is minor metadata; instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it." So we could add a short

    after About the role maybe. But we already have About the role paragraph; we could append location info there. However we must preserve ALL substantive information. So we should include location. Let's add a sentence: "Nearest Major Market: New Jersey." Could be its own

    after About the role. But we must not create extra sections; just a short

    . Thus About the role could have two paragraphs: first the purpose, second location. Alternatively we could add location as a separate

    after About the role before Responsibilities. Let's do that. Now check for any other metadata: Business Unit: MAES Division: Packaging & Board Assembly. That's also