> Markdown version of [/jobs/ext/4727928-sre-l1-l2-support-cloud-platform-ops-engineer](https://www.wearedevelopers.com/jobs/ext/4727928-sre-l1-l2-support-cloud-platform-ops-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # SRE L1/L2 Support/Cloud Platform Ops Engineer - **Company:** Bitdeer Technologies Group - **Location:** San Jose, CA, United States - **Experience:** Experienced - **Salary:** $105,000 - $155,000 - **Contract:** Permanent contract - **Skills:** Artificial Intelligence, JIRA, Command-Line Interface, Cloud Computing, Data Centers, Network Interface Controllers, Firmware, Monitoring of Systems, Issue Tracking Systems, Linux System Administration, Log Analysis, Nagios, Network Diagnostics, Prometheus, Software Engineering, Diagnostic Tools, Graphics Processing Unit (GPU), Computer Network Operations, Cloud Platform System, Grafana, Bitcoin, AIOps, Servicenow - **Published:** November 15, 2026 - **Apply:** https://www.careerbuilder.com/job-details/sre-l1-l2-support-cloud-platform-ops-engineer-san-jose-ca--3136cefd-6d0c-43dc-8766-dec48786cac6 ## About the Role Cloud Computing, Software Engineering, Bitcoin, Artificial Intelligence (AI), Technical Leadership, Operations, Cloud Computing, Network Operations Center, Logistics, Construction Management, * 2+ years in NOC, data center operations, or IT support role * Basic Linux system administration (command line, log analysis, service management) * Familiarity with monitoring tools (Prometheus, Grafana, Nagios, or equivalent) * Experience with ticketing systems (ServiceNow, Jira Service Management) * Ability to perform physical data center tasks: rack and stack, cabling, hardware replacement * Strong communication skills for shift handoffs, incident documentation, and escalation * Ability to work 8AM-8PM PST shift schedule (12-hour shifts with rotation) * Curiosity about automation - you don't just execute the runbook, you notice when it's the third time this month and ask what should change. * Comfort with structured data - you understand that how you file a ticket matters, because it may train a model that decides how the next one is filed. ## Description You are the first human in the loop - the escalation target when the AIOps system needs a decision, and the source of ground truth that turns novel incidents into new automations. NeoCloud is building an AI-operated GPU cloud. That doesn't mean fewer humans - it means humans focus on judgment calls the platform can't yet make, and every judgment call trains the platform to do it next time. In this L1 role you cover front-line monitoring and incident response for NeoCloud's US GPU DCs during the 8AM-8PM PST shift. You execute SOPs, escalate the hard cases, and feed the AIOps substrate the ground truth it needs to learn from novel incidents. What you'll own * Monitor GPU cluster health, network status, storage systems, and environmental sensors via centralized dashboards. * Respond to alerts and execute runbooks for common incidents: GPU errors, link flaps, node failures, storage alerts. * Perform hardware triage: identify failed GPUs, NICs, PSUs, disks, and cables from monitoring data and physical inspection. * Execute standard remediation: GPU reset, node drain/reboot, link re-seat, BMC recovery. * Collect diagnostic data for L2/SME escalation: logs, DCGM output, network diagnostics, hardware health reports. * Manage incident tickets from creation through resolution or escalation (ServiceNow/Jira). * Perform physical DC tasks: cable installation, hardware swap-outs, rack and stack, labeling (on-site roles). * Execute structured shift handoffs at 8AM and 8PM PST with the APAC operations team. * Maintain and update operational runbooks based on recurring issues. * Assist with hardware deployment, firmware updates, and inventory management under SME guidance. Feed the AIOps substrate * Every novel incident you resolve is data the platform team needs - you tag it, describe it, and hand it back so it becomes an automation. * Every runbook you touch should get closer to being executable by the platform, not by you. * Your handoff notes are structured signal, not free-form email. Why this role is different from a NOC job * You are not the last line of defense - the platform is. You are the training signal. * Growth path is real: strong L1s here move into SME roles, or into the platform team as automation authors.