Project Manager
BryComm, LLC · Charleston, SC · 2 wk ago
Project ManagementFull-time
We need to output HTML fragment with sections: headings for sections present: About the role? The posting includes intro paragraphs about company, why work with us, benefits, etc. We need to decide sections: maybe "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". We must only include sections when posting has real specific content.
Let's parse content:
- Intro: "Build Your Career Where You Matter Join CBX Solutions..." This is about company culture. Could be "About the role" or maybe "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map.
- "Why Work With Us?" then bullet list of benefits: Comprehensive Benefits: Health, dental, vision, prescription coverage, life insurance, and 401(k) with company match. Work-Life Balance: Generous paid time off... Career Growth: continuous learning... Supportive Culture: Innovation...
Thus we have Benefits section (with subpoints). Also maybe "Work-Life Balance" and "Career Growth" could be part of Benefits or separate sections? The instruction says use Benefits heading only if posting actually states them. It does state benefits. So we can put Benefits heading with list items.
- Pay: The posting includes "Pay Type Salary". That's a mention of pay type. It says Pay Type Salary. That's specific content (salary). So we should include Pay section with that detail.
- Schedule: Not mentioned. No schedule info. So omit Schedule.
- Responsibilities: The "Essential Functions" list is responsibilities. So we can have Responsibilities heading with list.
- Requirements: There's "Minimum Qualifications" and "Qualification Requirements". Also "Knowledge, Skills, And Abilities". Could split into Requirements (minimum qualifications) and Skills (knowledge, skills, abilities). The instruction says we can have Requirements and Skills sections. We'll include both.
- Qualifications: Might be redundant with Requirements. But we have Minimum Qualifications and Qualification Requirements. Could combine into Requirements. We'll not duplicate.
- Skills: Knowledge, Skills, And Abilities section.
Thus sections: About the role (intro), Responsibilities, Requirements, Skills, Benefits, Pay.
Check if any other sections like "Physical Demands" and "Work Environment" not in allowed headings; we should omit because not in list. We must not invent headings outside allowed list. So we omit those.
Now we need to preserve all substantive information, not invent or summarize away detail. Must not repeat job title as heading. Must not put Job ID etc.
We need to output only HTML fragment, no /, no markdown fences.
We'll produce something like:
.
Now the intro: "Build Your Career Where You Matter Join CBX Solutions, the nation’s leading provider of architectural doors, frames, hardware, specialty products, and complete security integration services. At CBX Solutions, trust and communication are the foundation of how we work. We foster an inclusive, collaborative culture where your voice is heard, your ideas matter, and your career has room to grow. Whether you're a problem-solver, innovator, or passionate about service, you’ll thrive here. Be part of a team that invests in your future, celebrates your success, and values your contribution."
We can combine into one or two paragraphs. Use
for sections present: About the role? The posting includes intro paragraphs about company, why work with us, benefits, etc. We need to decide sections: maybe "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". We must only include sections when posting has real specific content.
Let's parse content:
- Intro: "Build Your Career Where You Matter Join CBX Solutions..." This is about company culture. Could be "About the role" or maybe "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map.
- "Why Work With Us?" then bullet list of benefits: Comprehensive Benefits: Health, dental, vision, prescription coverage, life insurance, and 401(k) with company match. Work-Life Balance: Generous paid time off... Career Growth: continuous learning... Supportive Culture: Innovation...
Thus we have Benefits section (with subpoints). Also maybe "Work-Life Balance" and "Career Growth" could be part of Benefits or separate sections? The instruction says use Benefits heading only if posting actually states them. It does state benefits. So we can put Benefits heading with list items.
- Pay: The posting includes "Pay Type Salary". That's a mention of pay type. It says Pay Type Salary. That's specific content (salary). So we should include Pay section with that detail.
- Schedule: Not mentioned. No schedule info. So omit Schedule.
- Responsibilities: The "Essential Functions" list is responsibilities. So we can have Responsibilities heading with list.
- Requirements: There's "Minimum Qualifications" and "Qualification Requirements". Also "Knowledge, Skills, And Abilities". Could split into Requirements (minimum qualifications) and Skills (knowledge, skills, abilities). The instruction says we can have Requirements and Skills sections. We'll include both.
- Qualifications: Might be redundant with Requirements. But we have Minimum Qualifications and Qualification Requirements. Could combine into Requirements. We'll not duplicate.
- Skills: Knowledge, Skills, And Abilities section.
Thus sections: About the role (intro), Responsibilities, Requirements, Skills, Benefits, Pay.
Check if any other sections like "Physical Demands" and "Work Environment" not in allowed headings; we should omit because not in list. We must not invent headings outside allowed list. So we omit those.
Now we need to preserve all substantive information, not invent or summarize away detail. Must not repeat job title as heading. Must not put Job ID etc.
We need to output only HTML fragment, no /, no markdown fences.
We'll produce something like:
About the role
... intro paragraph(s) ...
Responsibilities
- ... each essential function ... ...
Requirements
- Associate’s Degree or equivalent combination of education/experience preferred (specific to industry standards).
- Current and valid US driver’s license.
- At least 1-3 years of experience in relevant industries (e.g., construction, Division 8, Division 10, aluminum storefront).
Skills
- Intermediate to advanced proficiency in Microsoft Word, PowerPoint, Excel, Adobe Professional, Outlook, and web-based applications.
- Strong project management skills, process-oriented, highly organized, and quality-focused.
- Excellent communication skills, both verbal and written.
- Ability to build strong working relationships at all levels, internal and external.
- Self-motivated, proactive, and able to handle multiple projects.
- Detail-oriented with strong mathematical skills.
Benefits
- Comprehensive Benefits: Health, dental, vision, prescription coverage, life insurance, and 401(k) with company match.
- Work-Life Balance: Generous paid time off for rest, family, and self-care.
- Career Growth: You’ll benefit from continuous learning, mentorship, and leadership training including access to CBX University, our in-house development program.
- Supportive Culture: Innovation, creativity, and teamwork are at the heart of everything we do.
Pay
Pay Type: Salary
We need to ensure we didn't include filler like "commensurate with experience". Not present. Check we didn't duplicate lines. The "Why Work With Us?" section we turned into Benefits list. Good. We omitted "Physical Demands", "Work Environment", "Equal Opportunity Employer", etc. We kept "Other duties as assigned." as part of responsibilities list. We need to ensure we included all substantive info from Essential Functions list. Let's list them: - Assist in defining project scope and objectives, ensuring technical feasibility and alignment with stakeholder expectations. - Ensure all projects are delivered on time, within scope, and budget. - Develop detailed project plans to monitor and track progress. - Manage changes to project scope, schedule, and costs using appropriate verification techniques. - Report and escalate incidents to management as needed. - Successfully manage relationships with internal teams, customers, and all applicable stakeholders. - Establish and maintain relationships with third parties/vendors. - Delegate project tasks to appropriate resources. - Ensure quality control verification and enforcement. - Coordinate and attend site meetings as per customer schedule and requirements. - Perform routine inspections of work sites for quality, scope, standards compliance, and safety. - Create and maintain comprehensive project documentation. - Complete project close-out documents and activities. - Other duties as assigned. We'll put each as. Now "Why Work With Us? We’re committed to your success, personally and professionally. You’ll have access to:" then bullet list. We already captured bullet list as Benefits. Should we include the introductory sentence? Could be part of Benefits section preamble. We could add a
before the list: "We’re committed to your success, personally and professionally. You’ll have access to:" but the instruction says use
for prose. So we can include a
before the
- . That's fine.
Similarly for About the role we may have multiple paragraphs.
Now check for any other substantive info: "Job Details Pay Type Salary Telecommute Percentage 100 Scan this QR code and apply! Download Charleston, SC, USA". There's also Telecommute Percentage 100 (meaning fully remote). That's schedule/telework info. The instruction says include Schedule section only if posting actually states them. It does state Telecommute Percentage 100. That's about remote work, could be considered Schedule or maybe a separate heading like "Telecommute". But allowed headings include Schedule. So we could treat Telecommute Percentage as part of Schedule. However the instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state Telecommute Percentage 100, which is about schedule/remote work. So we should include a Schedule section with that detail.
But we need to see if we should treat Telecommute Percentage as schedule. The heading Schedule is allowed. So we add a Schedule section with content: "Telecommute Percentage: 100%" (or "Telecommute Percentage 100").
Also there is "Job Details Pay Type Salary Telecommute Percentage 100 Scan this QR code and apply! Download Charleston, SC, USA". The location "Charleston, SC, USA" is also substantive. Could be part of Schedule or maybe a separate heading like Location but not allowed. Could incorporate into Schedule or Pay? Probably better to include location in Schedule section as well, or maybe as a separate paragraph under Schedule. Since we cannot create new headings, we can put location in Schedule section as prose.
Thus Schedule section:
- Comprehensive Benefits: Health, dental, vision, prescription coverage, life insurance, and 401(k) with company match.
- Work-Life Balance: Generous paid time off for rest, family, and self-care.
- Career Growth: You’ll benefit from continuous learning, mentorship, and leadership training including access to CBX University, our in-house development program.
- Supportive Culture: Innovation, creativity, and teamwork are at the heart of everything we do.
- Assist in defining project scope and objectives, ensuring technical feasibility and alignment with stakeholder expectations.
- Ensure all projects are delivered on time, within scope, and budget.
- Develop detailed project plans to monitor and track progress.
- Manage changes to project scope, schedule, and costs using appropriate verification techniques.
- Report and escalate incidents to management as needed.
- Successfully manage relationships with internal teams, customers, and all applicable stakeholders.
- Establish and maintain relationships with third parties/vendors.
- Delegate project tasks to appropriate resources.
- Ensure quality control verification and enforcement.
- Coordinate and attend site meetings as per customer schedule and requirements.
Telecommute Percentage: 100% (fully remote). Location: Charleston, SC, USA.
But we need to ensure we don't invent filler. It's specific. Now we need to check if any other specifics like "Posted Tuesday, September 29, 2026 at 4:00 AM" is metadata; we can drop per instruction: do not put Job ID/requisition numbers as headings — fold minor metadata into a shortor drop it. The posting date/time is minor metadata; we could drop it or include in a short p. Probably drop it. Now we must ensure we don't repeat job title as heading. Not. Now produce final HTML. Let's craft:
About the role
Build Your Career Where You Matter Join CBX Solutions, the nation’s leading provider of architectural doors, frames, hardware, specialty products, and complete security integration services. At CBX Solutions, trust and communication are the foundation of how we work. We foster an inclusive, collaborative culture where your voice is heard, your ideas matter, and your career has room to grow. Whether you're a problem-solver, innovator, or passionate about service, you’ll thrive here. Be part of a team that invests in your future, celebrates your success, and values your contribution.
Why Work With Us?
but not allowed heading. We should not create a heading not in list. So we should incorporate that intro into Benefits section as prose before list. So we don't need a separate heading for Why Work With Us. Thus Benefits section:Benefits
We’re committed to your success, personally and professionally. You’ll have access to:
Pay
Pay Type: Salary
Schedule section:Schedule
Telecommute Percentage: 100% (fully remote). Location: Charleston, SC, USA.
Now Responsibilities: