Roofing Project Manager
CentiMark Corporation · Monroe, NC · 2 days ago
Information Technology$60k/yrFull-time
We need to output HTML fragment with sections only if real content. Use for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content: job summary (About the role), responsibilities list, qualifications list, skills list, benefits list, pay info ($60k plus annual bonus). No schedule info (no mention of schedule beyond Dayshift Hours maybe? Actually "Dayshift Hours" is listed under Premier Benefits? It appears as part of benefits list: "Dayshift Hours". That's schedule info? It's a schedule detail: dayshift hours. Could be considered schedule. The instruction: include Schedule section only if posting actually states them. It does mention Dayshift Hours. So we can include Schedule section with that detail.
We must not repeat job title as heading. No Job ID. Remove boilerplate: video link, EEO, etc. Also remove "WHY WORK FOR CENTIMARK?" etc. Keep substantive info.
We need to preserve all substantive info: job summary paragraph, responsibilities bullet list, qualifications bullet list, skills bullet list (maybe overlapping with qualifications). The posting includes "Candidate Qualifications" with bullet-like lines. Also "Proficiency in construction estimating software..." etc. Also "Bilingual skills preferred". Also "Premier Benefits" list. Also "Pay: $60k, plus annual bonus opportunity". Also "Dayshift Hours". Also maybe "Growth Opportunities" paragraph about company size; that's substantive but maybe not a specific section; could go under About the role? Might be considered company overview; we could include as part of About the role or maybe a separate section? Not required headings; we can put in About the role paragraph.
We must not invent or summarize away detail. Keep all details.
Let's extract:
About the role: "CentiMark Corporation, the national leader in the commercial roofing industry, has an exceptional opportunity for an experienced Roofing Project Manager in Monroe, NC. This role is paying $60k, plus annual bonus opportunity and premier benefits! Job Summary: The Roofing Project Manager is customer facing, being responsible for the flow of data, communication and documentation between CentiMark, the customer and stakeholders throughout all project phases. This position will engage primarily with New Construction projects being facilitated through General Contractors."
But we have Pay separate; we might not repeat pay in About the role. However the instruction: do not repeat job title as heading; we can keep the summary but maybe we should separate pay into Pay section. The About the role can include the job summary without pay. But we must preserve all substantive info; we can keep the pay info in Pay section and not duplicate. However the About the role currently includes "This role is paying $60k, plus annual bonus opportunity and premier benefits!" That's pay and benefits. We could split: keep the sentence about role being opportunity, but maybe we should move pay and benefits to respective sections. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. If we remove that sentence from About the role, we lose that info unless we put it elsewhere. We'll put pay in Pay section and benefits in Benefits section. So About the role will have the rest: "CentiMark Corporation, the national leader in the commercial roofing industry, has an exceptional opportunity for an experienced Roofing Project Manager in Monroe, NC. Job Summary: The Roofing Project Manager is customer facing, being responsible for the flow of data, communication and documentation between CentiMark, the customer and stakeholders throughout all project phases. This position will engage primarily with New Construction projects being facilitated through General Contractors."
That seems fine.
Responsibilities: list from "Generating project submittal packages" through "Provide support to the construction manager". Let's capture each line:
- Generating project submittal packages
- Pre-registering manufacturer’s warranties
- Change order management
- Produce & maintain schedule of values
- Maintain daily logs; generate progress reports
- Attend on-site meetings, take meeting minutes, perform quality control Inspections
- Navigate and resolve construction related issues, disputes and disagreements
- Maintain client project portals & act as primary POC throughout project phases
- Collaborate w/managers to fulfill data requests and answer technical questions
- Monitor project spend and assist in staying on budget
- Provide support to the construction manager
We need to keep punctuation as is.
Requirements: maybe "Experience coordinating large scale construction projects - Preferred Roofing related experience - Preferred". That's a bit weird. We'll treat as requirements.
Qualifications: maybe same as requirements? Actually the posting has "Candidate Qualifications" then bullet lines. We'll treat that as Qualifications.
Skills: maybe "Proficiency in construction estimating software (STACK, BIM 360, Procore)", "Thorough knowledge of construction practices and project flow", "Exceptional organizational & coordination skills", "Strong communication and interpersonal skills", "Competency in standard business applications: MS Office Suite, Cloud Apps, Acrobat", "Ability to read and translate construction plans, specifications and contracts", "Bilingual skills preferred". Those could be Skills.
But we have overlapping; we can separate: Requirements: Experience coordinating large scale construction projects; Preferred Roofing related experience. Qualifications: maybe same as skills? However we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We'll assign content accordingly.
Let's map:
- About the role: as above.
- Responsibilities: the list of duties.
- Requirements: "Experience coordinating large scale construction projects - Preferred Roofing related experience - Preferred". Actually the line: "Experience coordinating large scale construction projects - Preferred Roofing related experience - Preferred". Might be two bullet points: Experience coordinating large scale construction projects (Preferred), Roofing related experience (Preferred). We'll output as list items.
- Qualifications: maybe "Proficiency in construction estimating software (STACK, BIM 360, Procore)", "Thorough knowledge of construction practices and project flow", "Exceptional organizational & coordination skills", "Strong communication and interpersonal skills", "Competency in standard business applications: MS Office Suite, Cloud Apps, Acrobat", "Ability to read and translate construction plans, specifications and contracts", "Bilingual skills preferred". But some of those are skills. However we have separate Skills heading; we could put those under Skills. Qualifications could be something else? The posting only has "Candidate Qualifications" then those bullet lines. So we could treat that as Qualifications. Then Skills maybe we could leave empty or not include. But we need to only include sections with real content. If we put all those under Qualifications, we can omit Skills. However the instruction says prefer a few substantive sections over many thin ones. So we could combine Qualifications and Skills into one section? But we must follow allowed headings; we can omit Skills if no distinct content. Let's put all those bullet lines under Qualifications.
- Benefits: list from Premier Benefits.
- Pay: "$60k, plus annual bonus opportunity".
- Schedule: "Dayshift Hours". Possibly also mention that it's day shift. We'll put that.
Now ensure we don't include boilerplate: remove "WHY WORK FOR CENTIMARK? >>>> CLICK HERE TO WATCH VIDEO!", "CentiMark Corporation is North America’s largest commercial roofing contractor..." that's company overview maybe substantive but not under a heading; we could include in About the role as extra sentence. It's substantive about company size; we can add to About the role after job summary. It's not boilerplate; it's info about company. We'll keep.
Also remove "Drug Free Workplace - EOE (M/F/V/D) - E-Verify Employer For more information, please visit our website -- www.CentiMark.com/jobs". That's boilerplate/legal; remove.
Now craft HTML.
We'll open with maybe not needed; just output headings and content.
Structure:
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content: job summary (About the role), responsibilities list, qualifications list, skills list, benefits list, pay info ($60k plus annual bonus). No schedule info (no mention of schedule beyond Dayshift Hours maybe? Actually "Dayshift Hours" is listed under Premier Benefits? It appears as part of benefits list: "Dayshift Hours". That's schedule info? It's a schedule detail: dayshift hours. Could be considered schedule. The instruction: include Schedule section only if posting actually states them. It does mention Dayshift Hours. So we can include Schedule section with that detail.
We must not repeat job title as heading. No Job ID. Remove boilerplate: video link, EEO, etc. Also remove "WHY WORK FOR CENTIMARK?" etc. Keep substantive info.
We need to preserve all substantive info: job summary paragraph, responsibilities bullet list, qualifications bullet list, skills bullet list (maybe overlapping with qualifications). The posting includes "Candidate Qualifications" with bullet-like lines. Also "Proficiency in construction estimating software..." etc. Also "Bilingual skills preferred". Also "Premier Benefits" list. Also "Pay: $60k, plus annual bonus opportunity". Also "Dayshift Hours". Also maybe "Growth Opportunities" paragraph about company size; that's substantive but maybe not a specific section; could go under About the role? Might be considered company overview; we could include as part of About the role or maybe a separate section? Not required headings; we can put in About the role paragraph.
We must not invent or summarize away detail. Keep all details.
Let's extract:
About the role: "CentiMark Corporation, the national leader in the commercial roofing industry, has an exceptional opportunity for an experienced Roofing Project Manager in Monroe, NC. This role is paying $60k, plus annual bonus opportunity and premier benefits! Job Summary: The Roofing Project Manager is customer facing, being responsible for the flow of data, communication and documentation between CentiMark, the customer and stakeholders throughout all project phases. This position will engage primarily with New Construction projects being facilitated through General Contractors."
But we have Pay separate; we might not repeat pay in About the role. However the instruction: do not repeat job title as heading; we can keep the summary but maybe we should separate pay into Pay section. The About the role can include the job summary without pay. But we must preserve all substantive info; we can keep the pay info in Pay section and not duplicate. However the About the role currently includes "This role is paying $60k, plus annual bonus opportunity and premier benefits!" That's pay and benefits. We could split: keep the sentence about role being opportunity, but maybe we should move pay and benefits to respective sections. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. If we remove that sentence from About the role, we lose that info unless we put it elsewhere. We'll put pay in Pay section and benefits in Benefits section. So About the role will have the rest: "CentiMark Corporation, the national leader in the commercial roofing industry, has an exceptional opportunity for an experienced Roofing Project Manager in Monroe, NC. Job Summary: The Roofing Project Manager is customer facing, being responsible for the flow of data, communication and documentation between CentiMark, the customer and stakeholders throughout all project phases. This position will engage primarily with New Construction projects being facilitated through General Contractors."
That seems fine.
Responsibilities: list from "Generating project submittal packages" through "Provide support to the construction manager". Let's capture each line:
- Generating project submittal packages
- Pre-registering manufacturer’s warranties
- Change order management
- Produce & maintain schedule of values
- Maintain daily logs; generate progress reports
- Attend on-site meetings, take meeting minutes, perform quality control Inspections
- Navigate and resolve construction related issues, disputes and disagreements
- Maintain client project portals & act as primary POC throughout project phases
- Collaborate w/managers to fulfill data requests and answer technical questions
- Monitor project spend and assist in staying on budget
- Provide support to the construction manager
We need to keep punctuation as is.
Requirements: maybe "Experience coordinating large scale construction projects - Preferred Roofing related experience - Preferred". That's a bit weird. We'll treat as requirements.
Qualifications: maybe same as requirements? Actually the posting has "Candidate Qualifications" then bullet lines. We'll treat that as Qualifications.
Skills: maybe "Proficiency in construction estimating software (STACK, BIM 360, Procore)", "Thorough knowledge of construction practices and project flow", "Exceptional organizational & coordination skills", "Strong communication and interpersonal skills", "Competency in standard business applications: MS Office Suite, Cloud Apps, Acrobat", "Ability to read and translate construction plans, specifications and contracts", "Bilingual skills preferred". Those could be Skills.
But we have overlapping; we can separate: Requirements: Experience coordinating large scale construction projects; Preferred Roofing related experience. Qualifications: maybe same as skills? However we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We'll assign content accordingly.
Let's map:
- About the role: as above.
- Responsibilities: the list of duties.
- Requirements: "Experience coordinating large scale construction projects - Preferred Roofing related experience - Preferred". Actually the line: "Experience coordinating large scale construction projects - Preferred Roofing related experience - Preferred". Might be two bullet points: Experience coordinating large scale construction projects (Preferred), Roofing related experience (Preferred). We'll output as list items.
- Qualifications: maybe "Proficiency in construction estimating software (STACK, BIM 360, Procore)", "Thorough knowledge of construction practices and project flow", "Exceptional organizational & coordination skills", "Strong communication and interpersonal skills", "Competency in standard business applications: MS Office Suite, Cloud Apps, Acrobat", "Ability to read and translate construction plans, specifications and contracts", "Bilingual skills preferred". But some of those are skills. However we have separate Skills heading; we could put those under Skills. Qualifications could be something else? The posting only has "Candidate Qualifications" then those bullet lines. So we could treat that as Qualifications. Then Skills maybe we could leave empty or not include. But we need to only include sections with real content. If we put all those under Qualifications, we can omit Skills. However the instruction says prefer a few substantive sections over many thin ones. So we could combine Qualifications and Skills into one section? But we must follow allowed headings; we can omit Skills if no distinct content. Let's put all those bullet lines under Qualifications.
- Benefits: list from Premier Benefits.
- Pay: "$60k, plus annual bonus opportunity".
- Schedule: "Dayshift Hours". Possibly also mention that it's day shift. We'll put that.
Now ensure we don't include boilerplate: remove "WHY WORK FOR CENTIMARK? >>>> CLICK HERE TO WATCH VIDEO!", "CentiMark Corporation is North America’s largest commercial roofing contractor..." that's company overview maybe substantive but not under a heading; we could include in About the role as extra sentence. It's substantive about company size; we can add to About the role after job summary. It's not boilerplate; it's info about company. We'll keep.
Also remove "Drug Free Workplace - EOE (M/F/V/D) - E-Verify Employer For more information, please visit our website -- www.CentiMark.com/jobs". That's boilerplate/legal; remove.
Now craft HTML.
We'll open with maybe not needed; just output headings and content.
Structure:
About the role
CentiMark Corporation, the national leader in the commercial roofing industry, has an exceptional opportunity for an experienced Roofing Project Manager in Monroe, NC. Job Summary: The Roofing Project Manager is customer facing, being responsible for the flow of data, communication and documentation between CentiMark, the customer and stakeholders throughout all project phases. This position will engage primarily with New Construction projects being facilitated through General Contractors. CentiMark Corporation is North America’s largest commercial roofing contractor with 100 offices and over 3,500 employees. Each office has dedicated crews for the installation and service of all major roof systems, who are highly trained and experienced with a focus on safety.
Responsibilities
- Generating project submittal packages
- Pre-registering manufacturer’s warranties
- Change order management
- Produce & maintain schedule of values
- Maintain daily logs; generate progress reports
- Attend on-site meetings, take meeting minutes, perform quality control Inspections
- Navigate and resolve construction related issues, disputes and disagreements
- Maintain client project portals & act as primary POC throughout project phases
- Collaborate w/managers to fulfill data requests and answer technical questions
- Monitor project spend and assist in staying on budget
- Provide support to the construction manager
Requirements
- Experience coordinating large scale construction projects (Preferred)
- Roofing related experience (Preferred)
Qualifications
- Proficiency in construction estimating software (STACK, BIM 360, Procore)
- Thorough knowledge of construction practices and project flow
- Exceptional organizational & coordination skills
- Strong communication and interpersonal skills
- Competency in standard business applications: MS Office Suite, Cloud Apps, Acrobat
- Ability to read and translate construction plans, specifications and contracts
- Bilingual skills preferred
Benefits
- 2 Health Insurance Plans: No Cost “Core Plan” – No Cost Medical & Dental
- “Buy Up Plan” – Features a lower deductible for Medical
- Vision Plan
- Employer Paid Life & AD&D Insurance
- Traditional 401K with Company Match
- Roth 401K with Company Match
- Paid Holidays and Vacation
- Employer Provided Employee Stock Ownership Program (ESOP)
- Flexible Spending Account (FSA)
- Weekly Pay
- Referral Bonuses
- Dayshift Hours
Pay
$60k, plus annual bonus opportunity
Schedule
Dayshift Hours
Check duplication: Dayshift Hours appears also in Benefits list; we moved it to Benefits list as an item, but also we have Schedule section with Dayshift Hours. That duplicates. The instruction: do not repeat content? Not explicitly said, but we should avoid duplication. Since Dayshift Hours is a schedule detail, we could keep it only under Schedule and not under Benefits. However the benefits list included "Dayshift Hours" as a bullet under Premier Benefits. If we remove it from Benefits, we lose that benefit info. But we could keep it in Benefits and not have Schedule section, or keep it in Schedule and remove from Benefits. Which is more appropriate? The benefit list includes Dayshift Hours as a benefit; schedule is about work hours. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It does have specific content for schedule: Dayshift Hours. So we should have Schedule