NextGenPros Inc

Digital Support Analyst

⭐ - Featured Role | Apply direct with Data Freelance Hub
This role is for a Digital Support Analyst (Level 1.5/Level 2) with a contract length of "unknown" and a pay rate of "unknown," located in "unknown." Key skills include incident triage, monitoring tools (e.g., Datadog), and cloud experience (GCP/Azure/AWS).
🌎 - Country
United States
πŸ’± - Currency
$ USD
-
πŸ’° - Day rate
Unknown
-
πŸ—“οΈ - Date
July 30, 2026
πŸ•’ - Duration
Unknown
-
🏝️ - Location
Unknown
-
πŸ“„ - Contract
Unknown
-
πŸ”’ - Security
Unknown
-
πŸ“ - Location detailed
Dallas, TX
-
🧠 - Skills detailed
#"ETL (Extract #Transform #Load)" #Dynatrace #AI (Artificial Intelligence) #Alation #Batch #Datadog #Automation #Jira #Deployment #Monitoring #Splunk #API (Application Programming Interface) #GCP (Google Cloud Platform) #Azure #Cloud #BitBucket #CRM (Customer Relationship Management) #AWS (Amazon Web Services) #Scala #React #DevOps #Observability
Role description
Job Description: Digital Support Analyst (Level 1.5/Level 2) Digital Service Management & Operations Position Overview We are seeking a highly motivated Digital Support Analyst (Level 1.5/Level 2) to help establish a modern, structured digital support and services model. This role will serve as a critical triage and diagnostic layer between the service desk (L1) and engineering teams (L3), transforming support from a reactive intake function into a proactive, insight-driven operations capability. Reporting to the Director, Digital Service Management & Operations, this role will focus on incident triage, monitoring, troubleshooting, and release-aware diagnostics across a complex, integrated application and cloud environment. Context & Mission The current support model operates as a broad, centralized intake layer covering end-user support, applications, and cloud infrastructure, but lacks: β€’ Dedicated monitoring (β€œeyes-on-glass”) β€’ Structured triage and diagnostic capability β€’ Deep technical ownership at the L1/L2 layers This role is designed to: β€’ Introduce structured L1.5/L2 triage and investigation β€’ Improve incident quality and escalation effectiveness β€’ Enable proactive monitoring and operational stability β€’ Support a high-frequency release environment Key Responsibilities 1. Incident Triage & Technical Investigation (Core Focus) β€’ Act as the primary L1.5/L2 triage layer, analyzing alerts, incidents, and system anomalies. β€’ Perform initial troubleshooting and diagnostics before escalation to L3 teams. β€’ Develop structured problem statements with actionable insights for engineering teams. β€’ Interpret and analyze: β€’ API responses and endpoint behavior β€’ Application errors (e.g., HTTP 500s) β€’ Latency and performance degradation β€’ Infrastructure and database indicators (CPU, memory, query performance) β€’ Participate in incident bridge calls, providing real-time technical insights. 1. Monitoring & β€œEyes-on-Glass” Operations β€’ Support the development of a dedicated monitoring capability. β€’ Continuously monitor systems using observability/APM tools (e.g., Datadog, GCP, Idera). β€’ Correlate alerts and identify patterns, anomalies, and early warning signals. β€’ Shift operations from reactive escalation β†’ proactive issue detection and prevention. 1. Cross-Functional Troubleshooting β€’ Investigate issues across integrated front-end, back-end, and cloud platforms (e.g., GCP environments). β€’ Perform cross-stack analysis, recognizing that issues may span multiple systems. β€’ Provide context-aware insights (e.g., dependency-related failures like external platform issues). 1. Release-Aware Support & QA Mindset β€’ Collaborate with the Release Manager and DevOps teams on frequent (multi-weekly) releases. β€’ Correlate incidents with: β€’ Recent deployments β€’ Configuration changes β€’ Feature rollouts β€’ Apply a QA-oriented mindset to validate system behavior post-release. β€’ Support hypercare and post-release monitoring activities. 1. Runbooks, Knowledge & Process Maturity β€’ Execute and continuously improve runbooks and standard operating procedures (SOPs). β€’ Document: β€’ Troubleshooting steps β€’ Known issues β€’ Root cause indicators β€’ Drive standardization of triage and escalation processes. β€’ Contribute to problem management lifecycle and post-incident reviews (PIRs). 1. Service Management & ITIL Alignment β€’ Operate within ServiceNow (incident, change, and problem management) and Atlassian (JIRA, Confluence, Bitbucket). β€’ Improve: β€’ Ticket quality β€’ Categorization and prioritization β€’ Escalation readiness β€’ Support CAB readiness activities by providing operational insights. β€’ Contribute to defining an L1–L2–L3 escalation framework. 1. Automation, AI & Continuous Improvement β€’ Leverage emerging AIOps and automation capabilities for: β€’ Alert correlation β€’ Root cause identification β€’ Identify opportunities to reduce manual triage effort. β€’ Collaborate on improving integration between: β€’ ITSM (ServiceNow) β€’ Monitoring/observability tools Required Qualifications β€’ 3–6 years of experience in application support, production support, or digital operations. β€’ Strong troubleshooting experience in complex, integrated environments. β€’ Hands-on experience with: β€’ Monitoring/APM tools (Datadog, Dynatrace, Splunk, etc.) β€’ Incident management platforms (ServiceNow preferred) β€’ Ability to interpret: β€’ Logs, APIs, and system metrics β€’ Performance and error patterns β€’ Solid understanding of ITIL processes (Incident, Problem, Change). Preferred Qualifications β€’ Experience in cloud environments (GCP, Azure, or AWS). β€’ Exposure to CI/CD pipelines and DevOps practices. β€’ Familiarity with: β€’ CRM platforms (e.g., Salesforce, Dynamics) β€’ Job orchestration/batch processing tools β€’ Experience in high-availability, customer-facing digital systems. Key Competencies β€’ Strong analytical and diagnostic mindset β€’ Ability to move beyond escalation to true problem investigation β€’ Curiosity and ownership in understanding root causes β€’ Effective communication in high-pressure incident scenarios β€’ Ability to work across applications, infrastructure, and QA domains Team Structure & Operating Model β€’ Reports to: Director, Digital Service Management & Operations (Javier Mercado) β€’ Works alongside: β€’ DevOps & Engineering teams (CI/CD, releases, platform ownership) β€’ Release Manager (new role) β€’ Service Desk (L1) and Engineering (L3) β€’ Part of building a dedicated L1–L2–L3 support model