Right of Way Utility Specialist

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Apply today!" etc. Also remove "To request a copy of the position description..." etc. Also remove "What’s In It For You" maybe benefits? Actually benefits: "Work/life balance, 11 paid holidays a year, flexible work schedules, paid leave and so much more." Also mention Public Service Loan Forgiveness opportunity. Also mention salary range and PERS increase. Also schedule: "Work Monday through Friday, 8 a.m. to 5 p.m., with occasional hybrid work, overtime, evening/weekend work and extended travel as needed." Also mention travel frequently throughout Region 1 and occasionally statewide. Also field work. We need sections: About the role (maybe from "The Role" paragraph). Responsibilities (list of duties). Requirements (minimum qualifications). Qualifications (maybe special qualifications? Actually "Special Qualifications" is driving license). Skills (what we'd like to see). Benefits (work/life balance etc). Pay (salary range and PERS note). Schedule (work hours). Also maybe "Additional Information" but that's boilerplate (EEO etc) remove. We must not create sections with filler like "commensurate with experience". We have actual content. We must use

• for any list of duties/requirements/benefits. Use

  for prose. We must not include markdown fences. Just raw HTML. Let's extract content. Job Title: Right of Way Utility Specialist (not to be used as heading). Initial Posting Date etc maybe we can drop as metadata? 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

  with Initial Posting Date and Application Deadline and Agency Department etc? It says fold minor metadata into a short

  or drop it. Probably we can include a short paragraph with that info. But we need to preserve ALL substantive information. The dates are substantive? Might be considered metadata but still info. We'll include a short

  at top: "Initial Posting Date: 09/17/2026. Application Deadline: 10/01/2026. Agency: Department of Transportation. Position Type: Employee. Salary Range: $6,396 - $9,916." But salary range will be in Pay section; we might not repeat. Better to include only non-duplicated metadata: Initial Posting Date, Application Deadline, Agency Department, Position Type. We'll put in a

  . Now sections: About the role: The paragraph starting "The Role Our Engineering & Technical Services Branch is recruiting..." up to "Apply today!" but we should remove "Apply today!" as application instruction. Also remove "We provide a safe and reliable multimodal transportation system..." maybe that's part of role? It's more about agency mission; could be considered boilerplate? It's not EEO but still generic. Might keep as part of role? It's not specific to role. Safer to omit generic mission statement. Keep the description of role: "As part of our team, you will play a critical role in ensuring major transportation projects run smoothly by overseeing the planning, coordination, relocation and installation of utility infrastructure across Oregon. In this collaborative role, you will work directly with engineers, utility companies, municipalities and consultants to resolve complex utility conflicts, prepare relocation plans and budgets, and ensure timely, compliant integration into project schedules and contracts. By coordinating utilities efficiently, you will work to preserve the integrity of public and private utilities while protecting the safety of construction workers and the public by identifying utility conflicts. This important work also supports keeping projects on schedule and within budget." That's substantive. Responsibilities: From "A Day In The Life" bullet list (actually sentences separated by periods). We need to convert to list items. Sentences: - Manage utility activities, budgets, documentation, certification and compliance for assigned transportation projects. - Identify and resolve utility conflicts and coordinate relocations during project development. - Provide technical utility support, including plan reviews, utility plans, special provisions and design recommendations. - Coordinate utility relocations during construction and assist with resolving issues, claims and change orders. - Administer utility relocation reimbursement, including eligibility, costs and payment documentation. - Make technical and regulatory decisions regarding utility conflicts, relocations and compensable rights. - Build relationships and negotiate with utilities, municipalities, consultants and project teams to resolve issues and maintain schedules. - Travel frequently throughout Region 1 and occasionally statewide, depending on project needs. - Perform field work in varying terrain, weather, and construction environments. - Work Monday through Friday, 8 a.m. to 5 p.m., with occasional hybrid work, overtime, evening/weekend work and extended travel as needed. But the last one about work schedule could go to Schedule section. We'll keep schedule separate. Thus responsibilities list first 9 items (excluding schedule). We'll put in

  . Requirements: Minimum Qualifications bullet list (OR statements). We'll list as
  items. Minimum Qualifications: - Five years of experience in the field of engineering in project management or utility coordination; OR - An associate degree in the field of engineering (civil or transportation-related) and three years of engineering technician experience; OR - A bachelor’s degree in the field of engineering (civil or transportation-related) and two years of engineering technician experience; OR - An equivalent combination of experience, education, and training. - Note: Related experience, education, and training can include, but is not limited to construction management, forestry, geography, geology, geomatics, mathematics, physics, remote sensing and/or urban planning. We'll treat each as list item. Special Qualifications: Driving is essential function; must have valid US driver license and acceptable driving record; pre-employment driving record checks; license does not have to be issued in Oregon. We could put under Requirements or Qualifications? Probably under Requirements as special qualification. We'll include as list item. Skills (What we'd like to see): list of attributes. - Technical and analytical judgment in identifying, reviewing and resolving complex utility conflicts, including interpreting construction plans and recommending design alternatives. - Excellent communication and relationship-building skills when coordinating with utility companies, local agencies, consultants and project teams. - Demonstrated problem-solving and negotiation skills when resolving utility conflicts and developing practical relocation solutions. - Demonstrated organizational and project-management skills in coordinating multiple utility activities, maintaining documentation and meeting project schedules. - Demonstrated strong self-direction and adaptability in managing utility work independently while keeping management informed of issues, decisions and progress. We'll put as
  under Skills. Benefits: "Work/life balance, 11 paid holidays a year, flexible work schedules, paid leave and so much more. Learn more about working at the Oregon Department of Transportation and the benefits we offer." Also "Public Service Loan Forgiveness opportunity!" Also "Comprehensive and equitable base salary offer within the listed range." Actually that's pay. Also "Through an equal pay assessment, we will determine the salary offer using the information you provide in your submitted application materials." That's pay process. Also "The salary range listed is the non-PERS monthly salary range. If you are already a participating PERS member or once you become PERS eligible, the salary range will increase by 6%." That's pay detail. Thus Benefits section: work/life balance, 11 paid holidays, flexible work schedules, paid leave, Public Service Loan Forgiveness opportunity. Also maybe "Learn more about working at ODOT and the benefits we offer." That's generic; we can include as prose. We'll make list:
  • Work/life balance
  • 11 paid holidays a year
  • Flexible work schedules
  • Paid leave
  • Public Service Loan Forgiveness opportunity
  Pay: Salary range $6,396 - $9,916 (non-PERS monthly). Note about PERS increase 6% if eligible. Also equal pay assessment statement. We'll put as

  maybe with details. Schedule: Work Monday through Friday, 8 a.m. to 5 p.m., with occasional hybrid work, overtime, evening/weekend work and extended travel as needed. Also travel frequently throughout Region 1 and occasionally statewide depending on project needs. Perform field work in varying terrain, weather, and construction environments. Actually field work and travel could be responsibilities but we already have travel and field work in responsibilities. But schedule section should contain work hours and schedule specifics. We'll include: "Work Monday through Friday, 8 a.m. to 5 p.m., with occasional hybrid work, overtime, evening/weekend work and extended travel as needed." Also maybe note travel frequency? But that's already in responsibilities. We'll keep schedule just the work hours. Now we need to ensure we don't repeat content. Responsibilities already includes travel frequently throughout Region 1 and occasionally statewide, performing field work. So schedule section only about hours. Now we need to output HTML fragment: start with maybe a

  for metadata, then sections. We must not include or . Just fragment. Let's craft. Metadata

  : "Initial Posting Date: 09/17/2026. Application Deadline: 10/01/2026. Agency: Department of Transportation. Position Type: Employee." Now About the role:

  About the role

  then

  with the paragraph. Responsibilities:

  Responsibilities

  then
  • ... each. Requirements:

    Requirements

    then
    with items. Skills:

    Skills

    then
    . Benefits:

    Benefits

    then
    . Pay:

    Pay

    then

    with details. Schedule:

    Schedule

    then

    . Make sure no extra blank lines? It's fine. Check for any boilerplate left: We removed EEO, equal opportunity, scam warning, application instructions, "To request a copy...", "Need help?" etc. Also removed "Additional Information" etc. Also removed "We encourage people from all backgrounds..." that's EEO; removed. Also removed "If you are a current State of Oregon employee..." etc. Also removed "We do not offer visa sponsorship." etc. Also removed "The State of Oregon does not request or require your age..." etc. Also removed "You will be represented by..." etc. Also removed "ODOT is an Equal Employment Opportunity..." etc. Also removed "Applicants with a disability may request..." etc. Also removed "Oregon Relay Service..." etc. Also removed "Right of Way, Government Jobs" at end. Now verify we kept all substantive info: Role description, responsibilities list, minimum qualifications, special qualification (driving), skills list, benefits list, pay details, schedule. Also we kept metadata. Check if any substantive info missing: "Through an equal pay assessment, we will determine the salary offer using the information you provide in your submitted application materials. Please ensure your application materials are detailed, accurate and reflect your skills, experience (paid and unpaid) and education as they relate to the position when applying." That's about application process; we removed as application instructions. According to instruction, remove application instructions. So okay. Also "Comprehensive and equitable base salary offer within the listed range." That's part of pay; we included salary range and PERS note. The phrase "Comprehensive and equitable base salary offer within the listed range." is generic; we could include but it's not specific detail. Might be okay to