Ops Fiber Technician III - Phoenix, AZ
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a 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. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to parse the job posting.
Content:
Job Overview (maybe a heading but we shouldn't repeat job title). The "Job Overview" is likely a section heading but we need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have "Job Overview" then "Job Requirements:" then a list of requirements.
Then "Company Overview" describing Talus Development.
Then "Benefits" list.
Then EEO Statement etc which we need to remove.
Also there is "Agency Statement" etc remove.
We need to preserve substantive information: job overview, requirements, company overview, benefits.
We need to decide which sections to use.
"Job Overview" could map to "About the role" (or maybe "Responsibilities"?). The content after "Job Overview" is not given explicitly; the text shows "Job Overview Job Requirements:" maybe missing line break. Actually the snippet: "Job Overview Job Requirements: Must have a valid Arizona driver license and clean record..." It seems the job overview may be missing; maybe the overview is just the line "Job Overview". But we need to preserve substantive information; if there is no actual overview text besides the heading, we should not create a section with filler. So we might skip About the role if no content.
But we have "Job Requirements:" which is a list of requirements. That maps to "Requirements" section.
We have "Company Overview" which could map to "About the role"? Actually company overview is about the company, not role. Could be "About the role"? Not exactly. There's no specific heading for company overview; but we could put it under "About the role" maybe as description of the company? However guidelines: Use headings only for those specific categories. If we have company overview, we could treat it as "About the role" (since it's about the role context). Or we could omit if not fitting. But we need to preserve ALL substantive information; we cannot drop company overview. So we need to include it somewhere. The allowed headings include "About the role". That seems appropriate to include company overview and maybe role description. Since we don't have explicit role description besides requirements, we can put company overview under About the role.
We also have Benefits list, which maps to Benefits section.
Pay and Schedule: Not mentioned explicitly. There's "Competitive compensation paid weekly." That's about pay. So we have pay info: "Competitive compensation paid weekly." That's specific enough to create a Pay section. It mentions weekly pay but not amount. Is that considered filler? It's not "commensurate with experience" etc. It's a statement about compensation being competitive and paid weekly. That's substantive. So we should include Pay section.
Schedule: Not mentioned. No schedule info. So we should not create Schedule section.
Skills: Could be extracted from requirements but we already have Requirements section; we could also have Skills but we prefer few substantive sections. So we can combine skills into Requirements or maybe not create Skills.
Qualifications: Could be similar to Requirements. We'll just have Requirements.
Thus sections: About the role (company overview), Requirements (list), Benefits (list), Pay (statement). Possibly also Responsibilities? Not given explicitly; but many requirements are duties. Could map to Responsibilities. However we have a list of requirements that includes duties like "Ability to prep and install fiber cables..." etc. Those are responsibilities. So we could split: Responsibilities (duties) and Requirements (qualifications). But we need to avoid thin sections. Let's see if we can separate meaningfully.
The list includes many items: driver license, problem solve, Excel, lift 70 lbs, work on sites, commitment to quality, attention to detail, safely uses tools, prep and install fiber cables, fusion splice, read splice details, troubleshoot, knowledge of NESC, communication, proficiency with EXFO 715 OTDR, performs testing, distinguish color jackets, ETA Fiber Technician certified, 4 years experience, troubleshoots back to ODNA, assists in field training, completes OLM activations, edits documentation, provides invoicing data, perform hi-cap large fiber count ring work, experience with cable types, performs OLT augmentation, schedules and coordinates with Cox Comm project planners, completes HFC mid-split node change, performs testing and documentation.
These are a mix of qualifications and responsibilities. Could treat all as Requirements. That's fine.
Thus we will have:
About the role
Talus Development is a full service utility contractor specializing in communications infrastructure including coax, fiber, voice, video and data. We install conduit structures, pull fiber/conductors, fiber/coax splicing/testing, cabinets and power supplies in subdivisions, multi-dwelling units, cell tower and small cell environments.
Requirements
- Must have a valid Arizona driver license and clean record
- Must possess ability to problem solve
- Proficiency with Excel and Adobe Acrobat
- Requires ability to lift 70 lbs
- Must be able to work on sites with stairs, ladders, bucket trucks, and uneven terrain
- Complete commitment to quality following industry and customer standards
- Requires attention to detail while following specific documented instruction
- Safely uses hand and small power tools
- Ability to prep and install fiber cables into various enclosure types; includes new and existing
- Fusion splice fibers within customer spec and parameters
- Read and interpret splice details and complete as-built docs accordingly
- Ability to troubleshoot down to element level based on traces and or testing results
- Knowledge of and ability to follow NESC and other state and local safety conditions a must
- Excellent communication and critical thinking skills required
- Proficiency with EXFO 715 OTDR or newer version and interpret results
- Performs testing of light levels with EXFO or similar power meter
- Must be able to distinguish different color fiber jackets
- Must be ETA Fiber Technician certified
- Requires 4 years fiber optic splicing and troubleshooting experience
- Troubleshoots back to and including ODNA
- Assists in field training of newer techs
- Successfully completes OLM activations and speed tests
- Edits and updates customer required documentation; as-built docs
- Provides leader with accurate and clear invoicing data
- Ability to perform hi-cap large fiber count ring work
- Experience working with loose tube, spider ribbon and other common cable types
- Successfully performs OLT augmentation and testing
- Schedules and coordinates with Cox Comm project planners
- Completes HFC mid-split node change and performs all necessary testing and documentation
Benefits
- Competitive compensation paid weekly.
- Best-in-class; Medical, Dental, Vision, and LTD/STD.
- 401(k) with company match, vested day-one.
- Employee Stock Purchase Plan [ESPP].
- Tuition Reimbursement.
- Paid Time Off, Holiday Pay, and Community Service Paid Time Off.
- Pet Coverage "For our Furry Friends"
- Legal Assistance Coverage
- Award winning safety programs.
- Overtime opportunities.
- Growth Opportunities.
- And more.
Pay
Competitive compensation paid weekly.
But note we already have "Competitive compensation paid weekly." in Benefits list as first item. That duplicates. The Benefits list includes that line. Actually the Benefits section originally: "Benefits Competitive compensation paid weekly. Best-in-class; Medical, Dental, Vision, and LTD/STD.401(k) with company match, vested day-one.Employee Stock Purchase Plan [ESPP].Tuition Reimbursement.Paid Time Off, Holiday Pay, and Community Service Paid Time Off.Pet Coverage "For our Furry Friends"Legal Assistance CoverageAward winning safety programs.Overtime opportunities.Growth Opportunities.And more."
So the first item is "Competitive compensation paid weekly." That's both a benefit and pay info. We could keep it in Benefits and not create a separate Pay section to avoid duplication. However guidelines: never create Pay/Schedule/Benefits sections unless the posting actually states them. Pay is stated (competitive compensation paid weekly). But we already have it in Benefits. Could we still have a Pay section? It would duplicate the same sentence. Might be considered redundant but not invented. However we should avoid duplication? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is not inventing, but it's repeating same info. Might be okay but better to avoid redundancy. Since we already have that line in Benefits, we could omit Pay section. However the instruction says "Prefer a few substantive sections over many thin ones." Having both Benefits and Pay might be thin. Better to keep Benefits only and not create Pay.
Thus we will have About the role, Requirements, Benefits.
Check if any other sections like Responsibilities needed? Not needed.
Thus final HTML fragment:
About the role
Talus Development is a full service utility contractor specializing in communications infrastructure including coax, fiber, voice, video and data. We install conduit structures, pull fiber/conductors, fiber/coax splicing/testing, cabinets and power supplies in subdivisions, multi-dwelling units, cell tower and small cell environments.
Requirements
- Must have a valid Arizona driver license and clean record
- Must possess ability to problem solve
- Proficiency with Excel and Adobe Acrobat
- Requires ability to lift 70 lbs
- Must be able to work on sites with stairs, ladders, bucket trucks, and uneven terrain
- Complete commitment to quality following industry and customer standards
- Requires attention to detail while following specific documented instruction
- Safely uses hand and small power tools
- Ability to prep and install fiber cables into various enclosure types; includes new and existing
- Fusion splice fibers within customer spec and parameters
- Read and interpret splice details and complete as-built docs accordingly
- Ability to troubleshoot down to element level
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a 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. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the job posting. Content: Job Overview (maybe a heading but we shouldn't repeat job title). The "Job Overview" is likely a section heading but we need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have "Job Overview" then "Job Requirements:" then a list of requirements. Then "Company Overview" describing Talus Development. Then "Benefits" list. Then EEO Statement etc which we need to remove. Also there is "Agency Statement" etc remove. We need to preserve substantive information: job overview, requirements, company overview, benefits. We need to decide which sections to use. "Job Overview" could map to "About the role" (or maybe "Responsibilities"?). The content after "Job Overview" is not given explicitly; the text shows "Job Overview Job Requirements:" maybe missing line break. Actually the snippet: "Job Overview Job Requirements: Must have a valid Arizona driver license and clean record..." It seems the job overview may be missing; maybe the overview is just the line "Job Overview". But we need to preserve substantive information; if there is no actual overview text besides the heading, we should not create a section with filler. So we might skip About the role if no content. But we have "Job Requirements:" which is a list of requirements. That maps to "Requirements" section. We have "Company Overview" which could map to "About the role"? Actually company overview is about the company, not role. Could be "About the role"? Not exactly. There's no specific heading for company overview; but we could put it under "About the role" maybe as description of the company? However guidelines: Use headings only for those specific categories. If we have company overview, we could treat it as "About the role" (since it's about the role context). Or we could omit if not fitting. But we need to preserve ALL substantive information; we cannot drop company overview. So we need to include it somewhere. The allowed headings include "About the role". That seems appropriate to include company overview and maybe role description. Since we don't have explicit role description besides requirements, we can put company overview under About the role. We also have Benefits list, which maps to Benefits section. Pay and Schedule: Not mentioned explicitly. There's "Competitive compensation paid weekly." That's about pay. So we have pay info: "Competitive compensation paid weekly." That's specific enough to create a Pay section. It mentions weekly pay but not amount. Is that considered filler? It's not "commensurate with experience" etc. It's a statement about compensation being competitive and paid weekly. That's substantive. So we should include Pay section. Schedule: Not mentioned. No schedule info. So we should not create Schedule section. Skills: Could be extracted from requirements but we already have Requirements section; we could also have Skills but we prefer few substantive sections. So we can combine skills into Requirements or maybe not create Skills. Qualifications: Could be similar to Requirements. We'll just have Requirements. Thus sections: About the role (company overview), Requirements (list), Benefits (list), Pay (statement). Possibly also Responsibilities? Not given explicitly; but many requirements are duties. Could map to Responsibilities. However we have a list of requirements that includes duties like "Ability to prep and install fiber cables..." etc. Those are responsibilities. So we could split: Responsibilities (duties) and Requirements (qualifications). But we need to avoid thin sections. Let's see if we can separate meaningfully. The list includes many items: driver license, problem solve, Excel, lift 70 lbs, work on sites, commitment to quality, attention to detail, safely uses tools, prep and install fiber cables, fusion splice, read splice details, troubleshoot, knowledge of NESC, communication, proficiency with EXFO 715 OTDR, performs testing, distinguish color jackets, ETA Fiber Technician certified, 4 years experience, troubleshoots back to ODNA, assists in field training, completes OLM activations, edits documentation, provides invoicing data, perform hi-cap large fiber count ring work, experience with cable types, performs OLT augmentation, schedules and coordinates with Cox Comm project planners, completes HFC mid-split node change, performs testing and documentation. These are a mix of qualifications and responsibilities. Could treat all as Requirements. That's fine. Thus we will have:
About the role
Talus Development is a full service utility contractor specializing in communications infrastructure including coax, fiber, voice, video and data. We install conduit structures, pull fiber/conductors, fiber/coax splicing/testing, cabinets and power supplies in subdivisions, multi-dwelling units, cell tower and small cell environments.
Requirements
- Must have a valid Arizona driver license and clean record
- Must possess ability to problem solve
- Proficiency with Excel and Adobe Acrobat
- Requires ability to lift 70 lbs
- Must be able to work on sites with stairs, ladders, bucket trucks, and uneven terrain
- Complete commitment to quality following industry and customer standards
- Requires attention to detail while following specific documented instruction
- Safely uses hand and small power tools
- Ability to prep and install fiber cables into various enclosure types; includes new and existing
- Fusion splice fibers within customer spec and parameters
- Read and interpret splice details and complete as-built docs accordingly
- Ability to troubleshoot down to element level based on traces and or testing results
- Knowledge of and ability to follow NESC and other state and local safety conditions a must
- Excellent communication and critical thinking skills required
- Proficiency with EXFO 715 OTDR or newer version and interpret results
- Performs testing of light levels with EXFO or similar power meter
- Must be able to distinguish different color fiber jackets
- Must be ETA Fiber Technician certified
- Requires 4 years fiber optic splicing and troubleshooting experience
- Troubleshoots back to and including ODNA
- Assists in field training of newer techs
- Successfully completes OLM activations and speed tests
- Edits and updates customer required documentation; as-built docs
- Provides leader with accurate and clear invoicing data
- Ability to perform hi-cap large fiber count ring work
- Experience working with loose tube, spider ribbon and other common cable types
- Successfully performs OLT augmentation and testing
- Schedules and coordinates with Cox Comm project planners
- Completes HFC mid-split node change and performs all necessary testing and documentation
Benefits
- Competitive compensation paid weekly.
- Best-in-class; Medical, Dental, Vision, and LTD/STD.
- 401(k) with company match, vested day-one.
- Employee Stock Purchase Plan [ESPP].
- Tuition Reimbursement.
- Paid Time Off, Holiday Pay, and Community Service Paid Time Off.
- Pet Coverage "For our Furry Friends"
- Legal Assistance Coverage
- Award winning safety programs.
- Overtime opportunities.
- Growth Opportunities.
- And more.
Pay
Competitive compensation paid weekly.
But note we already have "Competitive compensation paid weekly." in Benefits list as first item. That duplicates. The Benefits list includes that line. Actually the Benefits section originally: "Benefits Competitive compensation paid weekly. Best-in-class; Medical, Dental, Vision, and LTD/STD.401(k) with company match, vested day-one.Employee Stock Purchase Plan [ESPP].Tuition Reimbursement.Paid Time Off, Holiday Pay, and Community Service Paid Time Off.Pet Coverage "For our Furry Friends"Legal Assistance CoverageAward winning safety programs.Overtime opportunities.Growth Opportunities.And more." So the first item is "Competitive compensation paid weekly." That's both a benefit and pay info. We could keep it in Benefits and not create a separate Pay section to avoid duplication. However guidelines: never create Pay/Schedule/Benefits sections unless the posting actually states them. Pay is stated (competitive compensation paid weekly). But we already have it in Benefits. Could we still have a Pay section? It would duplicate the same sentence. Might be considered redundant but not invented. However we should avoid duplication? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is not inventing, but it's repeating same info. Might be okay but better to avoid redundancy. Since we already have that line in Benefits, we could omit Pay section. However the instruction says "Prefer a few substantive sections over many thin ones." Having both Benefits and Pay might be thin. Better to keep Benefits only and not create Pay. Thus we will have About the role, Requirements, Benefits. Check if any other sections like Responsibilities needed? Not needed. Thus final HTML fragment:About the role
Talus Development is a full service utility contractor specializing in communications infrastructure including coax, fiber, voice, video and data. We install conduit structures, pull fiber/conductors, fiber/coax splicing/testing, cabinets and power supplies in subdivisions, multi-dwelling units, cell tower and small cell environments.
Requirements
- Must have a valid Arizona driver license and clean record
- Must possess ability to problem solve
- Proficiency with Excel and Adobe Acrobat
- Requires ability to lift 70 lbs
- Must be able to work on sites with stairs, ladders, bucket trucks, and uneven terrain
- Complete commitment to quality following industry and customer standards
- Requires attention to detail while following specific documented instruction
- Safely uses hand and small power tools
- Ability to prep and install fiber cables into various enclosure types; includes new and existing
- Fusion splice fibers within customer spec and parameters
- Read and interpret splice details and complete as-built docs accordingly
- Ability to troubleshoot down to element level