Job Summary

At AMD, our mission is to build great products that accelerate next-generation computing experiences, from AI and data centers to PCs, gaming, and embedded systems. Grounded in a culture of innovation and collaboration, we pursue execution excellence while being direct, humble, collaborative, and inclusive of diverse perspectives. Join us as we shape the future of AI and beyond. Together, we advance your career.

THE ROLE

We are seeking an SRE L1 Generalist to provide first-line monitoring, intake, triage, evidence collection, authorized remediation, escalation, and validation across the Fleet Services infrastructure stack. The role is part of IOQ’s operations and provides a consistent and efficient front door for compute, storage, networking, identity, cluster services, and supporting infrastructure.

The SRE L1 Generalist follows approved SOPs and runbooks, restores service for documented scenarios, and creates complete escalation packages when deeper expertise is required. Success in this role depends on disciplined execution, strong Linux fundamentals, high-quality ticket records, and reliable shift handoffs.

THE PERSON

You are curious, methodical, and calm under pressure. You do not guess when evidence is available. You follow procedures precisely, recognize stop conditions, communicate impact clearly, and escalate early when scope, risk, access, or technical complexity exceeds L1 authority.

Key Responsibilities

KEY RESPONSIBILITIES

• Monitor agreed dashboards, alerts, queues, and service-health signals across in-scope Fleet Services infrastructure.
• Acknowledge and classify incoming alerts and Jira tickets; confirm affected assets, symptoms, impact, priority, and ownership.
• Execute documented L1 checks for compute, storage, network, identity, authentication, virtualization, and cluster-service issues.
• Collect required logs, command output, timestamps, configuration state, topology or dependency details, and reproduction evidence.
• Perform only authorized low-risk remediation defined in approved runbooks, then validate recovery and document results.
• Escalate unresolved or high-risk cases to the correct L2/L3 owner with complete evidence, work performed, current state, and explicit assistance requested.
• Maintain accurate ticket status through review, in progress, on hold, validation, resolution, and closure; track delegated work until completion.
• Perform structured shift handoffs that identify active incidents, aging tickets, blocked work, risks, owners, and next steps.
• Support SOP and runbook validation through ticket playback, tabletop exercises, supervised execution, and feedback on missing or unclear steps.
• Identify repetitive work, alert noise, documentation gaps, and automation candidates for review by engineering and automation owners.

Skill Requirements

PREFERRED EXPERIENCE

• Experience in a NOC, service desk, infrastructure operations, junior SRE, systems administration, or technical support environment.
• Working knowledge of Linux command-line troubleshooting, processes, filesystems, services, networking, permissions, and logs.
• Foundational understanding of compute, virtualization, storage, TCP/IP networking, DNS, DHCP, identity, and authentication.
• Experience with Jira or comparable ticketing systems and with monitoring tools such as Prometheus, Grafana, SolarWinds, or PagerDuty.
• Ability to follow technical procedures, capture accurate evidence, recognize risk and stop conditions, and communicate concise handoffs.
• Basic scripting or automation experience with Python, shell, Ansible, or APIs is beneficial.
• Exposure to MAAS, Xen, VMware, Azure, NetApp, Pure, Weka, Arista, Cisco, or GPU/HPC infrastructure is beneficial.

ACADEMIC CREDENTIALS

Associate’s or Bachelor’s degree in Computer Science, Information Technology, Engineering, or a related field preferred; equivalent relevant experience considered.

Foundational Linux, cloud, networking, or IT service-management certification is beneficial.

Other Requirements

WORKING MODEL

Works within a follow-the-sun shift model and participates in weekend or after-hours coverage as assigned.

Requires disciplined real-time communication and complete handoff documentation.

ROLE BOUNDARIES AND ESCALATION

L1 resolves documented, authorized scenarios and does not make unapproved production changes or bypass change control.

L1 support tier is independent of incident priority; a high-priority event may require immediate parallel engagement of L2/L3 owners.