Assistant Project Manager
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 (the page already shows it) and 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 has:
- About Us (company description) – maybe not needed as a heading? Could be "About the role"? Actually "About Us" is company description, not role. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content accordingly.
We have:
- About This Role: description of role responsibilities (some overlap with What You'll Do). Could be "About the role" heading.
- What You'll Do: list of duties – could be "Responsibilities".
- What You'll Bring: qualifications, requirements, skills – could be "Requirements" or "Qualifications" and "Skills". We need to decide.
- What You'll Get: Pay and Benefits – we have Pay range and Benefits list.
We also have some other paragraphs: "Our projects are regulated..." etc. That's boilerplate legal/EEO; we should remove.
We must not include sections with filler like "Schedule" if not present. No schedule info given.
Thus we can have sections:
About the role
– content from "About This Role" paragraph.
Responsibilities
– list from "What You'll Do" (bullet list).
Requirements
– maybe combine "What You'll Bring" bullet points (education, experience, knowledge, skills, abilities). Could split into Requirements and Skills but we prefer few substantive sections. Could make one "Requirements" section containing all.
Benefits
– list benefits.
Pay
– pay range.
We must not include Schedule.
We need to use - for any list of duties/requirements/benefits. For prose, use
.
Thus:
- About the role: prose paragraph.
- Responsibilities:
- each duty.
- Requirements: maybe a mix of prose and list? The "What You'll Bring" includes bullet-like sentences but not explicitly bullet list. We can convert each sentence into
- . That would be a list.
- Benefits: list.
- Pay: maybe a
with the range.
We must preserve all substantive information. Let's extract.
About Us paragraph: "PAR Western Line Contractors, LLC (dba QUES), a subsidiary of Quanta Services, Inc. (NYSE: PWR), is composed of some of the most highly qualified professionals experienced in all aspects of engineering, designing, asset management, and construction management for the electric utility and other industries. We are a highly mobile and flexible team with the ability to service every area and region within our customers’ area of operation. With over 700 employees and growing, we have thousands of years of combined electrical utility experience to draw from when committing to provide our clients with a wide range of utility services."
Is this substantive? It's about the company. The instruction says we can include sections only when posting has real specific content for it. There's no heading like "About the company" in allowed headings, but we could incorporate into "About the role"? Probably not needed. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not add a heading for About Us. We could incorporate that info into About the role paragraph? But that would be mixing company description with role description. Might be okay to keep as a brief
before the headings? The instruction says output ONLY the HTML fragment, no extra headings not allowed? It didn't forbid extra paragraphs not under headings, but we should follow the pattern: use headings for sections. Could have a leading
for company overview, but not required. Safer to include it as part of About the role? Might be considered filler? It's substantive but not role-specific. However the instruction says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid having a
outside sections. But to be safe, we can include a brief
for company overview before the headings, as it's substantive and not a heading. The instruction didn't prohibit that. However they said "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It didn't say you cannot have other elements. I'd include a short
for company overview.
Now extract About This Role paragraph:
"The Assistant Project Manager will work with the Project Manager to provide general administrative, technical, financial, and resource management support for their assigned projects from initial bid preparation through project close-out. The employee will be responsible for project data collection, entry, and management within the relevant corporate information systems which will deserve a high attention to detail and thoroughness. In this role, it will be essential to learn how the business runs, how changing circumstances are handled, and who to contact when there are questions. Critical for success are excellent oral and verbal communication skills, and the ability to work in teams."
We'll put that as
under
About the role
.
Now Responsibilities: list from "What You'll Do". Let's extract each bullet:
- Work with safety personnel to ensure that project is being built in accordance with OSHA and company regulations and that proper training is occurring
- Setup, organize, update, and maintain electronic and printed files of project documents utilizing various systems, including Microsoft Word, Excel, Project, and Sharepoint; Primavera P6; EcoSys; Quickbase; InEight; Procore; and others
- Define problems, gather information, and recommend appropriate resolutions
- Support pre-construction efforts, including bid preparation, contract and exhibit review, and execution planning
- Build and maintain relationships with clients, suppliers, and subcontractors; schedule and manage subcontractors, vendors, and material suppliers
- Monitor construction with the superintendent to keep the project on schedule and within budget, and review cost reports to identify ways to reduce cost while maintaining productivity
- Manage budget projections, cost forecasting, and productivity for labor, material, equipment, and subcontractors, including daily, weekly, and monthly progress reporting and cost-to-complete accuracy
- Oversee invoicing and payment applications and monitor the quality of labor, equipment, material, and subcontractor reporting for assigned projects
- Lead and document project meetings (agendas and minutes) daily, weekly, and monthly as required
- Develop, negotiate, submit, and track client and/or subcontractor change orders
- Assume additional responsibilities as directed by division or project management
We'll make each a - .
Now Requirements: from "What You'll Bring". Let's parse sentences:
- 2 Year’s Construction Science, Project Management, Construction Management, Construction Engineering, Engineering, or similar related Degree OR Equivalent combinations of technical training and/or related experience
- Entry level knowledge of all aspects of project management, project controls, contract management, budgeting, estimating, schedules, and safety required
- Must be able to maintain a professional appearance and work well under pressure to meet deadlines
- Knowledge of project management, project controls, estimating, construction, finance, and contract management, with an understanding of corporate and industry practices, processes, and standards
- Ability to learn and apply accounting revenue recognition concepts and operations as needed to examine construction operations
- Proficient in Microsoft Office (Word, Excel, Access, Outlook, Visio, Sharepoint); familiar with or ready to learn Primavera P6, JD Edwards, Hubble, EcoSys, Quickbase, and InEight
- Effective communication skills (oral, written, presentation, listening) and the ability to organize and prioritize numerous tasks
- Ability to travel and work on project location, as required, with a valid driver's license and acceptable motor vehicle driving record (MVR)
- Ability to read, analyze, and interpret technical specifications, financial reports, and legal documents
We could make each a
- . Some are long but okay.
Now Benefits: from "What You'll Get": "Benefits include-- Medical, Dental, Vision, 401K". Also maybe other benefits? That's it.
We'll make a
- Medical
- Dental
- Vision
- 401K
.
Pay: "Pay- $90,000 - $115,000 /Annually *Depending on Experience". We'll output as Pay: $90,000 - $115,000 annually (depending on experience). Keep the info.
We should also maybe include note about criminal background checks etc? That's boilerplate legal; remove.
Now ensure we don't repeat job title as heading. We didn't.
Now produce HTML fragment:
PAR Western Line Contractors, LLC (dba QUES), a subsidiary of Quanta Services, Inc. (NYSE: PWR), is composed of some of the most highly qualified professionals experienced in all aspects of engineering, designing, asset management, and construction management for the electric utility and other industries. We are a highly mobile and flexible team with the ability to service every area and region within our customers’ area of operation. With over 700 employees and growing, we have thousands of years of combined electrical utility experience to draw from when committing to provide our clients with a wide range of utility services.
About the role
The Assistant Project Manager will work with the Project Manager to provide general administrative, technical, financial, and resource management support for their assigned projects from initial bid preparation through project close-out. The employee will be responsible for project data collection, entry, and management within the relevant corporate information systems which will deserve a high attention to detail and thoroughness. In this role, it will be essential to learn how the business runs, how changing circumstances are handled, and who to contact when there are questions. Critical for success are excellent oral and verbal communication skills, and the ability to work in teams.
Responsibilities
- Work with safety personnel to ensure that project is being built in accordance with OSHA and company regulations and that proper training is occurring
- Setup, organize, update, and maintain electronic and printed files of project documents utilizing various systems, including Microsoft Word, Excel, Project, and Sharepoint; Primavera P6; EcoSys; Quickbase; InEight; Procore; and others
- Define problems, gather information, and recommend appropriate resolutions
- Support pre-construction efforts, including bid preparation, contract and exhibit review, and execution planning
- Build and maintain relationships with clients, suppliers, and subcontractors; schedule and manage subcontractors, vendors, and material suppliers
- Monitor construction with the superintendent
for prose. 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. 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 has: - About Us (company description) – maybe not needed as a heading? Could be "About the role"? Actually "About Us" is company description, not role. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content accordingly. We have: - About This Role: description of role responsibilities (some overlap with What You'll Do). Could be "About the role" heading. - What You'll Do: list of duties – could be "Responsibilities". - What You'll Bring: qualifications, requirements, skills – could be "Requirements" or "Qualifications" and "Skills". We need to decide. - What You'll Get: Pay and Benefits – we have Pay range and Benefits list. We also have some other paragraphs: "Our projects are regulated..." etc. That's boilerplate legal/EEO; we should remove. We must not include sections with filler like "Schedule" if not present. No schedule info given. Thus we can have sections:
About the role
– content from "About This Role" paragraph.Responsibilities
– list from "What You'll Do" (bullet list).Requirements
– maybe combine "What You'll Bring" bullet points (education, experience, knowledge, skills, abilities). Could split into Requirements and Skills but we prefer few substantive sections. Could make one "Requirements" section containing all.Benefits
– list benefits.Pay
– pay range. We must not include Schedule. We need to use- for any list of duties/requirements/benefits. For prose, use
. Thus: - About the role: prose paragraph. - Responsibilities:
- each duty. - Requirements: maybe a mix of prose and list? The "What You'll Bring" includes bullet-like sentences but not explicitly bullet list. We can convert each sentence into
- . That would be a list.
- Benefits: list.
- Pay: maybe a
with the range. We must preserve all substantive information. Let's extract. About Us paragraph: "PAR Western Line Contractors, LLC (dba QUES), a subsidiary of Quanta Services, Inc. (NYSE: PWR), is composed of some of the most highly qualified professionals experienced in all aspects of engineering, designing, asset management, and construction management for the electric utility and other industries. We are a highly mobile and flexible team with the ability to service every area and region within our customers’ area of operation. With over 700 employees and growing, we have thousands of years of combined electrical utility experience to draw from when committing to provide our clients with a wide range of utility services." Is this substantive? It's about the company. The instruction says we can include sections only when posting has real specific content for it. There's no heading like "About the company" in allowed headings, but we could incorporate into "About the role"? Probably not needed. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not add a heading for About Us. We could incorporate that info into About the role paragraph? But that would be mixing company description with role description. Might be okay to keep as a brief
before the headings? The instruction says output ONLY the HTML fragment, no extra headings not allowed? It didn't forbid extra paragraphs not under headings, but we should follow the pattern: use headings for sections. Could have a leading
for company overview, but not required. Safer to include it as part of About the role? Might be considered filler? It's substantive but not role-specific. However the instruction says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid having a
outside sections. But to be safe, we can include a brief
for company overview before the headings, as it's substantive and not a heading. The instruction didn't prohibit that. However they said "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It didn't say you cannot have other elements. I'd include a short
for company overview. Now extract About This Role paragraph: "The Assistant Project Manager will work with the Project Manager to provide general administrative, technical, financial, and resource management support for their assigned projects from initial bid preparation through project close-out. The employee will be responsible for project data collection, entry, and management within the relevant corporate information systems which will deserve a high attention to detail and thoroughness. In this role, it will be essential to learn how the business runs, how changing circumstances are handled, and who to contact when there are questions. Critical for success are excellent oral and verbal communication skills, and the ability to work in teams." We'll put that as
under
About the role
. Now Responsibilities: list from "What You'll Do". Let's extract each bullet: - Work with safety personnel to ensure that project is being built in accordance with OSHA and company regulations and that proper training is occurring - Setup, organize, update, and maintain electronic and printed files of project documents utilizing various systems, including Microsoft Word, Excel, Project, and Sharepoint; Primavera P6; EcoSys; Quickbase; InEight; Procore; and others - Define problems, gather information, and recommend appropriate resolutions - Support pre-construction efforts, including bid preparation, contract and exhibit review, and execution planning - Build and maintain relationships with clients, suppliers, and subcontractors; schedule and manage subcontractors, vendors, and material suppliers - Monitor construction with the superintendent to keep the project on schedule and within budget, and review cost reports to identify ways to reduce cost while maintaining productivity - Manage budget projections, cost forecasting, and productivity for labor, material, equipment, and subcontractors, including daily, weekly, and monthly progress reporting and cost-to-complete accuracy - Oversee invoicing and payment applications and monitor the quality of labor, equipment, material, and subcontractor reporting for assigned projects - Lead and document project meetings (agendas and minutes) daily, weekly, and monthly as required - Develop, negotiate, submit, and track client and/or subcontractor change orders - Assume additional responsibilities as directed by division or project management We'll make each a - . Now Requirements: from "What You'll Bring". Let's parse sentences: - 2 Year’s Construction Science, Project Management, Construction Management, Construction Engineering, Engineering, or similar related Degree OR Equivalent combinations of technical training and/or related experience - Entry level knowledge of all aspects of project management, project controls, contract management, budgeting, estimating, schedules, and safety required - Must be able to maintain a professional appearance and work well under pressure to meet deadlines - Knowledge of project management, project controls, estimating, construction, finance, and contract management, with an understanding of corporate and industry practices, processes, and standards - Ability to learn and apply accounting revenue recognition concepts and operations as needed to examine construction operations - Proficient in Microsoft Office (Word, Excel, Access, Outlook, Visio, Sharepoint); familiar with or ready to learn Primavera P6, JD Edwards, Hubble, EcoSys, Quickbase, and InEight - Effective communication skills (oral, written, presentation, listening) and the ability to organize and prioritize numerous tasks - Ability to travel and work on project location, as required, with a valid driver's license and acceptable motor vehicle driving record (MVR) - Ability to read, analyze, and interpret technical specifications, financial reports, and legal documents We could make each a
- . Some are long but okay.
Now Benefits: from "What You'll Get": "Benefits include-- Medical, Dental, Vision, 401K". Also maybe other benefits? That's it.
We'll make a
- Medical
- Dental
- Vision
- 401K . Pay: "Pay- $90,000 - $115,000 /Annually *Depending on Experience". We'll output as
- Work with safety personnel to ensure that project is being built in accordance with OSHA and company regulations and that proper training is occurring
- Setup, organize, update, and maintain electronic and printed files of project documents utilizing various systems, including Microsoft Word, Excel, Project, and Sharepoint; Primavera P6; EcoSys; Quickbase; InEight; Procore; and others
- Define problems, gather information, and recommend appropriate resolutions
- Support pre-construction efforts, including bid preparation, contract and exhibit review, and execution planning
- Build and maintain relationships with clients, suppliers, and subcontractors; schedule and manage subcontractors, vendors, and material suppliers
- Monitor construction with the superintendent
Pay: $90,000 - $115,000 annually (depending on experience). Keep the info. We should also maybe include note about criminal background checks etc? That's boilerplate legal; remove. Now ensure we don't repeat job title as heading. We didn't. Now produce HTML fragment:
PAR Western Line Contractors, LLC (dba QUES), a subsidiary of Quanta Services, Inc. (NYSE: PWR), is composed of some of the most highly qualified professionals experienced in all aspects of engineering, designing, asset management, and construction management for the electric utility and other industries. We are a highly mobile and flexible team with the ability to service every area and region within our customers’ area of operation. With over 700 employees and growing, we have thousands of years of combined electrical utility experience to draw from when committing to provide our clients with a wide range of utility services.
About the role
The Assistant Project Manager will work with the Project Manager to provide general administrative, technical, financial, and resource management support for their assigned projects from initial bid preparation through project close-out. The employee will be responsible for project data collection, entry, and management within the relevant corporate information systems which will deserve a high attention to detail and thoroughness. In this role, it will be essential to learn how the business runs, how changing circumstances are handled, and who to contact when there are questions. Critical for success are excellent oral and verbal communication skills, and the ability to work in teams.
Responsibilities