Senior Network Reliability Engineer

We need to output HTML fragment with sections: About the role? The posting includes "Company Alaska Airlines The Team ..." then "Role Summary". We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. We have: - About the role: Could be the "Role Summary" paragraph: "The Senior Network Reliability Engineer is a subject matter expert..." That's a prose description. - Responsibilities: The list of duties under "Key Duties". Many bullet-like sentences. Should be

• . - Requirements: The "Job-Specific Experience, Education & Skills Required" section includes required experience, education, certifications, etc. That's requirements. - Qualifications: Possibly overlapping with Requirements. But we can separate: maybe "Job-Specific Experience, Education & Skills Required" as Requirements; "Preferred" as Qualifications or Skills? Actually "Preferred" includes additional experience, familiarity, etc. Could be Skills. - Skills: Could be the preferred skills list. - Benefits: There's a "Total Rewards" section listing benefits: free standby travel, comprehensive well-being programs, generous 401k match, annual bonus plans, generous holiday and paid time off. Also mention "Alaska Airlines, Hawaiian Airlines and Horizon Air pay and benefits can vary..." but we have concrete benefits. - Pay: Salary Range $117,700-$176,550 / year plus details. So we have Pay. - Schedule: Not explicitly mentioned; maybe "Full-Time" under Employment Type. Could be schedule: Full-Time. But we need to only include Schedule if posting actually states it. It does state Employment Type Full-Time. So we can include Schedule section with Full-Time. We must not repeat job title as heading. No Job ID etc. We must remove boilerplate: EEO, regulatory, apply by date, etc. Also remove duplicated lines. We must preserve all substantive information; not invent or summarize away detail. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. Company Alaska Airlines The Team ... This is introductory fluff about company; could be part of About the role? Actually "About the role" maybe includes company description? But we can include a short paragraph about the team under About the role? The instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role heading and include the company/team description plus role summary. But we must not repeat job title as heading; we can still include role summary prose. Let's craft:

  About the role

  Guided by our purpose, core values, and leadership principles, we are creating an airline people love. Our corporate teams set the strategies and operational plans to ensure the success of our company. Whether we use our expertise in accounting, human resources, finance, planning, legal, marketing, or any of our operational divisions, our shared passion for travel and our guests is what motivates us to achieve excellence each day. If you share our passion for creating an airline people love, we want to hear from you.

  The Senior Network Reliability Engineer is a subject matter expert in network design. As an individual contributor, this role exercises considerable judgment to make decisions in executing life cycle processes for network equipment and provide recommendations to ensure optimal network utilization.

  That seems fine. Next Responsibilities: list of duties from "Key Duties". We'll extract each sentence as a list item. Let's list them: - Build, develop and implement automation to improve the reliability of the network meeting business SLA objectives. - Design, test and deliver scripts to automate manual operational work. - Implement perimeter network security controls and participate in incident response. - Act as a subject matter expert in the development of detailed network design artifacts including design, network diagrams, and low-level network configuration. - Manage operational sustainment of the network, including fielding user requests, system-initiated tickets, network incidents, and escalations, providing 24x7 on-call support as needed. - Manage and execute life cycle process for network equipment, including OS patching and upgrades. - Develop and implement resilient network backup and recovery to maintain reliable network operating system and tools (e.g., Solarwinds). - Review and react to monitoring alerts, logs, and alarms. - Help define best practices for network management systems, including recommendations for key performance indicators and alert thresholds. - Analyze data traffic patterns within network infrastructure, detecting operational problems and recommending changes to ensure optimal network utilization. - Install and configure enterprise network devices, including routers, switches, wireless access points, firewalls, and remote access concentrators; work directly with customers to resolve incidents. - Drive network deployment projects by creating work break-down structures, work instruction packages, and track to completion all network deliverables for the project. - Lead in the development and production of complex documentation for installation, network topology, and troubleshooting of communications hardware or software. - Regularly monitor all network devices to enable rapid issue resolution and reporting metrics as needed. We'll put each as
