Statewide Permit Manager

The user wants me to reformat a job posting into clean, well-structured semantic HTML. I need to follow the rules: 1. Use

for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) 2. Use

• for lists of duties/requirements/benefits, and

  for prose 3. Do NOT repeat the job title as a heading 4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it 5. Preserve ALL substantive information; do NOT invent or summarize away detail 6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions 7. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text 8. Never create Pay/Schedule/Benefits sections unless the posting actually states them 9. Prefer a few substantive sections over many thin ones 10. Output ONLY the HTML fragment — no /, no markdown code fences Let me analyze the job posting content: The posting has: - Job title: "Statewide Permit Manager" (but I shouldn't repeat as heading) - Overview/description paragraph - "About The Role" section with metadata (salary range, employment status, background check, schedule code, location, recruiter, application deadline) - "Responsibilities And Duties" section with bullet points - "Minimum Qualifications" section with two tracks (Engineer and Non-engineer) and additional qualifications - "Why You Should Join Our Team" section with mission and culture - "The Agency" section with link - EEO Statement (boilerplate - should remove) I need to structure this into appropriate sections. Let me map: 1. About the role - could include the overview paragraph and maybe the metadata 2. Responsibilities - the duties list 3. Qualifications - the minimum qualifications (both tracks) 4. Benefits - the "Why You Should Join Our Team" section (mission, culture) 5. Pay - salary ranges are given for both tracks 6. Schedule - schedule code is given (AX – Career Service exempt) 6. Location - location is given But the rules say: "never create Pay/Schedule/Benefits sections unless the posting actually states them" - the posting does state salary ranges, schedule code, and benefits (mission, culture). So I can include them. However, "Prefer a few substantive sections over many thin ones." So I should combine where appropriate. Let me think about the structure: - About the role: overview paragraph + metadata (location, schedule, employment status, background check, recruiter, deadline) - but deadline might be considered application instruction? The rule says remove application instructions. But deadline is metadata. I'll include it in a short paragraph. - Responsibilities: the list of duties - Qualifications: the minimum qualifications (both engineer and non-engineer tracks, plus the additional qualifications) - Pay: salary ranges for both tracks - Schedule: schedule code - Benefits: mission and culture But the "Why You Should Join Our Team" is more about culture/mission than traditional benefits. Could be a "Benefits" section or "Culture" section. The rules mention "Benefits" as a possible heading. I'll use "Benefits" for that. Also, the "About The Role" heading in the original is a section heading. I should use

  for section headings. The original has "About The Role" and "Responsibilities And Duties" and "Minimum Qualifications" and "Why You Should Join Our Team". I'll map these to standard headings: "About the role", "Responsibilities", "Qualifications", "Benefits". Also add "Pay" and "Schedule" since they have specific info. Now, I need to output only HTML fragment, no markdown fences. Let me draft:

  About the role

  The Statewide Permit Manager oversees and proactively participates in the management, administration, and execution of the Department's statewide permitting programs within the Right of Way (ROW) and Regional Divisions. Reporting directly to the ROW Real Estate Manager and periodically to the Director of ROW, responsibilities include the overall improvement of UDOT permit programs, regional permit staffing, permit training, permit software implementations, and permitting-related standards of care. Key focus areas include special projects, disposition and application processes, customer support, Encroachment Permitting, Conditional Access Permits (CAP), Outdoor Advertising Control (OAC), Small Wireless Facilities (5G), Fiber Optics ROW support, Special Events, GIS permit records and data management, and third-party inspection oversight as needed.

  This position is open to both engineers and non-engineers. Full-time, career service exempt (at-will) position located at Calvin Rampton Building, 4501 South 2700 West, Taylorsville, Utah. Background check required. Recruiter: Porter Cook (pccook@utah.gov). Application deadline: 11/2/2026 (may close earlier if sufficient applicant pool).

  Responsibilities

  • Direct statewide permitting operations, programs (Encroachment, Conditional Access, Small Wireless, Outdoor Advertising), and team staff, including supervisory duties such as hiring, workload assignment, and performance evaluations.
  • Manage program budgets, fee collection, bonding ($100,000 continuous), liability insurance ($1M/$3M), and online permit portal technology, conducting fee evaluations at least every 5 years to maintain a break-even model.
  • Ensure compliance with federal and state regulations, Utah Administrative Codes (UAC R930-6 and UAC R930-7), stormwater requirements (SWPPP/MS4), and FHWA standards in collaboration with regional staff and leadership.
  • Partner with the Utah Attorney General's Office on permit appeals, administrative hearings, rule reviews, and final order drafts.
  • Coordinate workflow and align activities across regional permit offices (Regions 1–4), utilities, developers, and local government entities.
  • Manage legacy permit reviews, limited access modifications, Outdoor Advertising Control (OAC) compliance, constituent signage notifications, and variance requests.
  • Lead quarterly outreach meetings (at least two in-person, one remote annually) with each region for strategic alignment, policy updates, and training.
  • Serve as the primary statewide subject matter expert on ROW permitting, technical access guidelines, median toolkits, traffic control plans, and excavation standards for internal divisions, local governments, utilities, and legislative entities.
  • Prepare legal documentation, SULAs, drainage agreements, specifications, and special provisions.
  • Exercise final authority for permit approvals, denials, and revocations, defending determinations in administrative or legal proceedings.
  • Analyze complex access issues and lead operational enhancements, including digital permit portal upgrades.

  Qualifications

  Engineer Candidates

  • Registered as a professional engineer (PE) in Utah.
  • At least four (4) years of engineering experience following licensure as a PE.

  Non-engineer Candidates

  • A Bachelor's degree (or higher) from an accredited institution in a related field AND at least eight (8) years of professional relevant experience in Rights-Of-Way or a closely related field.
  • Note: Directly related professional experience may be substituted for the education requirement on a year-for-year basis (e.g., 12 years of total related experience if no degree is held).

  All Candidates

  • Demonstrated experience managing rights-of-way, access management programs, utility accommodation, or encroachment permitting in public entities, including knowledge of real estate principles and property management standards in transportation environments.
  • Thorough knowledge of Utah Administrative Code (UAC R930-6 Access Management, UAC R930-7 Utility Accommodation), UDOT standard specifications, traffic control standards, and bonding/insurance practices.
  • Proven ability to thrive and manage effectively in a high-volume public sector or transportation environment.

  Pay

  • Engineer Candidates: $48.10 - $76.27 per hour
  • Non-engineer Candidates: $45.53 - $72.25 per hour

  Schedule

  Schedule Code: AX – Career Service exempt (at-will)

  Benefits

  A Mission That Matters – At the Utah Department of Transportation (UDOT), our mission is to "Enhance quality of life through transportation." We help the traveling public get where they want, when they want, as safely as possible. By joining our team, you contribute to the framework of Good Health, Connected Communities, Better Mobility, and a Strong Economy for all of Utah.

  Our Culture and Values – We aren't just a state agency; we are a team built on an internal culture of Trust, Teamwork, and Flexibility. We live by the values of Respect, Integrity, and Caring.

  I should not include the EEO statement, the agency link, or the accommodations contact. Also, note that the original has "Salary Range: Based on qualifications" but then gives specific ranges for each track. I'll use the specific ranges. The "About The Role" section in the original includes metadata. I'll fold that into the About the role section. I used

  for sub-sections under Qualifications. The rules say use

  for section headings. It doesn't forbid

  for subsections. But to be safe, maybe I should keep all headings as

  ? The rules: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say not to use other heading levels. But to keep it simple, I could make "Engineer Candidates" and "Non-engineer Candidates" as

  ? That would create many sections. Better to keep as

  or just use within the list. However, the qualifications have two distinct tracks. I'll keep as

  for clarity, but the rule might expect only

  . Let me re-read: "use

  for section headings". It doesn't say exclusively. But to be safe, I'll make them

  as well? That would create many sections. The rule says "Prefer a few substantive sections over many thin ones." So maybe I should not split qualifications into subsections. Instead, I can list them under one Qualifications section with bullet points that indicate the track. But the qualifications are quite different for each track. I think using

  is acceptable semantic HTML. However, the instruction says "use

  for section headings". It might be okay to use

  for subsections. I'll keep as

  but if the system expects only

  , I might need to adjust. Since the user didn't explicitly forbid other heading levels, I'll keep. Alternatively, I can make them

  but that would create more sections. Let's see: "Qualifications" is a section, then "Engineer Candidates" and "Non-engineer Candidates" could be subsections. I'll keep as

  . Now, check for any boilerplate: EEO statement removed. "The Agency" link removed. Accommodations contact removed. Also, the