Fiber Optic Transport Engineer
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate, EEO, legal, application instructions, etc. Must preserve all substantive info. We need to parse the posting. Key sections: - About The Role: paragraph(s) describing role: "As a Fiber Optic Transport Engineer, you will manage the physical layer of the statewide Intelligent Transportation Systems (ITS) Network." Then "About The Role In this role, you will lead the architecture, design, provisioning, and advanced troubleshooting of high-capacity Layer 1, 2, and 3 optical transport systems. You will play a vital role in ensuring that UDOT's backbone network provides the capacity, redundancy, and low latency necessary to support critical transportation systems statewide." We can combine into a
. - Position Information: Salary Range: $33.37 - $59.01 FT/PT Status: Full Time Background Check: ... Schedule Code: B - Competitive Career Service (12 month probationary period) Location: Traffic Operations Center, 2060 South 2760 West, Salt Lake Recruiter: Jill Barela I jbarela@utah.gov Application Deadline: 09/29/2026 *This job posting may close at any time after the minimum advertising period of three (3) business days has passed, should a sufficient applicant pool be received. Applicants are encouraged to apply as early as possible. We need to include Pay and Schedule sections only if posting actually states them. Salary range is given, so Pay section should include that. Schedule: they gave Schedule Code: B - Competitive Career Service (12 month probationary period). That's schedule info. Also FT/PT Status: Full Time. So we can include Schedule section with that info. Location maybe not a heading; we can put in a short p under maybe About the role? But we have no heading for location; we could include in a paragraph under About the role or maybe a separate section like "Location" but not in allowed headings list. The instruction says use headings only for those specific headings; we can still include other info in
without heading. So we can put location, recruiter, deadline etc in a paragraph maybe under a generic "About the role"? Better to keep them in a paragraph after About the role but before Responsibilities. However we must not invent sections. We'll just include them as a
after the About the role heading. Responsibilities: list bullet points under "Key Responsibilities". There are subheadings: Network Architecture & Planning, Database & GIS Mapping Management, Coordination & Operations. Each with bullet points. We need to output
- for any list of duties/requirements/benefits. So we can create a
- with items for each bullet. Could also group by subheadings? The instruction: Use
- for any list of duties/requirements/benefits, and
for prose. So for Responsibilities we can have
Responsibilities
then a- with each duty as
- . We should preserve all details.
Qualifications: there is a "Qualifications" section with education/experience criteria. Also "Preferred Qualifications". Also "Knowledge, Skills, & Abilities". The instruction says we have headings for Qualifications, Skills. Possibly we need to separate Qualifications (education/experience) and Skills (knowledge, skills, abilities). Preferred qualifications could go under Qualifications or Skills? Probably under Qualifications as preferred. But we have a separate Skills heading for knowledge, skills, abilities. So we will:
-
Qualifications
: include education/experience requirement and preferred qualifications (maybe as a- ).
-
- Network Architecture & Planning: Analyze statewide fiber and communication needs, contribute to future system improvements, and assist with long-term system planning.
- Design fiber paths and monitoring systems to mitigate physical and optical threats (e.g., detecting fiber bends or unauthorized intrusion).
- Facilitate fiber optic designs and device configurations between UDOT and design consultants.
- Prepare splice details, connection test sheets, and acceptance testing documentation.
- Database & GIS Mapping Management: Maintain and update fiber management, Fiber Channel As-Built, and IP plan databases.
- Manage UDOT fiber mapping using ESRI and Bentley OpenComms platforms.
- Publish GIS mapping content and build custom visualization tools on the UPLAN platform.
- Coordination & Operations: Direct major fiber cutover operations and respond to system updates.
- Partner with UDOT Regions to coordinate Blue Stakes utility locating and permitting.
- Collaborate with local government entities, state agencies, and external consultants.
- Develop clear network documentation, including concepts, user guides, training manuals, and database queries.
- Advanced Optical Networking: Hands-on proficiency in configuring and optimizing multi-vendor optical networking hardware.
- CAD Drafting: Demonstrated proficiency with Computer-Aided Design (CAD) drafting tools for network planning.
- Optical Transport & Protocols: Thorough understanding of Optical Transport Networks (OTN), segment routing, and Layer 1–3 protocols across multi-vendor hardware platforms.
- Fiber Testing & Diagnostics: Mastery of active fiber metrics, including the ability to analyze advanced OTDR trace data and troubleshoot long-distance signal degradation.
- Geospatial Expertise: Practical understanding of GIS concepts and mapping tools, specifically ESRI/ArcGIS, Bentley OpenComms, or related spatial platforms.
- Network Documentation: Ability to author detailed technical guides, training manuals, database queries, and system architecture concepts.
- Technical Collaboration: Strong communication skills with a proven ability to collaborate effectively with regional teams, external consultants, and government agencies.
- Exceptional Health Coverage: We offer some of the most competitive medical premiums in the industry, including comprehensive family plans with very low out-of-pocket costs and HSA options.
- Retirement Choice: Flexibility between a 10% employer-paid 401(k) (no match required) or a Pension/401(k) Hybrid plan.
- Generous Paid Time Off: 12 paid holidays per year plus 8 hours of combined leave (4 annual and 4 sick) accrued each pay period.
- Dental & Vision: Multiple high-quality plan options to fit your needs.
Skills
: include Knowledge, Skills, & Abilities list. Benefits: there is a "Benefits At a Glance" section with bullet points. So we will haveBenefits
with- .
Pay: we have Salary Range: $33.37 - $59.01. So
Pay
withmaybe. Schedule: we have FT/PT Status: Full Time; Schedule Code: B - Competitive Career Service (12 month probationary period). So
Schedule
with. We must not include boilerplate like EEO statement, application instructions, etc. Also remove duplicated lines. We need to preserve all substantive information: location, recruiter, deadline maybe considered substantive? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Location, recruiter, deadline are not those; they are substantive. So we should keep them. Where to put? Could be in a
after About the role heading, maybe as a separate section like "Position Information" but not in allowed headings. Since we cannot create new headings beyond the list, we should embed them in a paragraph. Probably after About the role heading we can have a
containing: "Location: Traffic Operations Center, 2060 South 2760 West, Salt Lake. Recruiter: Jill Barela (jbarela@utah.gov). Application Deadline: 09/29/2026. This job posting may close at any time after the minimum advertising period of three (3) business days has passed, should a sufficient applicant pool be received. Applicants are encouraged to apply as early as possible." However the last sentence about posting may close is maybe considered application instruction? It's about the posting timeline; could be considered boilerplate? It's not EEO but it's about advertising period. Might be considered part of posting details; but it's not strictly prohibited. The instruction says remove application instructions. That sentence is not exactly instruction to apply but informs about closing. Might be okay to keep. But safer to remove that line? It's not exactly application instruction but it's about the posting. I'd keep location, recruiter, deadline. The line about closing may be considered boilerplate; I'd drop it to be safe. Now we need to ensure we don't repeat any content inadvertently. Let's draft:
About the role
As a Fiber Optic Transport Engineer, you will manage the physical layer of the statewide Intelligent Transportation Systems (ITS) Network. In this role, you will lead the architecture, design, provisioning, and advanced troubleshooting of high-capacity Layer 1, 2, and 3 optical transport systems. You will play a vital role in ensuring that UDOT's backbone network provides the capacity, redundancy, and low latency necessary to support critical transportation systems statewide. Location: Traffic Operations Center, 2060 South 2760 West, Salt Lake. Recruiter: Jill Barela (jbarela@utah.gov). Application Deadline: 09/29/2026.
Then Responsibilities:Responsibilities
Qualifications
A Bachelor’s degree (or higher) in Electrical Engineering, Computer Engineering, Telecommunications Engineering, Computer Science, Geography/GIS, Information Systems, or a related field, plus four (4) years of professional experience in a related technical area. Note: Directly related professional experience may be substituted for the education requirement on a year-for-year basis (e.g., 8 years of total related experience if no degree is held).
Preferred qualifications:
Skills
Benefits
Pay
Salary Range: $33.37 - $59.01
Schedule:Schedule
Full Time; Schedule Code: B - Competitive Career Service (12 month probationary period)
We must ensure no extra headings like "About The Role" with capital T? Use exactly "About the role". The instruction says usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should match case: "About the role". Good. Check we didn't include Requirements heading (none). We didn't include Requirements because no specific content besides qualifications; but we have Qualifications and Skills. That's fine. We removed boilerplate: EEO statement, application instructions, etc. We kept location, recruiter, deadline. Did we keep any duplicated lines? Not. Check that we didn't include "Background Check:" etc. That's substantive? It says "Background Check: You must successfully pass a criminal history check." That is substantive info about requirement.
- . We should preserve all details.
Qualifications: there is a "Qualifications" section with education/experience criteria. Also "Preferred Qualifications". Also "Knowledge, Skills, & Abilities". The instruction says we have headings for Qualifications, Skills. Possibly we need to separate Qualifications (education/experience) and Skills (knowledge, skills, abilities). Preferred qualifications could go under Qualifications or Skills? Probably under Qualifications as preferred. But we have a separate Skills heading for knowledge, skills, abilities. So we will:
-
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use
- for any list of duties/requirements/benefits, and