• . Next Requirements: Job-Specific Experience, Education & Skills Required. We need to capture required items: - 4 years of experience in: * Designing, deploying, and operating modern data center fabric architectures (EVPN-VXLAN), and managing enterprise-scale network environments using Juniper (Junos), Cisco (IOS/NX-OS), BGP routing, and Fortinet firewalls. * Configuring and managing F5 BIG-IP platforms (LTM & GTM), including load balancing, traffic management, and DNS/GSLB services in enterprise environments. * Designing and implementing cloud networking in Microsoft Azure, including VNets, VNet peering, load balancing, application gateways, and hybrid connectivity (VPN/ExpressRoute) or AWS. * Troubleshooting complex network issues across L2 through L7, including packet capture analysis, traffic flow validation, and root cause analysis in distributed environments. * Implementing and operating network observability, monitoring, alerting, and incident response processes, including driving faster MTTR improvements. - Bachelor’s degree with a focus in computer science or related area; or an additional 2 years in lieu of this degree. - Cisco Certified Network Professional (CCNP) and Cisco Certified Internetwork Expert (CCIE) certifications. - High school diploma or equivalent. - Minimum age of 18. - Must be authorized to work in the U.S. We'll put as list. Next Qualifications: maybe we can treat "Preferred" as Qualifications? Or Skills. The instruction includes Qualifications and Skills separate. We could put "Preferred" under Qualifications (or Skills). Let's decide: Qualifications could be the preferred experience items: 2 years of experience automating network infrastructure using tools like Ansible, Terraform, Python and GIT including development of reusable playbooks/modules and CI/CD pipelines; Familiarity with ITIL process and procedures; Experience with SolarWinds, Infoblox and similar network management tools; Knowledge of QoS, DSCP, and traffic engineering for VoIP; Knowledge and experience with Juniper MIST; Familiarity with cellular technology, theory and application, including modern mobile devices and apps; Working knowledge of infrastructure components; cloud, compute, database and storage; Experience diagnosing performance issues in complex distributed applications. We'll put those as list under Qualifications. Skills: Could be maybe the certifications? But we already used certifications in Requirements. Could leave Skills empty or not include. Better to not create empty sections. So we may omit Skills if no specific skill list beyond what's covered. However we have some skill-like items in Preferred; but we already used them for Qualifications. Could also split: Requirements = required experience/education/certifications; Qualifications = preferred experience; Skills = technical skills like automation tools, ITIL, etc. But we risk duplication. Let's follow the headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. For Qualifications and Skills we need to decide if we have distinct content. We could put "Preferred" under Qualifications, and under Skills we could list specific technical skills like automation tools (Ansible, Terraform, Python, GIT), ITIL, SolarWinds, Infoblox, QoS/DSCP, Juniper MIST, cellular tech, infrastructure components, diagnosing performance issues. That seems like skills. Thus: Qualifications: Preferred experience items (2 years automation, ITIL familiarity, experience with SolarWinds/Infoblox, etc.) Actually those are also skills. Hmm. Better: Qualifications = preferred experience (2 years automation, ITIL familiarity, experience with SolarWinds/Infoblox, etc.) Skills = specific technical skills: knowledge of QoS, DSCP, traffic engineering for VoIP; Juniper MIST; cellular technology; infrastructure components; diagnosing performance issues. But there is overlap. Let's just create Qualifications for the preferred experience bullet list (2 years automation, ITIL, experience with SolarWinds/Infoblox, etc.) and Skills for the remaining technical knowledge items. Let's list Preferred items from posting: "Preferred 2 years of experience automating network infrastructure using tools like Ansible, Terraform, Python and GIT including development of reusable playbooks/modules and CI/CD pipelines.Familiarity with ITIL process and procedures.Experience with SolarWinds, Infoblox and similar network management tools.Knowledge of QoS, DSCP, and traffic engineering for VoIP.Knowledge and experience with Juniper MIST.Familiarity with cellular technology, theory and application, including modern mobile devices and apps.Working knowledge of infrastructure components; cloud, compute, database and storage.Experience diagnosing performance issues in complex distributed applications." We can split: Qualifications: - 2 years of experience automating network infrastructure using tools like Ansible, Terraform, Python and GIT including development of reusable playbooks/modules and CI/CD pipelines. - Familiarity with ITIL process and procedures. - Experience with SolarWinds, Infoblox and similar network management tools. Skills: - Knowledge of QoS, DSCP, and traffic engineering for VoIP. - Knowledge and experience with Juniper MIST. - Familiarity with cellular technology, theory and application, including modern mobile devices and apps. - Working knowledge of infrastructure components; cloud, compute, database and storage. - Experience diagnosing performance issues in complex distributed applications. That seems reasonable. Now Benefits: list from Total Rewards: - Free stand-by travel privileges on Alaska Airlines, Hawaiian Airlines & Horizon Air - Comprehensive well-being programs including medical, dental and vision benefits - Generous 401k match program - Annual bonus plans - Generous holiday and paid time off We'll put as list. Pay: Salary Range $117,700-$176,550 / year plus details: "Pay will be based on multiple factors, including and not limited to location, relevant experience/level and skillset while balancing internal equity relative to other Alaska/Hawaiian/Horizon employees. Alaska/Hawaiian/Horizon is committed to fair, unbiased compensation along with competitive benefits in all locations in which we operate. Note: We don’t typically hire at the top of the range." We'll put as prose

  . Schedule: Employment Type Full-Time. Could also mention FLSA Status Exempt Regular/Temporary Regular but schedule is Full-Time. We'll put

  Full-Time

  . Now ensure we don't include boilerplate: EEO, regulatory, apply by date, etc. Also remove duplicated lines like "Apply by 7:00 PM Pacific Time on 9/18/2026" repeated. Now produce HTML fragment. Let's craft:

  About the role

  Guided by our purpose, core values, and leadership principles, we are creating an airline people love. Our corporate teams set the strategies and operational plans to ensure the success of our company. Whether we use our expertise in accounting, human resources, finance, planning, legal, marketing, or