Process Engineer I
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to parse the job posting.
First, there is a description: "At CRB, we design and build..." That's about the company. Could be "About the role"? Actually "About the role" heading is for description of role. The posting includes "Job Description The Entry-Level Process Engineer focuses on the design and engineering of manufacturing facility and equipment, supporting facility infrastructure and critical utility systems." So we can put that under About the role (or maybe Responsibilities). The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections to include based on content.
We have:
- About the role: description of role, tasks, core activities.
- Responsibilities: maybe list of duties: execution of engineering calculations, supporting documentation, support field installation, work closely with others, self-check, manage time, solve complex problems, project work includes levels of design, works on basic complexity under direction, engineering deliverables list.
- Requirements: maybe qualifications: ABET-accredited Bachelor’s degree in mechanical, chemical or bioprocess engineering; 0 to 3 years of experience in a design firm setting; FE exam registration or completion preferred.
- Qualifications: maybe same as Requirements? Actually they have "Qualifications" section in posting: ABET-accredited Bachelor’s degree ... 0 to 3 years ... FE exam registration or completion preferred. Then "Preferred Qualifications" list.
- Skills: maybe list of skills: fundamental experience with performing engineering calculations, developing and implementing list of discipline systems designs; chemistry/biochemistry; process modeling, material and energy balances; fluid mechanics, hydraulic modeling, heat transfer; strong communication skills; ability to participate in internal cross-discipline project team coordination; proficient at fundamental discipline design calculations under supervision; proficiency in AutoCAD; proficiency in Microsoft Office suite; proficiency in engineering software applications including CAD, process modeling and calculation programs.
- Benefits: posting says "CRB offers a complete and competitive benefit package designed to meet individual and family needs." That's a statement about benefits. So we can include Benefits section with that sentence.
- Pay: not mentioned. So we should NOT include Pay section.
- Schedule: not mentioned. So omit Schedule.
We must not include boilerplate like EEO, equal opportunity, etc. Remove those lines.
Also remove "Additional Information" about confidentiality, EEO, etc. Also remove "Employment is contingent on background screening." etc. Also remove "CRB does not accept unsolicited resumes..." etc. Also remove "Please, no phone calls or emails." Also remove "If you are unable to complete this application due to a disability..." etc.
We must preserve all substantive information. So we need to keep the description of role, responsibilities, qualifications, preferred qualifications, skills, benefits statement.
We need to format using headings, - for any list of duties/requirements/benefits, and
for prose.
We need to decide what is a list vs prose.
We have core activities list: "Supports the documentation of the process design scope in coordination with other disciplines." etc. That's a list of bullet-like sentences. Could be turned into
- .
Similarly engineering deliverables list: list of items.
Qualifications: bullet list? Could be prose but we can make list.
Preferred qualifications: list.
Skills: list.
Benefits: just a sentence, so
.
We must not repeat the job title as a heading. The job title is "Entry-Level Process Engineer". Not to be used as heading.
We must not put Job ID/requisition numbers as headings.
We must output only HTML fragment.
Let's craft.
First, maybe start with
About the role
then a describing role: "The Entry-Level Process Engineer focuses on the design and engineering of manufacturing facility and equipment, supporting facility infrastructure and critical utility systems. Typical tasks include execution of engineering calculations including heat transfer and pressure drop calculations. The Entry-Level Process Engineer is responsible for supporting the documentation of the process design scope in coordination with other disciplines. The Entry-Level Process Engineer may support field installation teams and execute construction site observations. This role is expected to work closely with other architects, engineers and designers, as well as other internal and external team members to ensure a coordinated, constructible and complete design."
Then
Responsibilities
then a with items:
- Supports the documentation of the process design scope in coordination with other disciplines.
- Works closely with other architects, engineers and designers, as well as other internal and external team members to ensure a coordinated, constructible and complete design.
- Self-checks own work but communicates often with peers and Supervisor.
- Able to work on one or more projects concurrently and manage time effectively.
- Solves complex problems under the direction and supervision of a mentor or supervisor.
- Project work may include all levels of design such as studies, conceptual and schematic design, design development, construction documentation and construction administration.
- Works on matters of basic complexity in a support role under the direction of more experienced Process Engineers.
- Engineering deliverables include: Block and Process Flow Diagrams; User Requirements Specifications; Equipment List; Equipment General Arrangements; Equipment Datasheets; Utility Summary; Piping and Instrumentation Diagrams (P&IDs).
We could split engineering deliverables as separate list or include as one item with sublist? Simpler: keep as one item with semicolons.
Then Requirements
then :
- ABET-accredited Bachelor’s degree in mechanical, chemical or bioprocess engineering
- 0 to 3 years of experience in a design firm setting
- Fundamentals of Engineering exam registration or completion preferred
Then Preferred Qualifications
then :
- Fundamental experience with performing engineering calculations, developing and implementing list of discipline systems designs
- Fundamental experience with chemistry/biochemistry
- Fundamental experience with process modeling, material and energy balances and basic sizing calculations
- Fundamental experience with fluid mechanics, hydraulic modeling and fundamental heat transfer
- Strong communication skills and ability to participate in internal cross-discipline project team coordination
- Proficient at fundamental discipline design calculations under the supervision of an engineer
- Proficiency in AutoCAD
- Proficiency in Microsoft Office suite required
- Proficiency in engineering software applications including computer-aided drafting, process modeling and calculation programs
Then Skills
maybe we could combine with Preferred Qualifications? But they asked to use Skills section if there is real specific content. The preferred qualifications already list skills. Could we treat them as Skills? The instruction: Use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we have Qualifications (maybe the required qualifications) and Skills (maybe the preferred qualifications/skills). We already used Requirements for required qualifications. We have Qualifications maybe we could use for the "Qualifications" section (the required). But we already used Requirements. Let's map:
- Requirements: required qualifications (degree, experience, FE exam)
- Qualifications: maybe the "Qualifications" heading in posting (which is same as required). But we can't duplicate. Perhaps we treat "Qualifications" as the required qualifications and "Skills" as the preferred qualifications/skills. However the instruction says we can use those headings; we need to include a section only when posting has real specific content for it. So we need to decide which headings to use.
We have content for:
- About the role (description)
- Responsibilities (duties)
- Requirements (required qualifications)
- Qualifications (maybe same as Requirements? but we could treat as "Qualifications" for the required qualifications and skip Requirements? But we need to avoid duplication. The posting has a section labeled "Qualifications" (required) and then "Preferred Qualifications". So we could use Qualifications
for the required qualifications (degree, experience, FE exam). Then Skills
for the preferred qualifications and skills list. Then we could also have Responsibilities
for duties. And About the role
for overview.
Thus we would not use "Requirements" heading. That's okay; we only include headings with real content.
Thus sections:
- About the role
- Responsibilities
- Qualifications (required)
- Skills (preferred qualifications/skills)
- Benefits
We must not include Pay or Schedule.
Now we need to ensure we don't include boilerplate.
Let's extract the required qualifications text: "Qualifications ABET-accredited Bachelor’s degree in mechanical, chemical or bioprocess engineering 0 to 3 years of experience in a design firm setting Fundamentals of Engineering exam registration or completion preferred". We'll format as list.
Preferred qualifications and skills: The block after "Preferred Qualifications" includes many items. We'll treat them as skills.
Now benefits: "CRB offers a complete and competitive benefit package designed to meet individual and family needs." We'll put as .
Now ensure we don't include any lines about EEO, etc.
Now produce HTML.
We need to wrap each section:
Heading
then either or
- ...
.
For About the role: we have a few sentences; we can put in .
For Responsibilities: we have list; we can put
.
For Qualifications: list.
For Skills: list.
For Benefits: .
Let's craft.
Check for any duplicate content: The responsibilities list includes some items that also appear in core activities; we must preserve all substantive information, but we can combine similar items to avoid duplication? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we must not omit any detail. If we combine similar items, we might be summarizing. Better to keep each distinct sentence as separate list item, even if similar. However we must avoid duplication of identical lines. The posting has "Core Activities" list that includes:
- Supports the documentation of the process design scope in coordination with other disciplines.
- Works closely with other architects, engineers and designers, as well as other internal and external team members to ensure a coordinated, constructible and complete design.
- Self-checks own work but communicates often with peers and Supervisor.
- Able to work on one or more projects concurrently and manage time effectively.
- Solves complex problems under the direction and supervision of a mentor or supervisor
- Project work may include all levels of design such as studies, conceptual and schematic design, design development, construction documentation and construction administration.
- Works on matters of basic complexity in a support role under the direction of more experienced Process Engineers.
- Engineering deliverables include: Block and Process Flow Diagrams User Requirements Specifications Equipment List Equipment General Arrangements Equipment Datasheets Utility Summary Piping and Instrumentation Diagrams (P&IDs)
Then later in "Job Description" there is also: "The Entry-Level Process Engineer focuses on the design and engineering of manufacturing facility and equipment, supporting facility infrastructure and critical utility systems. Typical tasks include execution of engineering calculations including heat transfer and pressure drop calculations. The Entry-Level Process Engineer is responsible for supporting the documentation of the process design scope in coordination with other disciplines. The Entry-Level Process Engineer may support field installation teams and execute construction site observations. This role is expected to work closely with other architects, engineers and designers, as well as other internal and external team members to ensure a coordinated, constructible and complete design."
So we have overlapping items: supporting documentation, working closely, etc. We should keep all distinct statements; duplication is okay if they appear multiple times? The instruction says remove duplicated lines. So we should not repeat identical lines. If the same sentence appears twice, we should include only once. Let's identify duplicates:
- "Supports the documentation of the process design scope in coordination with other disciplines." appears both in Job Description and Core Activities. Duplicate -> include once.
- "Works closely with
headings, - for any list of duties/requirements/benefits, and
for prose.
We need to decide what is a list vs prose.
We have core activities list: "Supports the documentation of the process design scope in coordination with other disciplines." etc. That's a list of bullet-like sentences. Could be turned into
- .
Similarly engineering deliverables list: list of items.
Qualifications: bullet list? Could be prose but we can make list.
Preferred qualifications: list.
Skills: list.
Benefits: just a sentence, so
.
We must not repeat the job title as a heading. The job title is "Entry-Level Process Engineer". Not to be used as heading.
We must not put Job ID/requisition numbers as headings.
We must output only HTML fragment.
Let's craft.
First, maybe start with
About the role
then a describing role: "The Entry-Level Process Engineer focuses on the design and engineering of manufacturing facility and equipment, supporting facility infrastructure and critical utility systems. Typical tasks include execution of engineering calculations including heat transfer and pressure drop calculations. The Entry-Level Process Engineer is responsible for supporting the documentation of the process design scope in coordination with other disciplines. The Entry-Level Process Engineer may support field installation teams and execute construction site observations. This role is expected to work closely with other architects, engineers and designers, as well as other internal and external team members to ensure a coordinated, constructible and complete design."
Then
Responsibilities
then a with items:
- Supports the documentation of the process design scope in coordination with other disciplines.
- Works closely with other architects, engineers and designers, as well as other internal and external team members to ensure a coordinated, constructible and complete design.
- Self-checks own work but communicates often with peers and Supervisor.
- Able to work on one or more projects concurrently and manage time effectively.
- Solves complex problems under the direction and supervision of a mentor or supervisor.
- Project work may include all levels of design such as studies, conceptual and schematic design, design development, construction documentation and construction administration.
- Works on matters of basic complexity in a support role under the direction of more experienced Process Engineers.
- Engineering deliverables include: Block and Process Flow Diagrams; User Requirements Specifications; Equipment List; Equipment General Arrangements; Equipment Datasheets; Utility Summary; Piping and Instrumentation Diagrams (P&IDs).
We could split engineering deliverables as separate list or include as one item with sublist? Simpler: keep as one item with semicolons.
Then Requirements
then :
- ABET-accredited Bachelor’s degree in mechanical, chemical or bioprocess engineering
- 0 to 3 years of experience in a design firm setting
- Fundamentals of Engineering exam registration or completion preferred
Then Preferred Qualifications
then :
- Fundamental experience with performing engineering calculations, developing and implementing list of discipline systems designs
- Fundamental experience with chemistry/biochemistry
- Fundamental experience with process modeling, material and energy balances and basic sizing calculations
- Fundamental experience with fluid mechanics, hydraulic modeling and fundamental heat transfer
- Strong communication skills and ability to participate in internal cross-discipline project team coordination
- Proficient at fundamental discipline design calculations under the supervision of an engineer
- Proficiency in AutoCAD
- Proficiency in Microsoft Office suite required
- Proficiency in engineering software applications including computer-aided drafting, process modeling and calculation programs
Then Skills
maybe we could combine with Preferred Qualifications? But they asked to use Skills section if there is real specific content. The preferred qualifications already list skills. Could we treat them as Skills? The instruction: Use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we have Qualifications (maybe the required qualifications) and Skills (maybe the preferred qualifications/skills). We already used Requirements for required qualifications. We have Qualifications maybe we could use for the "Qualifications" section (the required). But we already used Requirements. Let's map:
- Requirements: required qualifications (degree, experience, FE exam)
- Qualifications: maybe the "Qualifications" heading in posting (which is same as required). But we can't duplicate. Perhaps we treat "Qualifications" as the required qualifications and "Skills" as the preferred qualifications/skills. However the instruction says we can use those headings; we need to include a section only when posting has real specific content for it. So we need to decide which headings to use.
We have content for:
- About the role (description)
- Responsibilities (duties)
- Requirements (required qualifications)
- Qualifications (maybe same as Requirements? but we could treat as "Qualifications" for the required qualifications and skip Requirements? But we need to avoid duplication. The posting has a section labeled "Qualifications" (required) and then "Preferred Qualifications". So we could use Qualifications
for the required qualifications (degree, experience, FE exam). Then Skills
for the preferred qualifications and skills list. Then we could also have Responsibilities
for duties. And About the role
for overview.
Thus we would not use "Requirements" heading. That's okay; we only include headings with real content.
Thus sections:
- About the role
- Responsibilities
- Qualifications (required)
- Skills (preferred qualifications/skills)
- Benefits
We must not include Pay or Schedule.
Now we need to ensure we don't include boilerplate.
Let's extract the required qualifications text: "Qualifications ABET-accredited Bachelor’s degree in mechanical, chemical or bioprocess engineering 0 to 3 years of experience in a design firm setting Fundamentals of Engineering exam registration or completion preferred". We'll format as list.
Preferred qualifications and skills: The block after "Preferred Qualifications" includes many items. We'll treat them as skills.
Now benefits: "CRB offers a complete and competitive benefit package designed to meet individual and family needs." We'll put as .
Now ensure we don't include any lines about EEO, etc.
Now produce HTML.
We need to wrap each section:
Heading
then either or
- ...
.
For About the role: we have a few sentences; we can put in .
For Responsibilities: we have list; we can put
.
For Qualifications: list.
For Skills: list.
For Benefits: .
Let's craft.
Check for any duplicate content: The responsibilities list includes some items that also appear in core activities; we must preserve all substantive information, but we can combine similar items to avoid duplication? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we must not omit any detail. If we combine similar items, we might be summarizing. Better to keep each distinct sentence as separate list item, even if similar. However we must avoid duplication of identical lines. The posting has "Core Activities" list that includes:
- Supports the documentation of the process design scope in coordination with other disciplines.
- Works closely with other architects, engineers and designers, as well as other internal and external team members to ensure a coordinated, constructible and complete design.
- Self-checks own work but communicates often with peers and Supervisor.
- Able to work on one or more projects concurrently and manage time effectively.
- Solves complex problems under the direction and supervision of a mentor or supervisor
- Project work may include all levels of design such as studies, conceptual and schematic design, design development, construction documentation and construction administration.
- Works on matters of basic complexity in a support role under the direction of more experienced Process Engineers.
- Engineering deliverables include: Block and Process Flow Diagrams User Requirements Specifications Equipment List Equipment General Arrangements Equipment Datasheets Utility Summary Piping and Instrumentation Diagrams (P&IDs)
Then later in "Job Description" there is also: "The Entry-Level Process Engineer focuses on the design and engineering of manufacturing facility and equipment, supporting facility infrastructure and critical utility systems. Typical tasks include execution of engineering calculations including heat transfer and pressure drop calculations. The Entry-Level Process Engineer is responsible for supporting the documentation of the process design scope in coordination with other disciplines. The Entry-Level Process Engineer may support field installation teams and execute construction site observations. This role is expected to work closely with other architects, engineers and designers, as well as other internal and external team members to ensure a coordinated, constructible and complete design."
So we have overlapping items: supporting documentation, working closely, etc. We should keep all distinct statements; duplication is okay if they appear multiple times? The instruction says remove duplicated lines. So we should not repeat identical lines. If the same sentence appears twice, we should include only once. Let's identify duplicates:
- "Supports the documentation of the process design scope in coordination with other disciplines." appears both in Job Description and Core Activities. Duplicate -> include once.
- "Works closely with
for prose. We need to decide what is a list vs prose. We have core activities list: "Supports the documentation of the process design scope in coordination with other disciplines." etc. That's a list of bullet-like sentences. Could be turned into
- .
Similarly engineering deliverables list: list of items.
Qualifications: bullet list? Could be prose but we can make list.
Preferred qualifications: list.
Skills: list.
Benefits: just a sentence, so
. We must not repeat the job title as a heading. The job title is "Entry-Level Process Engineer". Not to be used as heading. We must not put Job ID/requisition numbers as headings. We must output only HTML fragment. Let's craft. First, maybe start with
About the role
then adescribing role: "The Entry-Level Process Engineer focuses on the design and engineering of manufacturing facility and equipment, supporting facility infrastructure and critical utility systems. Typical tasks include execution of engineering calculations including heat transfer and pressure drop calculations. The Entry-Level Process Engineer is responsible for supporting the documentation of the process design scope in coordination with other disciplines. The Entry-Level Process Engineer may support field installation teams and execute construction site observations. This role is expected to work closely with other architects, engineers and designers, as well as other internal and external team members to ensure a coordinated, constructible and complete design." Then
Responsibilities
then a- with items:
- Supports the documentation of the process design scope in coordination with other disciplines.
- Works closely with other architects, engineers and designers, as well as other internal and external team members to ensure a coordinated, constructible and complete design.
- Self-checks own work but communicates often with peers and Supervisor.
- Able to work on one or more projects concurrently and manage time effectively.
- Solves complex problems under the direction and supervision of a mentor or supervisor.
- Project work may include all levels of design such as studies, conceptual and schematic design, design development, construction documentation and construction administration.
- Works on matters of basic complexity in a support role under the direction of more experienced Process Engineers.
- Engineering deliverables include: Block and Process Flow Diagrams; User Requirements Specifications; Equipment List; Equipment General Arrangements; Equipment Datasheets; Utility Summary; Piping and Instrumentation Diagrams (P&IDs).
We could split engineering deliverables as separate list or include as one item with sublist? Simpler: keep as one item with semicolons.
Then
- ...
Requirements
then- :
- ABET-accredited Bachelor’s degree in mechanical, chemical or bioprocess engineering
- 0 to 3 years of experience in a design firm setting
- Fundamentals of Engineering exam registration or completion preferred
Then
Preferred Qualifications
then- :
- Fundamental experience with performing engineering calculations, developing and implementing list of discipline systems designs
- Fundamental experience with chemistry/biochemistry
- Fundamental experience with process modeling, material and energy balances and basic sizing calculations
- Fundamental experience with fluid mechanics, hydraulic modeling and fundamental heat transfer
- Strong communication skills and ability to participate in internal cross-discipline project team coordination
- Proficient at fundamental discipline design calculations under the supervision of an engineer
- Proficiency in AutoCAD
- Proficiency in Microsoft Office suite required
- Proficiency in engineering software applications including computer-aided drafting, process modeling and calculation programs
Then
Skills
maybe we could combine with Preferred Qualifications? But they asked to use Skills section if there is real specific content. The preferred qualifications already list skills. Could we treat them as Skills? The instruction: Use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we have Qualifications (maybe the required qualifications) and Skills (maybe the preferred qualifications/skills). We already used Requirements for required qualifications. We have Qualifications maybe we could use for the "Qualifications" section (the required). But we already used Requirements. Let's map: - Requirements: required qualifications (degree, experience, FE exam) - Qualifications: maybe the "Qualifications" heading in posting (which is same as required). But we can't duplicate. Perhaps we treat "Qualifications" as the required qualifications and "Skills" as the preferred qualifications/skills. However the instruction says we can use those headings; we need to include a section only when posting has real specific content for it. So we need to decide which headings to use. We have content for: - About the role (description) - Responsibilities (duties) - Requirements (required qualifications) - Qualifications (maybe same as Requirements? but we could treat as "Qualifications" for the required qualifications and skip Requirements? But we need to avoid duplication. The posting has a section labeled "Qualifications" (required) and then "Preferred Qualifications". So we could useQualifications
for the required qualifications (degree, experience, FE exam). ThenSkills
for the preferred qualifications and skills list. Then we could also haveResponsibilities
for duties. AndAbout the role
for overview. Thus we would not use "Requirements" heading. That's okay; we only include headings with real content. Thus sections: - About the role - Responsibilities - Qualifications (required) - Skills (preferred qualifications/skills) - Benefits We must not include Pay or Schedule. Now we need to ensure we don't include boilerplate. Let's extract the required qualifications text: "Qualifications ABET-accredited Bachelor’s degree in mechanical, chemical or bioprocess engineering 0 to 3 years of experience in a design firm setting Fundamentals of Engineering exam registration or completion preferred". We'll format as list. Preferred qualifications and skills: The block after "Preferred Qualifications" includes many items. We'll treat them as skills. Now benefits: "CRB offers a complete and competitive benefit package designed to meet individual and family needs." We'll put as. Now ensure we don't include any lines about EEO, etc. Now produce HTML. We need to wrap each section:
Heading
then eitheror
. For Responsibilities: we have list; we can put
- .
For Qualifications: list.
For Skills: list.
For Benefits:
. Let's craft. Check for any duplicate content: The responsibilities list includes some items that also appear in core activities; we must preserve all substantive information, but we can combine similar items to avoid duplication? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we must not omit any detail. If we combine similar items, we might be summarizing. Better to keep each distinct sentence as separate list item, even if similar. However we must avoid duplication of identical lines. The posting has "Core Activities" list that includes: - Supports the documentation of the process design scope in coordination with other disciplines. - Works closely with other architects, engineers and designers, as well as other internal and external team members to ensure a coordinated, constructible and complete design. - Self-checks own work but communicates often with peers and Supervisor. - Able to work on one or more projects concurrently and manage time effectively. - Solves complex problems under the direction and supervision of a mentor or supervisor - Project work may include all levels of design such as studies, conceptual and schematic design, design development, construction documentation and construction administration. - Works on matters of basic complexity in a support role under the direction of more experienced Process Engineers. - Engineering deliverables include: Block and Process Flow Diagrams User Requirements Specifications Equipment List Equipment General Arrangements Equipment Datasheets Utility Summary Piping and Instrumentation Diagrams (P&IDs) Then later in "Job Description" there is also: "The Entry-Level Process Engineer focuses on the design and engineering of manufacturing facility and equipment, supporting facility infrastructure and critical utility systems. Typical tasks include execution of engineering calculations including heat transfer and pressure drop calculations. The Entry-Level Process Engineer is responsible for supporting the documentation of the process design scope in coordination with other disciplines. The Entry-Level Process Engineer may support field installation teams and execute construction site observations. This role is expected to work closely with other architects, engineers and designers, as well as other internal and external team members to ensure a coordinated, constructible and complete design." So we have overlapping items: supporting documentation, working closely, etc. We should keep all distinct statements; duplication is okay if they appear multiple times? The instruction says remove duplicated lines. So we should not repeat identical lines. If the same sentence appears twice, we should include only once. Let's identify duplicates: - "Supports the documentation of the process design scope in coordination with other disciplines." appears both in Job Description and Core Activities. Duplicate -> include once. - "Works closely with