OSP Design Technician

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. No Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. Key info: - TEKsystems seeking OSP Design Tech for Boise Idaho client. Client expanding OSP Engineering group due to project growth. Team bottleneck, adding multiple OSP Design Technicians. - This is a full time, direct placement position with client. - Role supports outside plant telecom projects including city and state roadway relocations, utility relocations, aerial and underground fiber construction, ongoing network expansion initiatives. - Position combines design work, field engineering, documentation, contractor coordination, construction support. - Primary Responsibilities list: bullet points. - Required Qualifications: bullet list. - Preferred Qualifications: bullet list. - Work Environment: Approximately 50% field / 50% office; Travel up to 20%; occasional overtime, evenings, weekends, holiday work may be required. - Employee Value Proposition: bullet list. - Top Required Skills: bullet list. - Job Type & Location: Permanent position based out of Emmett, ID. - Pay And Benefits: pay range $66560.00 - $83200.00/yr. Then list benefits. - Workplace Type: fully onsite position in Emmett,ID. - Application Deadline: anticipated to close on Sep 29, 2026. - About TEKsystems: boilerplate; we need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About TEKsystems" sections are likely boilerplate; we should drop them unless they contain substantive info about the role. They are generic company description; we should remove. - Also "San Francisco Fair Chance Ordinance", "Massachusetts Lie Detector", "Use of Artificial Intelligence (AI)" are legal boilerplate; remove. Thus we need to keep: - Intro paragraph about role and context. - Primary Responsibilities. - Required Qualifications. - Preferred Qualifications. - Work Environment. - Employee Value Proposition (maybe as Benefits? but it's more about culture; could be under Benefits? The instruction says use Benefits section only if posting actually states them. The posting includes "Employee Value Proposition" with bullet points; that is essentially benefits/culture. We could treat that as Benefits section. However there is also a separate Pay And Benefits section with explicit benefits. So we could combine? Probably better to have Benefits section that includes the Employee Value Proposition bullet points plus the explicit benefits (medical plans etc). But we must not invent sections; we can have Benefits if there is real content. There is explicit benefits list, so we include Benefits. - Pay section: we have pay range. - Schedule: we have work environment (field/office, travel, overtime). That could be Schedule section. The instruction: use

