Field Technicians - Boston, NY State
About the role
and put that prose in. - Responsibilities: there is a "Responsibilities" heading with subpoints. We'll output
Responsibilities
then- each bullet.
- Requirements: there is "Skills Required" and "Educational Requirements Essential Skills & Experience". That could be "Requirements" or "Qualifications". We need to decide. The posting includes "Skills Required" with technical experience list, then "Educational Requirements Essential Skills & Experience" with bullet list of experience. That seems like qualifications/requirements. We'll put under
Requirements
(or Qualifications). Since we have both headings available, we need to avoid duplication. Choose one that best fits. The content includes required experience, skills, etc. That's more like "Requirements". We'll useRequirements
. Then we can list items. - Skills: there is also a "Skills Required" heading but we already used that content. Could also make a separate Skills section but that would duplicate. Better to combine into Requirements. The instruction: prefer a few substantive sections over many thin ones. So we can have About the role, Responsibilities, Requirements. Benefits? The posting mentions "Earn a competitive salary that reflects your experience and dedication" but not specific numbers, also mentions community connection, recognition, etc. That's benefits-ish but not specific benefits like health insurance, 401k. The instruction: never create Benefits section unless posting actually states them. It does mention "competitive salary", "community connection", "recognise our teammates". Those are somewhat benefits but vague. However they are specific statements: "Earn a competitive salary that reflects your experience and dedication", "Collaborate with supportive colleagues...", "Community connection, we frequently sponsor fundraisers...", "recognise our teammates and celebrate our wins." Those are benefits/perks. Could we make a Benefits section with those? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state competitive salary (pay) and community connection etc. But we need to avoid filler like "commensurate with experience". The phrase "competitive salary that reflects your experience and dedication" is somewhat vague but still a statement about pay. Should we include Pay section? It says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state competitive salary, so we could include Pay. However we must not include placeholder like "commensurate with experience". This is not exactly that but still vague. Might be okay. But we also have "Why You Will Love It Here:" which includes those benefits. Could treat as Benefits section. We also have Schedule? Not mentioned. So no Schedule. Thus we could have sections: About the role, Responsibilities, Requirements, Benefits, Pay. But we need to avoid duplication: Pay could be part of Benefits. Better to have Benefits section that includes competitive salary, community connection, recognition. Pay section maybe redundant. Since we have both Pay and Benefits headings available, we could split: Pay: competitive salary; Benefits: community connection, recognition, supportive colleagues. But the instruction: prefer a few substantive sections over many thin ones. So maybe combine into Benefits only, and not create Pay separate. Since we have a statement about salary, we can include it in Benefits. That seems reasonable. Thus sections: About the role, Responsibilities, Requirements, Benefits. Now we need to extract content. About the role: combine the introductory paragraphs before "Role Overview". The text: "Job Description And Benefits Entegro is at the forefront of Telecommunications technology, designing and deploying gigabit networks for future generations. We are proud to be industry leaders, working with communities, industry and service providers, to empower and connect people, homes and businesses, in urban and rural areas. Echoing our values, clients are at the heart of what we do both locally and internationally. They know they can depend on our expertise, experience, innovation and standard of service. With this our ambition is to build strong long-term client partnerships, where Entegro are a partner of choice, where we are trusted and understand our clients KPIs. Why You Will Love It Here: Earn a competitive salary that reflects your experience and dedication in our innovative workplace. Collaborate with supportive colleagues in a professional and welcoming environment. Community connection, we frequently sponsor fundraisers, teams and causes that are close to our hearts. And finally, we recognise our teammates and celebrate our wins. Join our team and be part of shaping the future of network innovation! Please Note: Only candidates permitted to work in the US will be considered for this role." We should preserve all substantive information, but remove boilerplate like "Please Note: Only candidates permitted to work in the US will be considered for this role." That's a requirement about eligibility; could be part of Requirements? It's a eligibility condition. Might be considered a requirement. But it's a note about work authorization. Could be included in Requirements. However the instruction says remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This note is about work eligibility, not exactly boilerplate but could be considered a requirement. I'd keep it in Requirements as a bullet: "Must be authorized to work in the US." Now the "Why You Will Love It Here:" part is benefits. Thus About the role: we can include the company description and mission etc, but exclude the "Why You Will Love It Here:" and the note. So About the role paragraph: "Entegro is at the forefront of Telecommunications technology, designing and deploying gigabit networks for future generations. We are proud to be industry leaders, working with communities, industry and service providers, to empower and connect people, homes and businesses, in urban and rural areas. Echoing our values, clients are at the heart of what we do both locally and internationally. They know they can depend on our expertise, experience, innovation and standard of service. With this our ambition is to build strong long-term client partnerships, where Entegro are a partner of choice, where we are trusted and understand our clients KPIs." Now Responsibilities: we have bullet list under Responsibilities heading with subheadings: Equipment Installation, Fibre & Cabling, Commissioning Support, Documentation. We need to extract each bullet point as list items. The text includes sentences; we can break into separate - items for each sentence or each bullet. Better to preserve the bullet points as they appear: Under Equipment Installation: list of sentences. We'll create
- for each sentence.
Let's extract:
Equipment Installation:
- Install Infinera (MTC-9 IOP Plus and GX-G42) and Ciena (6500 & Waveserver) equipment into customer racks.
- Install chassis, shelves, line cards, optics and associated hardware.
- Verify equipment installation against engineering designs and rack layouts.
- Install power, grounding and ancillary connections.
- Ensure all installations are completed to a high standard.
Fibre & Cabling:
- Install, patch and manage fibre optic cabling.
- Install structured copper cabling where required.
- Clean, inspect and certify fibre optic connections.
- Ensure correct cable routing, dressing and labelling.
- Maintain accurate cable management.
Commissioning Support:
- Support remote commissioning and Professional Services Engineers.
- Verify equipment readiness prior to commissioning.
- Assist with equipment power-up activities.
- Validate alarms, hardware status and LED indications.
- Perform optical power measurements and basic health checks.
- Support equipment acceptance testing and customer sign-off.
Documentation:
- Update rack elevations and as-built documentation.
- Record installed hardware, serial numbers and asset information.
- Complete installation and commissioning checklists.
- Capture installation photographs.
- Provide daily progress updates to the project team.
Now Requirements: we have "Skills Required" and "Educational Requirements Essential Skills & Experience". Also the note about US work eligibility.
Let's extract:
Skills Required:
- Required Technical Experience: Infinera MTC-9 IOP Plus & GX-G42 OR Ciena 6500 & Waveserver DWDM optical transport equipment
- Carrier-grade telecommunications equipment
- Fibre optic infrastructure
- Telecom racks and cabinets
- Power and grounding systems
- Experience with at least one of the following equipment sets: (maybe redundant) Actually the line: "Experience with at least one of the following equipment sets:" then list? It seems the previous line already listed. We'll keep as is.
Educational Requirements Essential Skills & Experience:
- Minimum 3 years' experience installing telecommunications or optical transport equipment.
- Experience working within carrier, service provider or data centre environments.
- Strong fibre optic handling, patching and cable management skills.
- Experience installing rack-mounted telecommunications equipment.
- Ability to interpret engineering drawings, rack elevations and installation documentation.
- Experience using optical test equipment, including optical power meters and Visual Fault Locators (VFLs).
- Strong health and safety awareness.
- Excellent attention to detail and documentation skills.
- Ability to work independently or as part of a project delivery team.
- Willingness to travel extensively.
Key Deliverables:
- Installation of Infinera MTC-9 IOP Plus and GX-G42 equipment and Ciena 6500 & Waveserver
- Rack build and equipment installation.
- Fibre installation, patching and cable management.
- Power, grounding and hardware verification.
- Support for commissioning and acceptance testing.
- Accurate as-built documentation.
- Successful handover to commissioning and operations teams.
Key Deliverables could be considered part of Requirements or maybe a separate section but we don't have a heading for that. Could incorporate into Requirements as additional bullets.
Thus Requirements section will combine all these bullet points.
Now Benefits: from "Why You Will Love It Here:" plus maybe the note about competitive salary etc.
Benefits bullets:
- Earn a competitive salary that reflects your experience and dedication in our innovative workplace.
- Collaborate with supportive colleagues in a professional and welcoming environment.
- Community connection, we frequently sponsor fundraisers, teams and causes that are close to our hearts.
- We recognise our teammates and celebrate our wins.
- Join our team and be part of shaping the future of network innovation! (maybe that's more call to action, but could be included.)
We should avoid duplicating the "Join our team..." as it's more of a call to action; but it's substantive. Could include as a bullet.
Now we need to output HTML fragment with
headings and
for prose,
- for lists.
We must not repeat job title as heading. Not include Job ID etc.
We must not include empty sections.
Thus final HTML:
About the role
Entegro is at the forefront of Telecommunications technology, designing and deploying gigabit networks for future generations. We are proud to be industry leaders, working with communities, industry and service providers, to empower and connect people, homes and businesses, in urban and rural areas. Echoing our values, clients are at the heart of what we do both locally and internationally. They know they can depend on our expertise, experience, innovation and standard of service. With this our ambition is to build strong long-term client partnerships, where Entegro are a partner of choice, where we are trusted and understand our clients KPIs.
Responsibilities
- Install Infinera
- for lists.
We must not repeat job title as heading. Not include Job ID etc.
We must not include empty sections.
Thus final HTML: