Wireless Network Operations Center (NOC) Lead
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate etc. The posting includes no explicit Pay or Schedule sections, so we should not create them.
We need to decide sections: About the role (maybe "About the role" heading). Responsibilities? The description includes responsibilities: coordinating scheduling, lead POC, coordinate training, provide documentation. Could be under "Responsibilities". Requirements: list of lead and supervise etc. Required Skills: list of qualifications. Preferred Skills: list. Benefits: list.
We must only include sections when posting has real specific content. All these have content.
We need to ensure we don't include filler like "commensurate with experience". Not present.
We need to output only HTML fragment, no /, no markdown fences.
Let's extract content.
First paragraph: "This program is required to provide ongoing support for the agencies Network Operations Center (NOC) and Wireless Network Operations Center (WNOC), which are critical components within the Office of Information and Technology (OIT), Enterprise Infrastructure and Operations Directorate (EIOD), and Network Operations Division (NOD). These centers perform real-time monitoring, proactive maintenance, incident detection and response, problem resolution, and network performance reporting across the agencies nationwide enterprise. They ensure network stability, availability, and the rapid escalation and resolution of technical issues."
Second: "Position Description: Responsible for coordinating the scheduling for the WNOC group supporting Cellular Over the Horizon Enforcement Network (COTHEN) and Land Mobile Radio (LMR). Serve as the lead point of contact (POC) for government and customers seeking technical assistance. Coordinate training for new contract staff and provide documentation for daily, weekly and monthly reports from the ticketing system and databases."
That's the role description.
Then "Requirements" heading in original: list bullet points after "Requirements". Let's capture each line:
- Lead and supervise NOC technicians and engineers, providing guidance, mentorship, and performance feedback
- Ensure 24/7 operational coverage and effective staffing of the wireless NOC team
- Develop and implement standard operating procedures (SOPs) and escalation protocols
- Oversee real-time monitoring of wireless network performance, ensuring minimal downtime and optimal service quality
- Lead incident response efforts for network outages, performance degradations, and security incidents
- Coordinate with field engineers, network engineers, and vendors to resolve escalated network issues
- Prepare and present regular performance, capacity, and incident reports to management
- Maintain accurate logs of incidents, escalations, maintenance, and network changes
- Identify recurring network issues and implement process improvements to reduce future incidents
- Collaborate with engineering teams on network upgrades, expansions, and migrations
- Ensure all changes follow established change management and risk mitigation processes
- Participate in planning and execution of network optimization projects
- Ensure adherence to network security policies, industry standards, and regulatory requirements
- Conduct periodic audits to verify compliance with operational procedures and security standards
Then "Required Skills:" list:
- A minimum of five (5) years' relevant experience in Tier 1 support operations
- Bachelor's degree in related technical fields such as Management Information Systems, Computer Science, Engineering, IT, Networking and Telecommunications
- Relevant certifications such as ITIL v3, CompTIA, CCNA
- Strong understanding of network fundamentals, including TCP/IP, routing protocols, network topology, and basic troubleshooting techniques
- Hands-on experience with network monitoring tools and ticketing systems
- Excellent problem-solving and analytical skills to identify and resolve network issues efficiently
- Effective communication skills for interacting with customers, technical teams, and management
- Deep knowledge of wireless network technologies (e.g., LTE, 5G, Wi-Fi)
- Experience with network monitoring tools (e.g., SolarWinds, NetScout, Nagios, or equivalent)
- Proficiency in troubleshooting network performance, latency, and connectivity issues
- Familiarity with network protocols, SNMP, VoIP, TCP/IP, and routing/switching concepts
- Knowledge of network security best practices and incident response procedures
- Experience managing NOC teams or network operations teams
- Ability to prioritize tasks in high-pressure environments and delegate effectively
- Strong project management skills for coordinating upgrades, maintenance, and troubleshooting efforts
- Strong diagnostic and root-cause analysis skills
- Ability to interpret network data, logs, and reports to drive decision-making
Then "Preferred Skills" list:
- Familiarity with ITIL processes, including Incident, Problem, and Change Management
- Familiarity with network virtualization technologies (e.g., SD-WAN, NFV).
- Knowledge of cloud-based network monitoring and management platforms
- Hands-on experience with 5G NR architecture, LTE, and Wi-Fi 6/6E technologies
- Experience with Cellular Over the Horizon Enforcement Network (COTHEN) and Land Mobile Radio (LMR)
- Ability to use analytics tools to identify network trends, performance issues, and capacity planning
- Experience generating dashboards and KPI reports for leadership.
- Familiarity with Lean, Six Sigma, or other continuous improvement methodologies
Then "Benefits" list:
- Medical
- Dental
- Vision
- AD&D
- STD
- LTD
- Company paid Life Insurance
- 401k with employer contribution
- Paid Time Off
- Pet Insurance
Also "SES provides a competitive salary and the following benefits:" preceding list. The salary is mentioned but not specific; we should not create Pay section because no specific salary figure. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits are stated, so we can include Benefits section. Pay is not stated with a number, just "competitive salary". That is vague; we should not create Pay section because it's not specific. So we omit Pay.
Now we need to format.
We'll have sections:
About the role
with paragraphs combining the two paragraphs? Could be one containing both sentences.
Better: first paragraph about program, second about position description. Could combine into one
with both sentences.
Then
Responsibilities
maybe? But the description already includes responsibilities. However we already used About the role for description. Could we treat About the role as overview and Responsibilities as the bullet list of duties? But the posting didn't separate responsibilities list; it's embedded in Position Description. The instruction: Use - for any list of duties/requirements/benefits. The Position Description is not a list but prose. So we keep as
.
We could still have a Responsibilities section with the same prose if we want, but we should not duplicate content. Better to have About the role (overview) and Responsibilities (the specific duties). However the posting only gave those duties in the Position Description paragraph; we could treat that as responsibilities. But then About the role would be empty or just generic. To avoid filler, we should only include sections with real specific content. So we can have a single section "About the role" containing the prose. Or we could have "Responsibilities" containing the prose. Which is more appropriate? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples. We can choose whichever fits. Since we have a description of role, we could put it under "About the role". That seems fine.
Then we have Requirements (list). Then Required Skills (list). Then Preferred Skills (list). Then Benefits (list).
We must not include "Qualifications" separate if we already have Required Skills; but we could combine Required Skills as Qualifications. However they gave example headings; we can use "Requirements" for the lead/supervise etc list, and "Skills" for the Required Skills list? But they also have "Qualifications". Might be better to have "Requirements" for the lead/supervise etc (duties) and "Required Skills" for the skill list. However the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map:
- About the role: overview paragraph.
- Responsibilities: maybe not needed if we already put overview there; but we could split: About the role = overview of program; Responsibilities = the position description duties (coordinate scheduling, lead POC, training, documentation). That would be a list? It's not a list but could be a
. That's okay.
- Requirements: the lead/supervise etc list (the bullet points after "Requirements").
- Qualifications: maybe the Required Skills list (education, experience, certifications). Or we could call it "Skills". But we have both Required Skills and Preferred Skills. Could treat Required Skills as "Skills" and Preferred Skills as "Preferred Skills" (but not in example headings). However we can still add a heading "Preferred Skills" as it's specific content. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we can add Preferred Skills heading.
Thus we need to decide mapping that avoids duplication and uses appropriate headings.
Let's outline:
About the role
This program is required to provide ongoing support for the agencies Network Operations Center (NOC) and Wireless Network Operations Center (WNOC), which are critical components within the Office of Information and Technology (OIT), Enterprise Infrastructure and Operations Directorate (EIOD), and Network Operations Division (NOD). These centers perform real-time monitoring, proactive maintenance, incident detection and response, problem resolution, and network performance reporting across the agencies nationwide enterprise. They ensure network stability, availability, and the rapid escalation and resolution of technical issues.
Responsibilities
Responsible for coordinating the scheduling for the WNOC group supporting Cellular Over the Horizon Enforcement Network (COTHEN) and Land Mobile Radio (LMR). Serve as the lead point of contact (POC) for government and customers seeking technical assistance. Coordinate training for new contract staff and provide documentation for daily, weekly and monthly reports from the ticketing system and databases.
Requirements
- Lead and supervise NOC technicians and engineers, providing guidance, mentorship, and performance feedback
- Ensure 24/7 operational coverage and effective staffing of the wireless NOC team
- Develop and implement standard operating procedures (SOPs) and escalation protocols
- Oversee real-time monitoring of wireless network performance, ensuring minimal downtime and optimal service quality
- Lead incident response efforts for network outages, performance degradations, and security incidents
- Coordinate with field engineers, network engineers, and vendors to resolve escalated network issues
- Prepare and present regular performance, capacity, and incident reports to management
- Maintain accurate logs of incidents, escalations, maintenance, and network changes
- Identify recurring network issues and implement process improvements to reduce future incidents
- Collaborate with engineering teams on network upgrades, expansions, and migrations
- Ensure all changes follow established change management and risk mitigation processes
- Participate in planning and execution of network optimization projects
- Ensure adherence to network security policies, industry standards, and regulatory requirements
- Conduct periodic audits to verify compliance with operational procedures and security standards
Skills
for prose. We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate etc. The posting includes no explicit Pay or Schedule sections, so we should not create them. We need to decide sections: About the role (maybe "About the role" heading). Responsibilities? The description includes responsibilities: coordinating scheduling, lead POC, coordinate training, provide documentation. Could be under "Responsibilities". Requirements: list of lead and supervise etc. Required Skills: list of qualifications. Preferred Skills: list. Benefits: list. We must only include sections when posting has real specific content. All these have content. We need to ensure we don't include filler like "commensurate with experience". Not present. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. First paragraph: "This program is required to provide ongoing support for the agencies Network Operations Center (NOC) and Wireless Network Operations Center (WNOC), which are critical components within the Office of Information and Technology (OIT), Enterprise Infrastructure and Operations Directorate (EIOD), and Network Operations Division (NOD). These centers perform real-time monitoring, proactive maintenance, incident detection and response, problem resolution, and network performance reporting across the agencies nationwide enterprise. They ensure network stability, availability, and the rapid escalation and resolution of technical issues." Second: "Position Description: Responsible for coordinating the scheduling for the WNOC group supporting Cellular Over the Horizon Enforcement Network (COTHEN) and Land Mobile Radio (LMR). Serve as the lead point of contact (POC) for government and customers seeking technical assistance. Coordinate training for new contract staff and provide documentation for daily, weekly and monthly reports from the ticketing system and databases." That's the role description. Then "Requirements" heading in original: list bullet points after "Requirements". Let's capture each line: - Lead and supervise NOC technicians and engineers, providing guidance, mentorship, and performance feedback - Ensure 24/7 operational coverage and effective staffing of the wireless NOC team - Develop and implement standard operating procedures (SOPs) and escalation protocols - Oversee real-time monitoring of wireless network performance, ensuring minimal downtime and optimal service quality - Lead incident response efforts for network outages, performance degradations, and security incidents - Coordinate with field engineers, network engineers, and vendors to resolve escalated network issues - Prepare and present regular performance, capacity, and incident reports to management - Maintain accurate logs of incidents, escalations, maintenance, and network changes - Identify recurring network issues and implement process improvements to reduce future incidents - Collaborate with engineering teams on network upgrades, expansions, and migrations - Ensure all changes follow established change management and risk mitigation processes - Participate in planning and execution of network optimization projects - Ensure adherence to network security policies, industry standards, and regulatory requirements - Conduct periodic audits to verify compliance with operational procedures and security standards Then "Required Skills:" list: - A minimum of five (5) years' relevant experience in Tier 1 support operations - Bachelor's degree in related technical fields such as Management Information Systems, Computer Science, Engineering, IT, Networking and Telecommunications - Relevant certifications such as ITIL v3, CompTIA, CCNA - Strong understanding of network fundamentals, including TCP/IP, routing protocols, network topology, and basic troubleshooting techniques - Hands-on experience with network monitoring tools and ticketing systems - Excellent problem-solving and analytical skills to identify and resolve network issues efficiently - Effective communication skills for interacting with customers, technical teams, and management - Deep knowledge of wireless network technologies (e.g., LTE, 5G, Wi-Fi) - Experience with network monitoring tools (e.g., SolarWinds, NetScout, Nagios, or equivalent) - Proficiency in troubleshooting network performance, latency, and connectivity issues - Familiarity with network protocols, SNMP, VoIP, TCP/IP, and routing/switching concepts - Knowledge of network security best practices and incident response procedures - Experience managing NOC teams or network operations teams - Ability to prioritize tasks in high-pressure environments and delegate effectively - Strong project management skills for coordinating upgrades, maintenance, and troubleshooting efforts - Strong diagnostic and root-cause analysis skills - Ability to interpret network data, logs, and reports to drive decision-making Then "Preferred Skills" list: - Familiarity with ITIL processes, including Incident, Problem, and Change Management - Familiarity with network virtualization technologies (e.g., SD-WAN, NFV). - Knowledge of cloud-based network monitoring and management platforms - Hands-on experience with 5G NR architecture, LTE, and Wi-Fi 6/6E technologies - Experience with Cellular Over the Horizon Enforcement Network (COTHEN) and Land Mobile Radio (LMR) - Ability to use analytics tools to identify network trends, performance issues, and capacity planning - Experience generating dashboards and KPI reports for leadership. - Familiarity with Lean, Six Sigma, or other continuous improvement methodologies Then "Benefits" list: - Medical - Dental - Vision - AD&D - STD - LTD - Company paid Life Insurance - 401k with employer contribution - Paid Time Off - Pet Insurance Also "SES provides a competitive salary and the following benefits:" preceding list. The salary is mentioned but not specific; we should not create Pay section because no specific salary figure. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits are stated, so we can include Benefits section. Pay is not stated with a number, just "competitive salary". That is vague; we should not create Pay section because it's not specific. So we omit Pay. Now we need to format. We'll have sections:
About the role
with paragraphs combining the two paragraphs? Could be onecontaining both sentences. Better: first paragraph about program, second about position description. Could combine into one
with both sentences. Then
Responsibilities
maybe? But the description already includes responsibilities. However we already used About the role for description. Could we treat About the role as overview and Responsibilities as the bullet list of duties? But the posting didn't separate responsibilities list; it's embedded in Position Description. The instruction: Use- for any list of duties/requirements/benefits. The Position Description is not a list but prose. So we keep as
. We could still have a Responsibilities section with the same prose if we want, but we should not duplicate content. Better to have About the role (overview) and Responsibilities (the specific duties). However the posting only gave those duties in the Position Description paragraph; we could treat that as responsibilities. But then About the role would be empty or just generic. To avoid filler, we should only include sections with real specific content. So we can have a single section "About the role" containing the prose. Or we could have "Responsibilities" containing the prose. Which is more appropriate? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples. We can choose whichever fits. Since we have a description of role, we could put it under "About the role". That seems fine. Then we have Requirements (list). Then Required Skills (list). Then Preferred Skills (list). Then Benefits (list). We must not include "Qualifications" separate if we already have Required Skills; but we could combine Required Skills as Qualifications. However they gave example headings; we can use "Requirements" for the lead/supervise etc list, and "Skills" for the Required Skills list? But they also have "Qualifications". Might be better to have "Requirements" for the lead/supervise etc (duties) and "Required Skills" for the skill list. However the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map: - About the role: overview paragraph. - Responsibilities: maybe not needed if we already put overview there; but we could split: About the role = overview of program; Responsibilities = the position description duties (coordinate scheduling, lead POC, training, documentation). That would be a list? It's not a list but could be a
. That's okay. - Requirements: the lead/supervise etc list (the bullet points after "Requirements"). - Qualifications: maybe the Required Skills list (education, experience, certifications). Or we could call it "Skills". But we have both Required Skills and Preferred Skills. Could treat Required Skills as "Skills" and Preferred Skills as "Preferred Skills" (but not in example headings). However we can still add a heading "Preferred Skills" as it's specific content. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we can add Preferred Skills heading. Thus we need to decide mapping that avoids duplication and uses appropriate headings. Let's outline:
About the role
This program is required to provide ongoing support for the agencies Network Operations Center (NOC) and Wireless Network Operations Center (WNOC), which are critical components within the Office of Information and Technology (OIT), Enterprise Infrastructure and Operations Directorate (EIOD), and Network Operations Division (NOD). These centers perform real-time monitoring, proactive maintenance, incident detection and response, problem resolution, and network performance reporting across the agencies nationwide enterprise. They ensure network stability, availability, and the rapid escalation and resolution of technical issues.
Responsibilities
Responsible for coordinating the scheduling for the WNOC group supporting Cellular Over the Horizon Enforcement Network (COTHEN) and Land Mobile Radio (LMR). Serve as the lead point of contact (POC) for government and customers seeking technical assistance. Coordinate training for new contract staff and provide documentation for daily, weekly and monthly reports from the ticketing system and databases.
Requirements
- Lead and supervise NOC technicians and engineers, providing guidance, mentorship, and performance feedback
- Ensure 24/7 operational coverage and effective staffing of the wireless NOC team
- Develop and implement standard operating procedures (SOPs) and escalation protocols
- Oversee real-time monitoring of wireless network performance, ensuring minimal downtime and optimal service quality
- Lead incident response efforts for network outages, performance degradations, and security incidents
- Coordinate with field engineers, network engineers, and vendors to resolve escalated network issues
- Prepare and present regular performance, capacity, and incident reports to management
- Maintain accurate logs of incidents, escalations, maintenance, and network changes
- Identify recurring network issues and implement process improvements to reduce future incidents
- Collaborate with engineering teams on network upgrades, expansions, and migrations
- Ensure all changes follow established change management and risk mitigation processes
- Participate in planning and execution of network optimization projects
- Ensure adherence to network security policies, industry standards, and regulatory requirements
- Conduct periodic audits to verify compliance with operational procedures and security standards
Skills