for Schedule if posting actually states them. The posting includes work environment details: Approximately 50% field / 50% office; Travel up to 20%; occasional overtime, evenings, weekends, holiday work may be required. That's schedule info. So we can create Schedule section. - Skills: there is "Top Required Skills" bullet list. That could be Skills section. - Requirements vs Qualifications: The posting has Required Qualifications and Preferred Qualifications. We could combine into Requirements section? The instruction: use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to include. We have both Required and Preferred qualifications; we could put them under Requirements (maybe split into Required and Preferred subheadings? But we cannot create subheadings not listed; we could just list all qualifications under Requirements heading. Or we could have Qualifications heading for Required Qualifications and maybe Preferred under Requirements? Safer: Use Requirements heading for Required Qualifications, and Qualifications heading for Preferred Qualifications? But that seems redundant. The instruction says prefer a few substantive sections over many thin ones. So maybe combine Required and Preferred into one Qualifications section. But we also have Skills separate. Let's think: The posting includes "Required Qualifications", "Preferred Qualifications", "Top Required Skills". Could map: - Requirements: maybe the core responsibilities? Actually Responsibilities separate. - Qualifications: combine Required and Preferred. - Skills: Top Required Skills. But we also have Responsibilities heading. Thus sections: About the role (maybe not required but we can include as intro paragraph without heading? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says use

for section headings (e.g. About the role, ...). It does not say we must include About the role heading; but we can include if we have content. The intro paragraph about role could be under About the role. Thus we will output:

About the role

... intro paragraph ...

Responsibilities

• ... each responsibility ...

Requirements

Maybe we can put Required Qualifications here? But we also have Qualifications heading. Let's decide: Use Requirements for Required Qualifications, Qualifications for Preferred Qualifications? That would be two thin sections. Better to combine into Qualifications. But we need to follow instruction: they gave examples but not mandatory to use all. We can choose to have Qualifications section containing both Required and Preferred. Then we can omit Requirements heading. However we also have Skills separate. So we will have:

Qualifications

• Required: ...
• Preferred: ...

but that mixes. Better to keep separate headings? The instruction says prefer a few substantive sections over many thin ones. Having both Required and Preferred as separate headings would be thin. So combine. Thus Qualifications section will contain both required and preferred bullet points, maybe we can label them within

or

with sub-bullets? We can just list all qualifications as bullet points, maybe with note (required) or (preferred). But we must preserve all substantive info; we can keep them as separate bullet groups but still under one heading. We'll do:

Qualifications

• Minimum 2 years of Outside Plant (OSP) telecom engineering or design experience (required)
• Experience supporting telecom construction and field operations (required)
• Ability to read and interpret: staking sheets, construction drawings, permitting documentation, methods of construction, right-of-way documentation (required)
• Experience working with Microsoft Visio (required)
• Working knowledge of CAD systems or telecom design software (required)
• Strong Microsoft Office skills (required)
• Strong organizational, communication, and problem-solving abilities (required)
• Ability to manage multiple priorities and work independently (required)
• Valid driver's license (required)
• Fiber optic network design experience (preferred)
• Utility relocation or road move project experience (preferred)
• Knowledge of RUS standards (preferred)
• Experience supporting permitting and construction processes (preferred)
• Field engineering experience (preferred)
• GIS experience (preferred)
• Project lead or contractor coordination experience (preferred)
• Telecommunications construction background (preferred)
But we must not invent content; we are just rephrasing slightly but preserving meaning. Adding "(required)" and "(preferred)" is okay as it clarifies but not adding new info; it's derived from original grouping. Should be fine. Now Skills: Top Required Skills bullet list: - 2+ year of OSP telecom engineering or design experience - Telecom construction and field operations experience - Ability to interpret permits, right-of-way documents, and construction methods - Microsoft Visio - CAD or telecom design software experience - Microsoft Office proficiency - Valid driver's license These overlap with qualifications; but we must preserve all substantive info; we can include them as Skills section. Now Benefits: we have Employee Value Proposition bullet list and Pay And Benefits benefits list. Employee Value Proposition: - Warm, collaborative team culture - Flexible and supportive management - Stable project pipeline with strong business growth - Opportunity to work across engineering, design, field operations, and construction - Exposure to critical fiber infrastructure and utility relocation projects - Strong visibility within a growing OSP organization Pay And Benefits benefits: - 4 medical plans, 2 dental plans, 1 vision plan - HSAs and FSAs - Paid parental leave - 9 company-paid holidays and paid time off - Fully covered group life insurance, AD&D, and short- and long-term disability - Optional extra protection: supplemental life, critical illness, accident, and hospital indemnity - Employee referral program and years of service recognition - 401(k) plan with company match - Tuition and certification reimbursement - Access to our Learning Management System for ongoing development We should combine these into Benefits section. Now Pay section: pay range $66560.00 - $83200.00/yr. Also note that compensation determined based on experience etc. We'll include that. Now Schedule section: work environment details: Approximately 50% field / 50% office; Travel up to 20% depending on project workload; Occasional overtime, evenings, weekends, and holiday work may be required. Now About the role: intro paragraph: TEKsystems is seeking an OSP Design Tech for our Boise Idaho client. Our client is expanding their OSP Engineering group due to significant project growth and increasing sales volume. The team is currently operating as a bottleneck for incoming work and is adding multiple OSP Design Technicians to increase project capacity. This is a full time, direct placement position with our client. This role supports outside plant telecom projects including city and state roadway relocations, utility relocations, aerial and underground fiber construction, and ongoing network expansion initiatives. The position combines design work, field engineering, documentation, contractor coordination, and construction support. We should also mention location: Emmett, ID (from Job Type & Location). Could include in About the role or maybe separate? But we have no separate heading for location; we could include in About the role paragraph. Also mention Workplace Type: fully onsite position in Emmett,ID. Could be part of About the role or Schedule? Probably include in About the role. Application Deadline: anticipated to close on Sep 29, 2026. This is metadata; we could drop as per 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 could fold into a short p under About the role or drop. The instruction says preserve ALL substantive information; is deadline substantive? Probably not essential to role; but it's info about timing. Might be considered minor metadata; we could drop. Safer to include as a short p under About the role? The instruction says fold minor metadata into a short

or drop it. So we can include a short p. Thus About the role paragraph will include all that. Now we must not include boilerplate like "About TEKsystems" etc. Now output HTML fragment only. Let's craft. We'll need to escape any special characters? Not needed. Structure:

About the role

TEKsystems is seeking an OSP Design Tech for our Boise Idaho client. The client is expanding their OSP Engineering group due to significant project growth and increasing sales volume; the team is currently a bottleneck for incoming work and is adding multiple OSP Design Technicians to increase project capacity. This is a full‑time, direct‑placement position with the client. The role supports