Project Engineer
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only use those headings if content exists. "About Us" is not in list, but we could maybe treat as "About the role"? However the posting includes "About Us" paragraph describing company. The instruction says do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. It doesn't forbid other headings not in list, but says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect we only use those headings. So we need to map content to those headings. We have: - About Us: company description. Could be placed under "About the role"? Not exactly. Maybe we can omit "About Us" as it's not required? But we must preserve ALL substantive information. So we need to include that info somewhere. Could put it in a
without heading? 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 say we cannot have other headings, but suggests we should use those headings for sections. Probably we can include an "About Us" section with
About Us
even though not in list, but they gave examples. Safer to follow instruction: use those headings only. But we need to include company description. Could place it under "About the role" heading? That seems odd but maybe acceptable. However "About the role" would be about the role, not company. The posting has "Job Overview:" which describes role. So we can put that under "About the role". The "About Us" could be considered company overview, maybe we can put under "About the role" as well? Might be mixing.
Better: Use headings: About the role (Job Overview), Responsibilities (Key Responsibilities and Essential Tasks), Qualifications (Qualifications Knowledge, Skills and Abilities), Benefits (What's in it for You? list), Pay (Compensation), Schedule (Work environment? maybe not schedule). Also we have "Work environment" details; could be placed under "Schedule"? Not exactly. There's no explicit schedule. Could omit Schedule if no specific schedule info. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. We have Pay (Compensation) stated: "Rex Moore pays hourly/salary rates commensurate with each employee’s knowledge, experience and skill level." That's vague but still mentions compensation. It's not a specific number, but it's still stating compensation. The instruction says 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. The phrase "commensurate with each employee’s knowledge, experience and skill level." is essentially "commensurate with experience" which is filler. So we should NOT create a Pay section because it's just filler. So we omit Pay.
Benefits: we have a list of benefits under "What's in it for You?" with specific items: Health Benefits, 401(k) with Company Match, Life and Disability Benefits, Paid Holidays & Paid time off, Access to multiple types of training, Opportunities for Self-development and Career Progression, Wellness Benefits & Employee Assistance Program, Family Leave (Maternity, Paternity), Tuition Reimbursement Program, Apprenticeship Program. Those are specific. So we can create Benefits section with - .
Schedule: we have work environment details but not schedule (hours). No explicit schedule. So we omit Schedule.
Qualifications: we have "Qualifications Knowledge, Skills and Abilities" with bullet-like sentences. We'll put under
Qualifications
and use - for each.
Responsibilities: we have "Key Responsibilities and Essential Tasks" with many sentences. We'll put under
Responsibilities
and - .
About the role: we have "Job Overview:" paragraph. We'll put under
About the role
as .
Also we have "About Us" company description. Could we incorporate that into About the role? Might be okay to add another
after the job overview under same heading? Or we could create a separate
About the company
but not in list. Safer to include as a under About the role? 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 gave examples. I'd include About Us as a
without heading, maybe preceding the About the role? But we need to preserve all substantive info. Let's put it as a
before the About the role heading? Could be weird.
Better: Add a
About the company
but not in examples. Might be considered violating instruction to only use those headings? The instruction says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say "only these", but implies these are typical. I'd stick to those headings and put company description in a
under About the role heading (maybe as a second paragraph). That preserves info.
Now we need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We see at end: "EOE Qualifications Knowledge, Skills and Abilities (previously named Qualifications):" Actually there is "EOE" before Qualifications. That's EEO boilerplate; we should drop "EOE". Also "PM22" at end maybe job ID; drop.
Also "Reporting Structure: Reports to – Project Executive/ Area Manager Department – Construction Services" is metadata; we can fold into a short
or drop. Probably drop as minor metadata.
Also "Work environment: Project Engineers typically work in an office environment, although they may occasionally visit worksites to observe a project or to meet with clients. When on worksites Project Engineers is to wear personal protective equipment (PPE), always including a hard hat, safety glasses, gloves, work boots and high viz vest/ shirt. Working around energized equipment. This role requires working in all elements, depending on job location, time of year, heat, cold, rain & snow." This is substantive about work environment; we could include under Responsibilities? Or maybe under a new section like "Working Conditions" but not in list. Could incorporate into Responsibilities as a bullet? Might be okay to add a
under Responsibilities? But we already have a list. Could add a
after the list under same heading? The instruction: Use
- for any list of duties/requirements/benefits, and
for prose. So we can have both
and under same heading. So we can keep Responsibilities heading, then
for the list of duties, then a for work environment prose.
Similarly, we have "Physical Requirements:" list; that could be under Qualifications? Or maybe under Requirements? There's no Requirements heading in examples but we could use Requirements for physical requirements. The examples include Requirements. So we can create a
Requirements
for physical requirements. That seems appropriate.
Thus sections:
- About the role: includes company description (About Us) and Job Overview.
- Responsibilities: list of duties + work environment prose.
- Requirements: physical requirements.
- Qualifications: knowledge, skills, abilities.
- Benefits: list.
We must not include Pay or Schedule.
Now we need to format.
Let's extract content.
About Us paragraph:
"About Us: Rex Moore continues to be powered by amazing employees just like you for over 100 years. Together we are building a world that is safe, comfortable, and sustainable. Our diverse team of experts spreading to National territories create innovative, integrated solutions to make cities more connected, buildings more intelligent and environments more comfortable and secure. Watch Our Story: About Rex Moore Group, Inc. - YouTube"
We should drop the "Watch Our Story: About Rex Moore Group, Inc. - YouTube" as it's a link/promo; maybe considered boilerplate? It's not legal but it's promotional. Might be considered navigation? Not sure. Safer to keep? It's not essential info about company; it's a call to watch video. Could be considered boilerplate. I'd drop it.
Job Overview paragraph:
"Job Overview: The Project Engineer will be responsible for managing all submittals, RFIs, Change Orders, Work Breakdown Structure and Material Kits for multiple projects. The ideal candidate must be able to work effectively in a multi-faceted and extremely fast paced team environment."
We'll keep that.
Now Responsibilities list (Key Responsibilities and Essential Tasks). Let's extract each sentence as bullet.
List:
- Respond to internal customer needs and resolve their issues in a timely manner
- Works closely with external customers Project Engineer and/or Assistant Project Managers
- Schedule and participate in project meetings (start-up, weekly, close-out)
- Take notes and capture action items during project meetings
- Prepare, maintain, and process RFI’s, Submittals and close-out documents
- Create and maintain Project Logs (Change Requests, Submittals, RFIs) - Sending weekly updates to customer for discussion
- Assist Project Managers and Project Executives in project duties
- Process material, rental equipment and tool orders
- Perform material takeoffs, with assistance, for Change Orders Request processing
- Prepare and coordinate delivery of site mobilization documentation
- Input and manage project scheduling functions, WBS and SIS, 10-5-2-1
- Collaborate with CI for material kit deliveries and backorders
- Maintain Construction Documents in Plan Grid and distribute to internal/external parties
- Perform all duties as outlined on the published Roles and Responsibilities Matrix
We need to ensure no duplication. Some sentences have extra punctuation; we'll keep as is.
Now Work environment prose:
"Work environment: Project Engineers typically work in an office environment, although they may occasionally visit worksites to observe a project or to meet with clients. When on worksites Project Engineers is to wear personal protective equipment (PPE), always including a hard hat, safety glasses, gloves, work boots and high viz vest/ shirt. Working around energized equipment. This role requires working in all elements, depending on job location, time of year, heat, cold, rain & snow."
We'll make a after the list.
Now Requirements (physical requirements). Extract:
"Physical Requirements: Ability to verbally communicate: convey detailed and accurate instructions and information.
Ability to hear with or without correction in order to receive and interpret detailed information.
Required to sit at a desk work station for long periods of time.
Push, pull, lift, and carry at least 10 pounds.
Frequently required to walk and stand. This position may involve infrequent site visits which will require the ability to walk on uneven surfaces, climb stairs and wear appropriate personal protective equipment.
Required to have visual acuity with or without correction in order to read contract documents, analyze data, view a computer monitor, and proof-read documents to identify errors.
Required to use
for prose. It doesn't say we cannot have other headings, but suggests we should use those headings for sections. Probably we can include an "About Us" section with
About Us
even though not in list, but they gave examples. Safer to follow instruction: use those headings only. But we need to include company description. Could place it under "About the role" heading? That seems odd but maybe acceptable. However "About the role" would be about the role, not company. The posting has "Job Overview:" which describes role. So we can put that under "About the role". The "About Us" could be considered company overview, maybe we can put under "About the role" as well? Might be mixing. Better: Use headings: About the role (Job Overview), Responsibilities (Key Responsibilities and Essential Tasks), Qualifications (Qualifications Knowledge, Skills and Abilities), Benefits (What's in it for You? list), Pay (Compensation), Schedule (Work environment? maybe not schedule). Also we have "Work environment" details; could be placed under "Schedule"? Not exactly. There's no explicit schedule. Could omit Schedule if no specific schedule info. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. We have Pay (Compensation) stated: "Rex Moore pays hourly/salary rates commensurate with each employee’s knowledge, experience and skill level." That's vague but still mentions compensation. It's not a specific number, but it's still stating compensation. The instruction says 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. The phrase "commensurate with each employee’s knowledge, experience and skill level." is essentially "commensurate with experience" which is filler. So we should NOT create a Pay section because it's just filler. So we omit Pay. Benefits: we have a list of benefits under "What's in it for You?" with specific items: Health Benefits, 401(k) with Company Match, Life and Disability Benefits, Paid Holidays & Paid time off, Access to multiple types of training, Opportunities for Self-development and Career Progression, Wellness Benefits & Employee Assistance Program, Family Leave (Maternity, Paternity), Tuition Reimbursement Program, Apprenticeship Program. Those are specific. So we can create Benefits section with- .
Schedule: we have work environment details but not schedule (hours). No explicit schedule. So we omit Schedule.
Qualifications: we have "Qualifications Knowledge, Skills and Abilities" with bullet-like sentences. We'll put under
Qualifications
and use- for each.
Responsibilities: we have "Key Responsibilities and Essential Tasks" with many sentences. We'll put under
Responsibilities
and- .
About the role: we have "Job Overview:" paragraph. We'll put under
About the role
as. Also we have "About Us" company description. Could we incorporate that into About the role? Might be okay to add another
after the job overview under same heading? Or we could create a separate
About the company
but not in list. Safer to include as aunder About the role? 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 gave examples. I'd include About Us as a
without heading, maybe preceding the About the role? But we need to preserve all substantive info. Let's put it as a
before the About the role heading? Could be weird. Better: Add a
About the company
but not in examples. Might be considered violating instruction to only use those headings? The instruction says "Usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say "only these", but implies these are typical. I'd stick to those headings and put company description in a
under About the role heading (maybe as a second paragraph). That preserves info. Now we need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We see at end: "EOE Qualifications Knowledge, Skills and Abilities (previously named Qualifications):" Actually there is "EOE" before Qualifications. That's EEO boilerplate; we should drop "EOE". Also "PM22" at end maybe job ID; drop. Also "Reporting Structure: Reports to – Project Executive/ Area Manager Department – Construction Services" is metadata; we can fold into a short
or drop. Probably drop as minor metadata. Also "Work environment: Project Engineers typically work in an office environment, although they may occasionally visit worksites to observe a project or to meet with clients. When on worksites Project Engineers is to wear personal protective equipment (PPE), always including a hard hat, safety glasses, gloves, work boots and high viz vest/ shirt. Working around energized equipment. This role requires working in all elements, depending on job location, time of year, heat, cold, rain & snow." This is substantive about work environment; we could include under Responsibilities? Or maybe under a new section like "Working Conditions" but not in list. Could incorporate into Responsibilities as a bullet? Might be okay to add a
under Responsibilities? But we already have a list. Could add a
after the list under same heading? The instruction: Use
- for any list of duties/requirements/benefits, and
for prose. So we can have both
- and
under same heading. So we can keep Responsibilities heading, then
- for the list of duties, then a
for work environment prose. Similarly, we have "Physical Requirements:" list; that could be under Qualifications? Or maybe under Requirements? There's no Requirements heading in examples but we could use Requirements for physical requirements. The examples include Requirements. So we can create a
Requirements
for physical requirements. That seems appropriate. Thus sections: - About the role: includes company description (About Us) and Job Overview. - Responsibilities: list of duties + work environment prose. - Requirements: physical requirements. - Qualifications: knowledge, skills, abilities. - Benefits: list. We must not include Pay or Schedule. Now we need to format. Let's extract content. About Us paragraph: "About Us: Rex Moore continues to be powered by amazing employees just like you for over 100 years. Together we are building a world that is safe, comfortable, and sustainable. Our diverse team of experts spreading to National territories create innovative, integrated solutions to make cities more connected, buildings more intelligent and environments more comfortable and secure. Watch Our Story: About Rex Moore Group, Inc. - YouTube" We should drop the "Watch Our Story: About Rex Moore Group, Inc. - YouTube" as it's a link/promo; maybe considered boilerplate? It's not legal but it's promotional. Might be considered navigation? Not sure. Safer to keep? It's not essential info about company; it's a call to watch video. Could be considered boilerplate. I'd drop it. Job Overview paragraph: "Job Overview: The Project Engineer will be responsible for managing all submittals, RFIs, Change Orders, Work Breakdown Structure and Material Kits for multiple projects. The ideal candidate must be able to work effectively in a multi-faceted and extremely fast paced team environment." We'll keep that. Now Responsibilities list (Key Responsibilities and Essential Tasks). Let's extract each sentence as bullet. List: - Respond to internal customer needs and resolve their issues in a timely manner - Works closely with external customers Project Engineer and/or Assistant Project Managers - Schedule and participate in project meetings (start-up, weekly, close-out) - Take notes and capture action items during project meetings - Prepare, maintain, and process RFI’s, Submittals and close-out documents - Create and maintain Project Logs (Change Requests, Submittals, RFIs) - Sending weekly updates to customer for discussion - Assist Project Managers and Project Executives in project duties - Process material, rental equipment and tool orders - Perform material takeoffs, with assistance, for Change Orders Request processing - Prepare and coordinate delivery of site mobilization documentation - Input and manage project scheduling functions, WBS and SIS, 10-5-2-1 - Collaborate with CI for material kit deliveries and backorders - Maintain Construction Documents in Plan Grid and distribute to internal/external parties - Perform all duties as outlined on the published Roles and Responsibilities Matrix We need to ensure no duplication. Some sentences have extra punctuation; we'll keep as is. Now Work environment prose: "Work environment: Project Engineers typically work in an office environment, although they may occasionally visit worksites to observe a project or to meet with clients. When on worksites Project Engineers is to wear personal protective equipment (PPE), always including a hard hat, safety glasses, gloves, work boots and high viz vest/ shirt. Working around energized equipment. This role requires working in all elements, depending on job location, time of year, heat, cold, rain & snow." We'll make aafter the list. Now Requirements (physical requirements). Extract: "Physical Requirements: Ability to verbally communicate: convey detailed and accurate instructions and information. Ability to hear with or without correction in order to receive and interpret detailed information. Required to sit at a desk work station for long periods of time. Push, pull, lift, and carry at least 10 pounds. Frequently required to walk and stand. This position may involve infrequent site visits which will require the ability to walk on uneven surfaces, climb stairs and wear appropriate personal protective equipment. Required to have visual acuity with or without correction in order to read contract documents, analyze data, view a computer monitor, and proof-read documents to identify errors. Required to use
- for any list of duties/requirements/benefits, and
- .
About the role: we have "Job Overview:" paragraph. We'll put under
- for each.
Responsibilities: we have "Key Responsibilities and Essential Tasks" with many sentences. We'll put under