Principal Network Architect / Subject Matter Expert (SME)

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (or Qualifications), Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We have location: Silver Spring, MD, partial remote work. That's schedule info? It's location and remote work. Could be Schedule? Not exactly schedule but work arrangement. Could include a "Location & Work Arrangement" but not in allowed headings. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have location and remote work; maybe we can put under Schedule? Not ideal. Could put under About the role? The posting includes location and remote work details. Could include a short

under About the role. Or we could create a Schedule section with remote work details. The posting says "This position is based in Silver Spring, MD, and allows for partial remote work." That's schedule/location. We'll include a Schedule section with that. Pay: The posting includes salary range but it's placeholder "xxx- xxx range". It says "The salary for this role is expected to be in the xxx- xxx range." That's not specific; it's placeholder. According to rules, we should NOT create Pay section unless posting actually states them. Since it's placeholder, we should omit Pay section. Benefits: There's a Benefits Snapshot with details. So include Benefits section. About the role: We have description about role, mission, etc. So include About the role. Responsibilities: Many bullet points. Include. Qualifications: There's "Experience and Education" plus "Technical Skills" etc. Could split into Requirements and Qualifications? The allowed headings: Requirements, Qualifications, Skills. We have experience/education, technical skills, communication, federal knowledge, certifications. We could map: Requirements = Experience and Education (maybe also Federal Knowledge?). Qualifications = maybe certifications? Skills = Technical Skills, Communication and Stakeholder Engagement. But we need to avoid duplication. Let's decide: - Requirements: Experience and Education (8 years experience, bachelor's degree, etc.) - Qualifications: Certifications preferred (CCIE etc.) plus maybe Federal Knowledge? Actually Federal Knowledge is more like knowledge area; could be under Skills? But we have Skills heading for technical skills. Could put Federal Knowledge under Skills as well. Better: Use Requirements for experience/education; Qualifications for certifications; Skills for technical skills, communication, federal knowledge. We must not repeat job title as heading. We must not include boilerplate like EEO, legal, etc. Remove navigation etc. We need to preserve all substantive information. So include all bullet points under responsibilities, qualifications, etc. We need to format as HTML:

About the role

then

... maybe multiple paragraphs. For lists use

