Government Careers
  • Tier 1 NOC Engineer with Security Clearance

  • Gray Wolf Solutions
  • Mc Lean, Virginia 22107 United States View Map
Tier 1 NOC Engineer McLean, VA (LX2) Required Clearance: FS poly preferred but a CI poly is acceptable A Tier 1 NOC Engineer in an Azure environment is responsible for providing initial monitoring,
troubleshooting, and support for cloud infrastructure and services. They play a critical role in ensuring
that Azure-based systems remain operational and that incidents are detected early and escalated as
needed. Below are the typical responsibilities for a Tier 1 NOC Engineer in an Azure environment. Skills Required: • Basic knowledge of Azure cloud services (e.g., Azure VMs, Storage, Networking, Azure Active Directory). • Familiarity with monitoring tools such as Azure Monitor, Application Insights, Log Analytics. • Basic troubleshooting and problem-solving skills, especially in cloud-based environments. • Understanding of networking fundamentals (e.g., DNS, VPN, IP addressing). • Strong communication skills for reporting and escalating incidents. • Basic security principles (e.g., user access, RBAC). Tools and Platforms Utilized: • Azure Monitor: For monitoring performance, resource health, and logs. • Azure Security Center: For managing and reviewing security alerts and policies. • Azure Portal: For accessing and managing resources, configurations, and monitoring. • Azure Active Directory (AAD): For managing user access and identity-related issues. • Azure Log Analytics: For querying and analyzing log data to troubleshoot issues. • ServiceNow or Jira: For managing and tracking incidents and service requests. Typical responsibilities: 1. Monitoring and Alerts • Monitor Azure Resources: Continuously monitor the health and status of Azure cloud resources (e.g., Virtual Machines, Storage Accounts, Azure Networking, etc.) using tools like Azure Monitor, Azure Application Insights, and third-party monitoring platforms. • Alert Management: Respond to and acknowledge alerts from monitoring tools, ensuring any issues are identified and recorded in the incident management system. • Review Dashboards: Regularly review Azure dashboards to identify any anomalies in resource usage, availability, or performance. 2. Incident Detection and Initial Troubleshooting • Identify Issues: Detect issues such as service outages, resource failures, performance degradation, or unusual spikes in traffic or resource usage. • Initial Troubleshooting: Perform basic troubleshooting to determine whether issues are related to Azure services, network issues, or user configurations. Use Azure tools (e.g., Azure Resource Health, Network Watcher) to diagnose the problem. • Log Review: Review system logs and diagnostic information to understand issues, such as checking logs from Azure Monitor, Application Insights, or Azure Security Center. ,3. Incident Escalation • Escalate Critical Issues: If the problem cannot be resolved at Tier 1, escalate the incident to Tier 2 or relevant engineering teams for further investigation. • Provide Detailed Information: Document all troubleshooting steps, error messages, and any relevant information to aid in escalation. 4. Service Requests and User Support • Support User Requests: Respond to user requests regarding Azure resources, such as provisioning new resources, accessing data, or configuring virtual machines. • Provide Basic Cloud Assistance: Assist users with basic configuration or access-related issues within the Azure environment (e.g., managing access control through Azure Active Directory). • Document and Track Requests: Create tickets for service requests and ensure they are resolved in a timely manner. 5. Perform Routine Maintenance and Tasks • Perform Routine Checks: Run daily checks on the health of virtual machines, databases, and other critical Azure resources. • Backup Verification: Ensure that backup operations (e.g., Azure Backup) are functioning correctly and confirm that data is backed up on a regular schedule. • Patch Management: Check if any updates or patches need to be applied to Azure virtual machines and infrastructure. 6. Documentation and Reporting • Incident Documentation: Document every incident and the steps taken to resolve or escalate it. Ensure tickets are kept up to date with accurate and comprehensive information. • Generate Reports: Provide reports on recurring issues, outages, or system performance for review by management or senior engineers. 7. Security Awareness • Monitor Security Alerts: Respond to security alerts related to Azure services, such as unauthorized access attempts or suspicious activities, using tools like Azure Security Center. • Basic Security Checks: Ensure basic security configurations, such as proper Azure role-based access control (RBAC), are in place. • Compliance Monitoring: Ensure that the environment remains compliant with security policies, standards, and regulations by monitoring configurations and incidents. 8. Communication and Collaboration • Collaborate with Other Teams: Work closely with Tier 2/3 engineers, DevOps, and system administrators to ensure issues are resolved and root causes are identified. • Update Stakeholders: Communicate effectively with internal teams or customers regarding the status of incidents, requests, or performance issues.
Tier 1 NOC Engineer McLean, VA (LX2) Required Clearance: FS poly preferred but a CI poly is acceptable A Tier 1 NOC Engineer in an Azure environment is responsible for providing initial monitoring,
troubleshooting, and support for cloud infrastructure and services. They play a critical role in ensuring
that Azure-based systems remain operational and that incidents are detected early and escalated as
needed. Below are the typical responsibilities for a Tier 1 NOC Engineer in an Azure environment. Skills Required: • Basic knowledge of Azure cloud services (e.g., Azure VMs, Storage, Networking, Azure Active Directory). • Familiarity with monitoring tools such as Azure Monitor, Application Insights, Log Analytics. • Basic troubleshooting and problem-solving skills, especially in cloud-based environments. • Understanding of networking fundamentals (e.g., DNS, VPN, IP addressing). • Strong communication skills for reporting and escalating incidents. • Basic security principles (e.g., user access, RBAC). Tools and Platforms Utilized: • Azure Monitor: For monitoring performance, resource health, and logs. • Azure Security Center: For managing and reviewing security alerts and policies. • Azure Portal: For accessing and managing resources, configurations, and monitoring. • Azure Active Directory (AAD): For managing user access and identity-related issues. • Azure Log Analytics: For querying and analyzing log data to troubleshoot issues. • ServiceNow or Jira: For managing and tracking incidents and service requests. Typical responsibilities: 1. Monitoring and Alerts • Monitor Azure Resources: Continuously monitor the health and status of Azure cloud resources (e.g., Virtual Machines, Storage Accounts, Azure Networking, etc.) using tools like Azure Monitor, Azure Application Insights, and third-party monitoring platforms. • Alert Management: Respond to and acknowledge alerts from monitoring tools, ensuring any issues are identified and recorded in the incident management system. • Review Dashboards: Regularly review Azure dashboards to identify any anomalies in resource usage, availability, or performance. 2. Incident Detection and Initial Troubleshooting • Identify Issues: Detect issues such as service outages, resource failures, performance degradation, or unusual spikes in traffic or resource usage. • Initial Troubleshooting: Perform basic troubleshooting to determine whether issues are related to Azure services, network issues, or user configurations. Use Azure tools (e.g., Azure Resource Health, Network Watcher) to diagnose the problem. • Log Review: Review system logs and diagnostic information to understand issues, such as checking logs from Azure Monitor, Application Insights, or Azure Security Center. ,3. Incident Escalation • Escalate Critical Issues: If the problem cannot be resolved at Tier 1, escalate the incident to Tier 2 or relevant engineering teams for further investigation. • Provide Detailed Information: Document all troubleshooting steps, error messages, and any relevant information to aid in escalation. 4. Service Requests and User Support • Support User Requests: Respond to user requests regarding Azure resources, such as provisioning new resources, accessing data, or configuring virtual machines. • Provide Basic Cloud Assistance: Assist users with basic configuration or access-related issues within the Azure environment (e.g., managing access control through Azure Active Directory). • Document and Track Requests: Create tickets for service requests and ensure they are resolved in a timely manner. 5. Perform Routine Maintenance and Tasks • Perform Routine Checks: Run daily checks on the health of virtual machines, databases, and other critical Azure resources. • Backup Verification: Ensure that backup operations (e.g., Azure Backup) are functioning correctly and confirm that data is backed up on a regular schedule. • Patch Management: Check if any updates or patches need to be applied to Azure virtual machines and infrastructure. 6. Documentation and Reporting • Incident Documentation: Document every incident and the steps taken to resolve or escalate it. Ensure tickets are kept up to date with accurate and comprehensive information. • Generate Reports: Provide reports on recurring issues, outages, or system performance for review by management or senior engineers. 7. Security Awareness • Monitor Security Alerts: Respond to security alerts related to Azure services, such as unauthorized access attempts or suspicious activities, using tools like Azure Security Center. • Basic Security Checks: Ensure basic security configurations, such as proper Azure role-based access control (RBAC), are in place. • Compliance Monitoring: Ensure that the environment remains compliant with security policies, standards, and regulations by monitoring configurations and incidents. 8. Communication and Collaboration • Collaborate with Other Teams: Work closely with Tier 2/3 engineers, DevOps, and system administrators to ensure issues are resolved and root causes are identified. • Update Stakeholders: Communicate effectively with internal teams or customers regarding the status of incidents, requests, or performance issues.
Government Careers

Government Careers

Government jobs offer stability, competitive benefits, and the chance to make a meaningful impact on your community and country.

Whether you’re starting your career or seeking new opportunities, these roles provide pathways for growth, security, and service.

Explore positions across a wide range of fields and take the first step toward a rewarding future in public service.

Show more

MORE JOBS