Traffic Control Apprentice Burnsville, NC
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. So we can include About the role heading with job summary. Then Responsibilities heading with list. Then Requirements heading with list (maybe combine requirements and qualifications). Then Benefits heading with list. Then Pay heading with paragraph. No Schedule because not provided. Also we should not include filler like "commensurate with experience". We have Pay specific. Good.
We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting: job summary, responsibilities list, requirements list, benefits list, pay. Also maybe include "Work Environment" and "Experience" as part of Requirements? The instruction: Prefer a few substantive sections over many thin ones. So we can combine Experience and Work Environment into Requirements section as bullet points.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At end there is EEO statement; we should drop that. Also duplicated lines like "Phoenix Spirit Group is looking to welcome..." etc. That seems like duplicated content; we should keep only unique substantive info. The posting includes repeated paragraphs about PSG and Helix. We need to keep substantive info but not duplicate. The repeated content about PSG and Helix appears twice; we should keep one copy. Also the "Phoenix Spirit Group is looking to welcome..." is similar to earlier. We'll keep one version.
We need to output only HTML fragment, no /, no markdown fences.
Let's craft:
About the role
... job summary paragraph ...
Then responsibilities list. Then requirements list. Then benefits list. Then pay. Make sure to use- for lists.
Let's extract exact text.
Job Summary: "JOB SUMMARY: The Traffic Control Apprentice is responsible for maintaining the flow of traffic around construction zones, maintenance projects, accidents, or other temporary traffic disruption areas. This role ensures the safety of workers, motorists, and pedestrians by maintaining proper traffic control and following all safety guidelines and regulations. _ As a Traffic Control Apprentice, you will be our front line for safety. _"
We can keep that as paragraph.
Responsibilities bullet list:
- Control vehicle and pedestrian traffic around work zones using handheld signs, paddles, or flags
- Set up, maintain, and remove temporary traffic control work zones including signs, barricades, and cones according to project requirements and regulations
- Communicate clearly with drivers to provide guidance and ensure safe traffic flow
- Monitor traffic and construction activity to anticipate and respond to potential safety hazards
- Coordinate with supervisors and other team members using hand signals, radios, or other communication equipment
- Adhere to all safety protocols, including wearing appropriate personal protective equipment (PPE)
- Warn workers when approaching vehicles fail to heed signals to prevent accidents and injuries
- Assist with loading/unloading traffic control equipment as needed
- Perform other work-related duties as assigned
Requirements/Qualifications list:
- Being a Team Player
- Understand and apply safe traffic control practices, sometimes in stressful situations
- Ability to receive and communicate instructions clearly, firmly and courteously
- Strong attention to detail and focus
- Keep a reliable and professional demeanor at all times
- Able to stand for extended periods (8+ hours) while maintaining focus
- Be 20 years of age or older
- Must be able to pass a drug screen
- Must have a valid driver's license AND also reliable transportation
- Able to lift and carry up to 50 lbs
- Ability to work in all weather conditions
- Have a high school diploma or equivalent preferred
- Traffic control/ Flagger Certification (Provided by the company)
- Experience: No prior experience required; traffic control experience preferred
- Willing to learn and follow safety procedures
- Work Environment: Outdoor work environment in and around construction zones; Exposure to traffic, loud noises, and construction equipment; Travel to different work sites
We could combine Experience and Work Environment as bullets.
Benefits list:
- Medical Insurance
- Dental Insurance
- Vision Insurance
- Company Paid Life Insurance
- 401(k) with Company Match
- Paid Time Off
- Paid Holidays
- Overtime Opportunities
- Paid on-the-job Training
- Referral Bonuses
- Safety Incentives
- Competitive wage with regular increases based on performance
- Advancement Opportunities
- Great Company Culture
Pay: "From $16.00 per hour"
We should not include Schedule.
Now ensure we don't include any boilerplate like "Helix Traffic Solutions, LLC is an Equal Opportunity Affirmative Action Employer." Remove.
Also remove duplicated lines like "Phoenix Spirit Group is looking to welcome talented, hard-working individuals to join our team! We are Phoenix Spirit Group (PSG), a traffic services company that prides itself on keeping our roadways safe..." That seems like duplicate of earlier content about PSG. We'll keep only one instance maybe the earlier "About PSG Traffic Services" paragraph. Let's see earlier: "About PSG Traffic Services PSG Traffic Services is a proud member of the Helix Traffic Solutions network, serving roadways across North Carolina and South Carolina with professional traffic management and traffic control solutions for projects of all sizes. PSG is committed to enhancing roadway safety and ensuring seamless operations while maintaining strict compliance with all state and local regulations. We support state agencies, municipalities, and leading private and publicly owned organizations throughout the region with dependable services and equipment designed to keep traffic flowing safely and efficiently. Our Services And Capabilities Include Traffic management and traffic control services for construction, maintenance, and infrastructure projectsSales and rental of traffic control equipment, including cones, drums, barricades, and channelizing devicesAdvanced trailered equipment such as arrow boards and portable message boardsTraffic solutions designed to minimize disruption while prioritizing safety and complianceProfessional planning and execution to manage complex traffic challenges effectively With a focus on precision, reliability, and regulatory adherence, PSG Traffic Services delivers solutions that protect workers, drivers, and surrounding communities."
That's substantive. The later duplicate about Phoenix Spirit Group is similar but we can drop it to avoid duplication. We'll keep the earlier About PSG Traffic Services paragraph as part of About the role? Actually About the role is job summary; we could also include a brief About the company paragraph under About the role? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So About the role heading likely expects description of the role, not company. But we could include company info under About the role as prose. It's okay. Thus About the role paragraph: combine job summary and maybe a brief about company? But we must not invent. We'll keep job summary as the About the role content. The company info could be considered part of About the role? Might be okay but risk of being considered not role-specific. However we need to preserve ALL substantive information; we cannot omit company info. So we need to include it somewhere. Could add a separate section like "About the company" but not in allowed headings. The instruction says use those headings for sections; but we can also have other headings? It says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections, but we could also include other headings if needed? It says "Use
for section headings (e.g. ...)" meaning those are examples; we should use h3 for any section headings we create. It doesn't forbid other headings, but we should follow the pattern. Safer to include company info under About the role heading as prose, as it's still about the role context. That should be fine. Thus About the role paragraph will include both job summary and company description. Let's craft About the role paragraph:
The Traffic Control Apprentice is responsible for maintaining the flow of traffic around construction zones, maintenance projects, accidents, or other temporary traffic disruption areas, ensuring the safety of workers, motorists, and pedestrians by maintaining proper traffic control and following all safety guidelines and regulations. As a front line for safety, you will work with Helix Traffic Solutions and its regional member PSG Traffic Services, a national leader in traffic control, work zone safety, and roadway infrastructure services serving North and South Carolina. PSG provides traffic management and traffic control services, sales and rental of equipment, advanced trailered equipment, and professional planning to keep traffic flowing safely and efficiently.
But we must not invent; we need to preserve exact wording. Better to keep two separate paragraphs: one for job summary, one about company. Both under About the role heading as separatetags. We'll copy exact sentences from the posting. Job summary paragraph exactly: "JOB SUMMARY: The Traffic Control Apprentice is responsible for maintaining the flow of traffic around construction zones, maintenance projects, accidents, or other temporary traffic disruption areas. This role ensures the safety of workers, motorists, and pedestrians by maintaining proper traffic control and following all safety guidelines and regulations. _ As a Traffic Control Apprentice, you will be our front line for safety. _" We can keep the underscores? They seem like formatting; we can remove underscores as they are not substantive. Probably okay to remove. Company paragraph: "About PSG Traffic Services PSG Traffic Services is a proud member of the Helix Traffic Solutions network, serving roadways across North Carolina and South Carolina with professional traffic management and traffic control solutions for projects of all sizes. PSG is committed to enhancing roadway safety and ensuring seamless operations while maintaining strict compliance with all state and local regulations. We support state agencies, municipalities, and leading private and publicly owned organizations throughout the region with dependable services and equipment designed to keep traffic flowing safely and efficiently. Our Services And Capabilities Include Traffic management and traffic control services for construction, maintenance, and infrastructure projectsSales and rental of traffic control equipment, including cones, drums, barricades, and channelizing devicesAdvanced trailered equipment such as arrow boards and portable message boardsTraffic solutions designed to minimize disruption while prioritizing safety and complianceProfessional planning and execution to manage complex traffic challenges effectively With a focus on precision, reliability, and regulatory adherence, PSG Traffic Services delivers solutions that protect workers, drivers, and surrounding communities." We need to fix missing spaces: "projectsSales" should be "projects. Sales". But we must not invent; we can't add punctuation that wasn't there? The original lacks spacing; but we can keep as is? It's messy but it's the original. We could add a space for readability but that's altering. Probably okay to keep as is; it's still the same characters. We'll keep exactly as given, but we can add a space after "projects" to make readable? That would be inventing. Better to keep as is. We'll output that paragraph. Now Responsibilities list: copy bullet points exactly as given. Requirements list: combine all bullet points from Requirements/Qualifications, Experience, Work Environment. We'll list each as
- . Benefits list: copy bullet points exactly. Pay: <