Project Specialist

We need to output HTML fragment with sections: headings

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Preserve all substantive info. Include a section only when posting has real specific content. Avoid filler like "commensurate with experience". No Pay/Schedule/Benefits unless posting actually states them. The posting mentions Total Rewards And Benefits with details. So we can have Benefits section. No explicit Pay or Schedule. There's mention of "May be required to work more than 40 hours per week." That's schedule info? It's about hours, could be considered schedule. But the instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state schedule info: "May be required to work more than 40 hours per week." That's schedule. So we could include a Schedule section with that detail. However we need to see if that's considered substantive. It's a statement about hours. Could be included under Schedule. But we need to decide: The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state schedule info, so we can include Schedule. However we must avoid filler like "varies", "TBD". This is specific: "May be required to work more than 40 hours per week." That's substantive. Also we have Qualifications section: includes education, experience, preferred. Also Physical Demands could be part of Requirements or Qualifications? Probably Requirements. The posting has "Qualifications" heading already. We'll keep that. We also have "Primary Duties" which is responsibilities. We'll make Responsibilities section. We have "Total Rewards And Benefits" => Benefits. We have "Physical Demands" maybe part of Requirements or a separate section? Not in allowed headings list; we could fold into Requirements or Qualifications. Probably Requirements. We have "Family Owned. Culture of Quality..." that's fluff but maybe part of About the role? Could be considered About the role (company description). We'll include About the role section with that prose. We need to remove EEO boilerplate etc. Also remove "Candidates are subject to pre-employment assessments..." etc. That's application instructions/legal; remove. Also remove "If reasonable accommodation is needed, please contact jobs@cesco.com" - that's application instruction; remove. Also remove "Crescent Electric Supply Company is proudly an Equal Opportunity Employer..." etc. Remove. Also remove "Veterans and military spouses are highly encouraged to apply." That's EEO; remove. Also remove "We recognize and value the unique strengths of the military community..." remove. Also remove "Candidates are subject to pre-employment assessments..." remove. Also remove "If reasonable accommodation is needed..." remove. Also remove "Crescent Electric is committed to the full inclusion..." remove. Now compile substantive content: - About the role: maybe a brief intro: "As a Project Specialist, you will be responsible for overseeing and managing projects beginning with initiating the submittal process, setting up the file, and ending when the job is closed." That's the first sentence. Also the culture statements: "Family Owned. Culture of Quality. Opportunities to Advance. Crescent is transforming and we are on a mission to power the communities we serve through teamwork and relentless customer focus. We have a vision of uncompromising teamwork committed to becoming the industry leader for our employees, suppliers, and shareholders. At Crescent, you will have the opportunity to develop professionally, grow personally and have the flexibility to balance your life's priorities. Let's serve together. Let's power our communities together. Let's become THE industry leaders...together." That's substantive. - Responsibilities: list of primary duties bullet points. Let's extract duties: "Set up each job file according to established standards. All documentation pertaining to the job is filed according to procedures. Ensure that active job files are kept current with all relative information pertaining to projects including customer purchase orders, sales orders, vendor purchase orders, cut sheets, vendor and customer correspondence, change orders, specification sheets, delivery schedules, manufacturer invoices, and acknowledgements. Release project for shipment with vendors once written release from customer is received. Perform appropriate expediting functions to ensure material is shipped by vendor and received by customer in the agreed-upon time frame. Build strong professional relationships with customers and vendors to provide the best customer service possible." We can make a

  • list. - Requirements/Qualifications: The posting has "Qualifications" heading with content: "High school diploma and 1 to 3 years related experience; or equivalent combination of education and experience. Bachelor's degree from four-year college or university preferred. Previous experience working with customers (preferably contractors/vendors) and experience working on Eclipse systems and processing orders is preferred." Also Physical Demands: "Predominately sitting, some standing, stooping and bending. Must have transportation available to attend meetings outside of the office. Sitting, using hands/fingers to handle/feel, reaching with hands/arms, and talking/hearing are often needed. Occasionally the ability to lift up to 25 lbs. is needed. For plan/specification reading, close vision (clear vision at 20 inches or less) and the ability to adjust focus (ability to adjust the eye to bring an object into sharp focus) are necessary. May be required to work more than 40 hours per week." We could treat Physical Demands as part of Requirements or a separate section? Not in allowed headings; we could include under Requirements (maybe as a subsection). But we need to follow instruction: Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have either Requirements or Qualifications. The posting already has Qualifications; we can keep that as Qualifications. Physical Demands could be part of Requirements (maybe we create a Requirements section). But we already have Qualifications; we could also have Requirements for physical demands. However we should avoid thin sections. Perhaps combine Qualifications and Physical Demands into one Qualifications section? But the instruction says we can use those headings; we can have both Qualifications and Requirements if we have content. However we risk thin sections. Let's see: Qualifications content is about education/experience. Physical Demands is about abilities. Could be separate but both are substantive. Might be okay to have both. But we also have Skills? Not explicitly listed; we could infer from duties but better not to invent. So we skip Skills. Benefits: we have details. Schedule: we have "May be required to work more than 40 hours per week." That's schedule info. Could be placed under Schedule section. But we already have Physical Demands includes that line. If we move schedule line to Schedule section, we need to remove from Physical Demands to avoid duplication. However the line is about hours, which is schedule. We could keep it under Physical Demands as part of demands, but then we would not have a Schedule section. The instruction says never create Schedule unless posting actually states them. It does state schedule info, but we could still include it under Physical Demands; but then we wouldn't have a Schedule section, which is fine. However we might want to separate schedule for clarity. But we risk creating a thin Schedule section with just that line; but it's still substantive. The instruction says prefer a few substantive sections over many thin ones. So maybe better to keep schedule line within Physical Demands (or Requirements) and not create a separate Schedule section. That reduces number of sections. Thus we will have sections: About the role, Responsibilities, Qualifications, Benefits. Possibly also Requirements? But we have Qualifications covering education/experience; we could add Requirements for physical demands. But that would be another section. Might be okay if we have substantive content. Let's see: Physical Demands content is several sentences; that's substantive. So we could have a Requirements section for physical demands and abilities. Then Qualifications for education/experience. That yields 4 sections plus About role and Responsibilities and Benefits = 6 sections. Might be okay but we need to avoid too many thin sections. Each is substantive. Alternatively combine Qualifications and Requirements into one Qualifications section that includes both education/experience and physical demands. That would be longer but still one section. The instruction allows Qualifications heading; we can put all qualification-related content there. That seems reasonable. Thus sections: About the role, Responsibilities, Qualifications, Benefits. Now we need to format. About the role:

    with the intro sentence plus the culture paragraph(s). Could be multiple

    but we can combine into one

    with sentences. Responsibilities:

    Responsibilities

    then
    • each duty. Qualifications:

      Qualifications

      then

      for prose? The content includes bullet-like items but we can make

      • for each qualification item. However the instruction: Use
        • for any list of duties/requirements/benefits, and

          for prose. So for qualifications list we should use

          • . Similarly for benefits list. Thus Qualifications: list items: - High school diploma and 1 to 3 years related experience; or equivalent combination of education and experience. - Bachelor's degree from four-year college or university preferred. - Previous experience working with customers (preferably contractors/vendors) and experience working on Eclipse systems and processing orders is preferred. We could also include physical demands as list items under Qualifications? Might be okay but they are not exactly qualifications; they are demands. But we can still list them as qualifications? Might be stretching. Better to keep them under Qualifications as they are still job requirements. The instruction says use list for any list of duties/requirements/benefits. So we can treat physical demands as requirements list. So we could have two lists: one for qualifications (education/experience) and another for requirements (physical demands). But that would be two sections if we separate headings. To keep one Qualifications section, we could combine both education/experience and physical demands into a single list? That would mix types but still a list. Might be okay. Alternatively we could have Qualifications (education/experience) and Requirements (physical demands) as two sections. Let's evaluate thinness: Qualifications section would have 3 items; Requirements section would have maybe 5 items (sitting, transportation, lifting, vision, hours). Both are substantive. So total sections: About role, Responsibilities, Qualifications, Requirements, Benefits = 5 sections. That's okay. But we need to avoid creating sections with filler. Both have real content. Thus we will have:

            About the role

            As a Project Specialist, you will be responsible for overseeing and managing projects beginning with initiating the submittal process, setting up the file, and ending when the job is closed. Family Owned. Culture of Quality. Opportunities to Advance. Crescent is transforming and we are on a mission to power the communities we serve through teamwork and relentless customer focus. We have a vision of uncompromising teamwork committed to becoming the industry leader for our employees, suppliers, and shareholders. At Crescent, you will have the opportunity to develop professionally, grow personally and have the flexibility to balance your life's priorities. Let's serve together. Let's power our communities together. Let's become THE industry leaders...together.

            Responsibilities

            • Set up each job file according to established standards.
            • All documentation pertaining to the job is filed according to procedures.
            • Ensure that active job files are kept current with all relative information pertaining to projects including customer purchase orders, sales orders,