Principal Network and Communications Engineer

for section headings. Use

• for lists. Use

  for prose. We must not include boilerplate like EEO, application process, etc. Remove those. We need to preserve all substantive information. So we need to include the descriptive paragraphs about role, responsibilities list, requirements, qualifications, skills, benefits, pay. Let's extract substantive content. About the role (intro): "Tacoma Public Utilities (TPU) is seeking an accomplished Principal Network Engineer to lead a team of talented network & communication systems Engineers in the design, implementation, and innovation of our critical Operational Technology (OT) infrastructure. In this role, you'll serve as the team lead, senior technical network strategist, and advisor for critical systems that support utility operations—delivering reliability and performance across control centers, substations, remote field environments, and other mission-critical systems. You’ll supervise a small team, guide large infrastructure projects from concept to execution, and play a vital role in the planning, procurement, and lifecycle management of TPU’s wide, local, and field area networks. Acting as a key bridge between infrastructure, cybersecurity, compliance, and business partners, you’ll help shape TPU’s long-term OT strategy while mentoring the next generation of engineers. This is a leadership-track engineering position designed for someone who thrives at the intersection of deep technical capability, operational excellence, and strategic foresight." That's the About the role. Responsibilities: combine Primary Responsibilities (Management) and Network Engineer responsibilities. We need to list each duty as

• . Could be many items. We'll need to capture them. Let's list from the text: Management: - Supports the workgroup Manager in the direct supervision of the Network and Communication Engineering team, also working in conjunction with other TPU staff on multiple highly complex integrated projects. - Provides training, mentorship, guidance, and support to junior personnel, and gives direction and support to contractors, consultants, internal engineers, and technicians by possessing and displaying a high level of technical knowledge. - Support performance reviews for subordinates and provide recommendations for hiring, terminations, and discipline. - Direct and assign tasks as needed to support projects, operations, and maintenance activities. - Provide technical and operational support to customers and business partners. - Recommend, procure, and coordinate training for staff to develop technical skill sets to support the workgroup technology portfolio and facilitate knowledge sharing to increase department resilience. - Assist with budget development for biannual capital projects and operations & maintenance (O&M) activities. - Responsible for managing project expenditures. Network Engineer: - Provide guidance and direction to other engineers and technicians in installing, commissioning, maintaining, and repairing IT/OT systems. - Subject matter expert and technical lead for TPU’s communication infrastructure. - Support and evaluate OT initiative project proposals. - Inspect projects and related activities to ensure compliance with the specifications, contracts, and applicable local, state, and federal codes. - Perform advanced level of engineering duties in the preparation, implementation, coordination, evaluation, and analysis of engineering projects. - Analyze data and coordinate projects with consultants and contractors. - Prepare drawings for reference documentation. - Prepare cost estimate, scheduling, material equipment purchases and delivery contracts. - Evaluate bids, administer contracts with consultants, manage project task progress, interpret and modify vendor design criteria. - Utilize a high level of technical expertise in the design, programming, and implementation of the operational control systems. - Prepare technical specifications, engineering calculations and plans for engineering projects. - Evaluate and coordinate maintenance, repair, installation, and design of computing architecture to support operational control systems. - Investigate and respond to incidents impacting operational control system functions. - Research, analyze, and perform advanced troubleshooting to address system malfunctions. - Serve as a technical advisor to the Utility Technology Architecture Board (UTAB). - Monitor technology advancements in the industry to ensure ongoing adherence to industry best practices. We'll output these as list items. Now Requirements (mandatory): - Bachelor's degree in electrical engineering or directly related field - 5 years of progressively responsible industrial controls experience - 1 year prior at senior, lead and/or supervisory level. - Equivalency: 1 year of experience = 1 year of education (maybe note) - Washington State Driver's License - Depending on assignment, some positions may require the ability to pass additional background checks and/or obtain additional certifications, with maintenance thereafter. We could combine. Now Qualifications (desired): - Advanced certifications such as VCP, CCNP, or CISSP. - Experience with OT infrastructure in regulated environments (e.g., NERC CIP). - Cisco ecosystem - Nokia MPLS ecosystem - System hardening and secure infrastructure design. - Backup, storage, and disaster recovery in OT environments. - Demonstrated ability to mentor others, lead large cross-functional initiatives, and participate in architectural governance. - Familiarity with ICS/SCADA systems, secure remote access, and segmented network design. We could also treat some as Skills. But we have a Skills heading optional. Could list technical skills: Cisco ecosystem, Nokia MPLS ecosystem, ICS/SCADA, secure remote access, segmented network design, system hardening, backup/storage/disaster recovery, etc. But to avoid duplication, maybe we put desired qualifications under Qualifications, and Skills under Skills (technical). However the desired qualifications already include many technical skills. Could split: Qualifications = advanced certs, ability to mentor, lead initiatives, architectural governance. Skills = technical expertise list. Let's decide: Qualifications heading: Desired Qualifications (advanced certs, ability to mentor, lead large cross-functional initiatives, participate in architectural governance). Also maybe include familiarity with ICS/SCADA etc? Might be better as Skills. Skills heading: Technical skills: OT infrastructure in regulated environments (NERC CIP), Cisco ecosystem, Nokia MPLS ecosystem, system hardening and secure infrastructure design, backup, storage, and disaster recovery in OT environments, ICS/SCADA systems, secure remote access, segmented network design. We'll keep both. Now Benefits: we have paragraph about Employee Benefits | City of Tacoma, then description of Tacoma Power etc. Also includes links to website etc. We need to preserve substantive info but remove navigation/legal/EEO etc. The benefits paragraph includes description of Tacoma Power, its hydroelectric nature, customers served, location, livable city, etc. Also includes links to website etc. Should we keep the links? They are part of benefits info (maybe not essential). The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the descriptive text about Tacoma Power, city, etc. The links maybe considered navigation? They are URLs to city website etc. Might be considered boilerplate? Not sure. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The URLs are not navigation per se but could be considered navigation. However they are part of the benefits description (they provide more info). Might be considered navigation but they are not typical navigation like menus. Safer to keep them? The instruction says remove navigation boilerplate. URLs could be considered navigation. I'd lean to remove them as they are not substantive content about benefits; they are just links. The descriptive text about Tacoma Power is substantive. We'll keep the descriptive sentences and drop the URLs. Thus Benefits section:

  Employee Benefits | City of Tacoma Tacoma Power Tacoma Power Is An Almost 100% Hydroelectric, Municipally-owned Public Power Utility, Located In Tacoma. We Serve Approximately 180,000 Customers As One Of The Three Operating Divisions Of Tacoma Public Utilities, Alongside Tacoma Water And Tacoma Rail. As One Of The Most Livable, Walkable Cities In The Country, You'll Find That Tacoma Is a Great Fit For All Interests With Places To Bike, Run, Hike, And Explore, The Perks Of a Big City, And The Charm Of a Small Town. We Welcome You To Take a Look At Our Website And Discover How The City Of Tacoma Can Make Your Next Career Move Part Of Our Combined Destiny

  maybe we can keep the sentence about website but drop the actual URLs. The sentence "We Welcome You To Take a Look At Our Website And Discover How The City Of Tacoma Can Make Your Next Career Move Part Of Our Combined Destiny" is okay without URLs. Now Pay: we have Pay Details: Annual Salary: $131,248.00 - $184,808.00. So

  Pay Details: Annual Salary: $131,248.00 - $184,808.00

  Now Schedule: none. Now we need to output HTML fragment with sections in order maybe: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We must not include empty sections. Let's craft. Use

  About the role

  then

  ...

  Responsibilities:

  Responsibilities