Infrastructure Tier 2 Engineer

⭐ - Featured Role | Apply direct with Data Freelance Hub
This role is for an Infrastructure Tier 2 Engineer on a contract basis, remote, for more than 6 months. Key skills include Azure monitoring, incident response, and proficiency in ServiceNow. Familiarity with Epic implementations and IaC documentation is required. Pay rate is "unknown."
🌎 - Country
United States
πŸ’± - Currency
$ USD
-
πŸ’° - Day rate
-
πŸ—“οΈ - Date discovered
August 21, 2025
πŸ•’ - Project duration
More than 6 months
-
🏝️ - Location type
Remote
-
πŸ“„ - Contract type
Unknown
-
πŸ”’ - Security clearance
Unknown
-
πŸ“ - Location detailed
United States
-
🧠 - Skills detailed
#Documentation #Azure #Splunk #Storage #Scala #Monitoring #GIT #Alation #Cloud #Infrastructure as Code (IaC) #Dynatrace
Role description
Role: Infrastructure Tier 2 Engineer Location: Remote Duration: Contract Job Description: Primary Monitoring & Incident Response β€’ Provide 24Γ—7 monitoring of Azure infrastructure (compute, network, storage) using tools such as Azure Monitor, Splunk, DynaTrace, and custom dashboards. β€’ Respond to alerts and triage P1/P2 escalations via ServiceNow war rooms, performing initial diagnosis and remediation where possible. β€’ Incident / Change / Exception process adherence. Capacity & Availability Management β€’ Identify scaling opportunities with virtual machines or service as required and identify zone redundancy patterns for performance. β€’ Keep track of capacity forecasts and proactively identify performance bottlenecks. SKILL SET & STAFFING CONSIDERATIONS β€’ Comfortable reading and troubleshooting logs/metrics (Splunk, DynaTrace, Azure Monitor). β€’ Familiar with Azure Backup services, basic restore procedures, and file share permissions. β€’ Proficiency in ticketing systems (ServiceNow), collaborating with other technical teams for escalations. β€’ Sufficient knowledge to follow runbooks and standard operating procedures (SOPs). β€’ Documentation of standard operating procedures and IaC changes should be continuously updated in a central repository (e.g., Git repos). β€’ Familiarity with Epic implementations (on-prem / cloud)