Audio Visual Design--Entry Level To AV

We need to output HTML fragment with sections: headings

for sections 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 — fold minor metadata into 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 parse the job description. Title: Junior Engineer Department: Audiovisual Reports to: AV Engineering Manager Summary ... Tasks ... Qualifications ... Job Type & Location ... Pay And Benefits ... Workplace Type ... Application Deadline ... About TEKsystems ... etc. We need to remove boilerplate: About TEKsystems, equal opportunity, etc. Also remove Application Deadline? It's not a required heading; but we could include as minor metadata in a short

  . The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." Application deadline is minor metadata; we can put in a

  . Also "Job Type & Location" is minor metadata; we can include in a

  . "Workplace Type" also minor metadata. We need sections: About the role (maybe from Summary), Responsibilities (Tasks), Requirements (Qualifications), Skills (maybe from Qualifications includes communication, detail oriented, MS Office, AutoCAD, networking, etc). Benefits and Pay: we have Pay And Benefits section with pay range and benefits list. So we should include Pay and Benefits sections? The instruction: "Prefer a few substantive sections over many thin ones." Could combine Pay and Benefits into one section? But they said use headings for Pay, Benefits, Schedule separately if content exists. Since we have both pay and benefits, we could make separate sections:

  Pay

  with pay range, and

  Benefits

  with list. Or combine into one

  Pay and Benefits

  but they said use headings for those specific names. It says: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those exact headings if we have content. So we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Possibly also Schedule? Not present. So we omit Schedule. We need to ensure we don't create sections with filler. We have content for each. Now we need to extract substantive content. About the role: from Summary: "The Junior Engineer is an entry level position in the AV Engineering department. The role of the Junior Engineer is to assist the Systems Engineers on the day to day engineering tasks. The Junior Engineer will learn all aspects of AV engineering. As a part of their training, the Junior Engineer will have the opportunity to work with sales people, project management, rack build and field staff to gain exposure to all aspects of the AV business. The Junior Engineer will eventually have the opportunity to transition into a sales engineer or system engineer role at Red Thread." We should preserve that. Responsibilities: from Tasks list. Need to list each bullet as

  . The tasks are: - Create / review system designs and proposals - Accompany sales people on client meetings to gather project requirements - Schedule and coordinate projects with subcontracted AutoCAD team - Review / create system drawings in AutoCAD based on sketches provide by the system engineers and product documentation - Attend onsite meetings to review and document construction progress and identify potential installation issues - Work with AV Lab to stage and test systems. Create punch lists for lab and/or programmers - Support field install staff and field engineers with technical support and functionality questions - Create / review change orders based on feedback from field staff and system engineers - Assist engineers with researching and troubleshooting product issues and provide solutions to installation team - Take active participation in various test bench or product development initiatives We need to keep the exact phrasing. Requirements: maybe from Qualifications? But they also have a "Qualifications" heading. The instruction says we can have both Requirements and Qualifications sections. However we need to avoid duplication. The posting has a "Qualifications" section with bullet points. We could treat that as Requirements. Or we could split: Requirements = education/experience, Skills = specific skills. But we have both Requirements and Qualifications as possible headings. The instruction says use those headings if content exists. We have content for both: we could put education/experience in Requirements, and skills in Skills. But the Qualifications section includes: Four-year college degree or equivalent experience; Excellent written and verbal communication skills; Detail oriented work approach and excellent follow up skills are a must; Proficiency in Microsoft Office products including, Outlook, Word, and Excel; General familiarity of Microsoft Windows environment and applications; Prior AutoCAD or Revit experience preferred; training will be provided if lacking; Knowledge of networking topology or commercial construction methods is a plus. We could separate: Requirements: Four-year college degree or equivalent experience. Skills: the rest (communication, detail oriented, MS Office, Windows familiarity, AutoCAD/Revit, networking/topology, commercial construction). However the instruction says prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one section? But they said we can use both headings. However to avoid many thin sections, we could combine into Qualifications only, and omit Requirements. But we need to follow instruction: "Prefer a few substantive sections over many thin ones." So we should aim for fewer sections. We already have About the role, Responsibilities, Qualifications, Skills, Benefits, Pay. That's six sections. Could we reduce? Maybe combine About the role and Responsibilities? No, they are distinct. Could combine Skills into Qualifications? That would reduce to five sections. Let's see: Qualifications could include both education/experience and skills. That seems reasonable. Then we wouldn't need a separate Skills section. The instruction says we can use Skills heading if we have content, but we prefer fewer sections. So we can omit Skills and put all qualification content under Qualifications. Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay. Check if we need Requirements? Not if we put everything in Qualifications. Now Benefits: list from Pay And Benefits: "Medical, dental & vision Critical Illness, Accident, and Hospital 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available Life Insurance (Voluntary Life & AD&D for the employee and dependents) Short and long-term disability Health Spending Account (HSA) Transportation benefits Employee Assistance Program Time Off/Leave (PTO, Vacation or Sick Leave)". Need to preserve as list. Pay: "$27.00 - $32.00/hr. Individual compensation offered for this position within this range will depend on many factors, including qualifications, skills, relevant experience, job knowledge, geographic location, internal equity, and other pertinent job-related factors." We should keep that. Now we need to strip boilerplate: About TEKsystems, equal opportunity, etc. Also remove "Job Type & Location", "Workplace Type", "Application Deadline". We can fold minor metadata into a short

  maybe at top? But we could drop them entirely as they are not substantive? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we could include a short

  containing location, job type, etc. But we need to preserve ALL substantive information; location and job type are substantive? They are minor metadata but still info. The instruction says we can fold minor metadata into a short

  or drop it. So we could either drop or include in a

  . To be safe, include a short

  at top: "Job Type & Location: Contract to Hire, Andover, MA. Workplace Type: Fully onsite." Also maybe include Application Deadline? That's also minor metadata. Could include: "Application Deadline: Sep 25, 2026." But that's far future; still info. We'll include. Thus we will have a leading

  with that metadata. Now we need to output only HTML fragment, no /, no markdown. Structure:

  Job Type & Location: Contract to Hire, Andover, MA. Workplace Type: Fully onsite. Application Deadline: Sep 25, 2026.

  About the role

  ...summary...

  Responsibilities

  • ... each task ...

  Qualifications

  • Four-year college degree or equivalent experience
  • Excellent written and verbal communication skills
  • Detail oriented work approach and excellent follow up skills are a must
  • Proficiency in Microsoft Office products including, Outlook, Word, and Excel
  • General familiarity of Microsoft Windows environment and applications
  • Prior AutoCAD or Revit experience preferred; training will be provided if lacking
  • Knowledge of networking topology or commercial construction methods is a plus

  Benefits

  • Medical, dental & vision
  • Critical Illness, Accident, and Hospital
  • 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available
  • Life Insurance (Voluntary Life & AD&D for the employee and dependents)
  • Short and long-term disability
  • Health Spending Account (HSA)
  • Transportation benefits
  • Employee Assistance Program
  • Time Off/Leave (PTO, Vacation or Sick Leave)

  Pay

  The pay range for this position is $27.00 - $32.00/hr. Individual compensation offered for this position within this range will depend on many factors, including qualifications, skills, relevant experience, job knowledge, geographic location, internal equity, and other pertinent job-related factors.

  We need to ensure we didn't include any boilerplate like "Eligibility requirements apply to some benefits..." etc. That's part of Benefits section? Actually the Pay And Benefits paragraph includes: "Eligibility requirements apply to some benefits and may depend on your job classification and length of employment. Benefits are subject to change and may be subject to specific elections, plan, or program terms. If eligible, the benefits available for this temporary role may include the following:" Then list. We should preserve the substantive info: the list of benefits. The introductory sentences about eligibility etc are somewhat boilerplate but still part of benefits description. Should we keep them? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The eligibility sentences are substantive? They are generic but still part of posting. However they might be considered boilerplate. The instruction also says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The eligibility sentences are not exactly those categories but could be considered generic boilerplate. However they are part of the benefits description; removing them might lose some nuance but not essential. I'd lean to keep them as part of Benefits section prose before the list. But we used a list only