• . We must not include markdown fences. Let's extract content. About the role: The initial paragraphs: "Position Description Valiant Solutions is seeking a Principal Network Architect / Subject Matter Expert (SME) to serve as the senior technical authority for a nationwide enterprise network operations consolidation supporting our government customer. Today the customer's network is managed in silos by separate vendors and internal teams across cloud, WAN, LAN, and security, which slows incident resolution and stalls modernization. This role owns the end-to-end design that replaces that model: a single operating picture spanning campus LAN, a carrier MPLS WAN reaching roughly 50 sites, two enterprise data centers, and two public cloud platforms. The architect sets technical direction for the agency's Zero Trust and IPv6 programs, grounded in NIST SP 800-207, TIC 3.0 reference architectures, and the federal IPv6 mandate in OMB M-21-07. This is a hands-on senior engineering role rather than a management position, and it serves as the final escalation point for Tier 3 architectural root cause analysis. Named one of the Best Places to Work in the Washington DC area for 12 consecutive years, Valiant is proud of our employee-centric culture and commitment to excellence. If you are interested in learning more about Valiant and this opportunity, we invite you to apply now! This position is based in Silver Spring, MD, and allows for partial remote work. Remote work requires a high level of trust in our employees, and we strictly adhere to the details outlined in our Remote Work Policy below." We should remove the invitation to apply now and maybe the Remote Work Policy mention? The policy details are later; we can keep location and remote work note. The "Remote work requires a high level of trust..." is part of policy; we could keep it under Schedule section. Thus About the role paragraph up to before "If you are interested..." maybe we keep that as part of About the role? It's promotional but still substantive. We'll keep. Responsibilities: Several bullet groups. We'll combine into one list? Could separate headings but not allowed. We'll just make a single
  with all responsibility items. List items: - Transition, Consolidation, and Assessment - Lead the assessment and validation of the device inventory across Cisco Catalyst and Nexus switches, Cisco Firepower Threat Defense firewalls, Cisco ISE appliances, and Ubiquiti UniFi and Meraki switches. - Direct the initial enterprise network assessment covering design, security, redundancy, and performance posture, and identify the gaps that block the target Zero Trust architecture. - Drive knowledge transfer from incumbent staff and government engineers, capturing undocumented operational procedures and reconciling them against existing network standard operating procedures. - Define the ITIL v4 aligned service management model that replaces tool-by-tool operation, and set the architecture for a consolidated monitoring dashboard aggregating MPLS WAN, data center fabric, and cloud telemetry. - Assess the existing ServiceNow ITSM workflow used for network service requests and deliver written recommendations through the customer's review process. - Network Design, Redundancy, and Tier 3 Engineering - Conduct the network design review within the first 90 days of performance and annually thereafter, identifying single points of failure in internet, DMZ, and cloud egress paths. - Verify that the hot-hot aggregation design across the Seattle and Ashburn data centers survives the loss of any single circuit or backbone device without dropping internet or cloud connectivity. - Plan and evaluate failover testing with the security team to confirm that backup paths activate automatically. - Serve as the Tier 3 escalation authority for architectural root cause analysis, complex code upgrades, and disaster recovery execution. - Review and approve Methods of Procedure before Change Control Board submission, including rollback plans and risk assessments, to protect the change success rate standard. - Multi-Cloud and Carrier Architecture - Own BGP traffic engineering across the carrier MPLS backbone, transport circuits, and cloud interconnects to prevent suboptimal routing between on-premise and cloud workloads. - Confirm that all cloud connectivity conforms to TIC 3.0 reference architectures so that cloud traffic is inspected and logged as required. - Set Quality of Service policy on customer edge routers so that mission data and VoIP traffic receive priority across the wide area network. - Act as the senior technical escalation point in carrier disputes, directing intrusive testing windows and vendor management escalation during circuit outages. - Modernization and IPv6 Transition - Own the enterprise IPv6 transition plan and drive the enterprise from a roughly 5 percent dual-stacked endpoint baseline toward the 80 percent target, including cloud environments that are currently IPv4-only. - Manage the interim dual-stack environment, keeping OSPFv3 and MP-BGP routing tables synchronized and stable. - Maintain the enterprise IPv6 addressing plan and prefix allocation across sites, data centers, and cloud tenancies. - Design NAT64 and DNS64 translation services if legacy IPv4-only applications are identified during migration. - Identify End-of-Life and End-of-Support hardware and propose replacement paths that support TrustSec and native IPv6. - Lead quarterly architecture reviews that adapt the design to changing traffic patterns such as increased cloud egress. We could keep headings inside list? Not allowed; we could just list items without subheadings. But we need to preserve all info; we can keep the subheadings as part of list item text (bold?). We'll just include them as plain text within
  • . Qualifications: Experience and Education. - 8 years of progressive network architecture experience, including enterprise LAN, WAN, and data center design. - Bachelor's degree in Computer Science, Information Systems, Mathematics, Engineering, or a related field. - Four additional years of relevant experience may substitute for the degree. - Demonstrated experience acting as the senior technical authority for a nationwide or multi-site enterprise network. - Experience consolidating fragmented, multi-vendor network operations into a single operating model. Skills: Technical Skills, Communication and Stakeholder Engagement, Federal Knowledge. We'll combine into one list maybe with subheadings inside items. Technical Skills: - Deep routing and switching expertise across OSPF, OSPFv3, BGP, MP-BGP, and EIGRP redistribution in carrier-managed environments. - Carrier-grade WAN design, including MPLS service management, Quality of Service policy, and circuit performance analysis using latency, jitter, packet loss, and availability metrics. - Data center fabric design with Cisco Catalyst and Nexus platforms, including Data Center Interconnect tuning for storage replication. - Multi-cloud network architecture across Oracle Cloud Infrastructure and Google Cloud Platform, including dedicated interconnect and hybrid routing design. - Zero Trust network design incorporating Cisco Identity Services Engine, TrustSec Security Group Tags, and identity-based firewall policy. - IPv6 transition planning at enterprise scale, including dual-stack operations, addressing plans, and translation gateways. - Familiarity with Infrastructure as Code practice using Terraform, sufficient to set standards for the engineering team. Communication and Stakeholder Engagement: - Written and verbal communication skills sufficient to explain network and security concepts to both engineers and non-technical government stakeholders. - Ability to brief senior government leadership, including the Contracting Officer's Representative and Technical Lead, on incident root cause, risk, and remediation. - Clear technical writing for Methods of Procedure, topology diagrams, standard operating procedures, and monthly status report inputs. - Ability to work as a contractor employee in a non-personal services environment, identifying as contractor staff in all meetings, correspondence, and system records. Federal Knowledge: - Working knowledge of federal network security direction, including Zero Trust Architecture (NIST SP 800-207), Trusted Internet Connection (TIC) 3.0 reference architectures, and the IPv6 mandate under OMB M-21-07. - Familiarity with NIST SP 800-53 Rev. 5 security and privacy controls as they apply to network and boundary protection. - Understanding of HSPD-12 identity credentialing and its enforcement in network access decisions. - Awareness of Section 508 accessibility requirements (WCAG 2.0 AA) as they apply to contract deliverables. - Experience operating inside a federal change control process, with government-approved documentation and deliverable acceptance criteria. Certifications (Qualifications? Actually "The Following Certifications Are Preferred" list). We'll put under Qualifications maybe separate list. Qualifications (Certifications): - CCIE Enterprise Infrastructure or CCNP Enterprise. - CCNP Security or Cisco Certified Specialist – Security Identity Management Implementation (300-715 SISE). - A cloud networking certification relevant to the environment, such as (GCP) Google Professional Cloud Network Engineer or (OCI) Oracle Cloud Infrastructure Architect. - ITIL v4 Foundation certification is preferred, given the requirement to unify operations under an ITSM framework. We could also include "About Valiant Solutions" but that's company description; maybe under About the role? Not needed. Could be omitted as not role-specific. The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it." About Valiant Solutions is company info; could be considered minor metadata? Might be okay to include under About the role? But we already have About the role section; we could add a short paragraph about V