L3 Support Engineer (SOPs and Runbooks)

Nebius is leading a new era in cloud infrastructure for the global AI economy. We are building a full-stack AI cloud platform that supports developers and enterprises from data and model training through to production deployment, without the cost and complexity of building large in-house AI/ML infrastructure.

Built by engineers, for engineers. From large-scale GPU orchestration to inference optimization, we own the hard problems across compute, storage, networking and applied AI.

Listed on Nasdaq (NBIS) and headquartered in Amsterdam, we have a global footprint with R&D hubs across Europe, the UK, North America and Israel. Our team of 1,500+ includes hundreds of engineers with deep expertise across hardware, software and AI R&D.

Our L3 Support Line is the datacenter center of expertise for servers, GPU platforms, firmware (BIOS and BMC) and deep Linux diagnostics across Europe and the US, and it is growing.

This position owns the L3 knowledge system: the documentation standard, the SOP and runbook library, the error catalog and the review cycle that keeps them true. You are an engineer who writes, not a writer who has learned some engineering. You sit in on L3 investigations, capture what was found and turn it into procedures L1 and L2 technicians can follow safely. You do not carry the ticket queue; your week is documentation. Our principle: a problem is not solved until the runbook or SOP is updated.

Own the L3 knowledge system (Primary Focus)

* Own the documentation standard used by all L3 teams: templates, quality bar, ownership, approval workflow and review cycles.

* Build and maintain the SOP, runbook, troubleshooting guide and error-code library for GPU platforms, server hardware, firmware, out-of-band management and Linux diagnostics.

* Prioritize by incident frequency, impact, risk and recurring L1/L2 escalations, and keep the library findable and linked.

* Run reviews after platform changes, firmware releases and incidents; manage draft, approved, deprecated and archived states.

Turn investigations into procedures

* Join L3 and RnD investigations to capture symptoms, root causes, evidence, resolutions and preventive actions.

* Write repeatable procedures with prerequisites, warnings, decision points, expected output, rollback and escalation conditions.

* Resolve missing or conflicting information with the engineers involved before publishing.

Write and test for L1, L2 and L3

* Layer the content so L1 gets exact steps and safeguards while L3 can reach the deeper diagnostic detail.

* Validate procedures end to end, have L1 and L2 technicians run them without coaching, and fix what makes them hesitate.

* When escalations recur, check whether the documentation is wrong, hidden, unclear or incomplete.

Platform readiness and hands-on

* Produce the documentation package for each new hardware platform before it enters production support.

* Travel to datacenters to observe procedures as they are really run and capture knowledge after incidents.

* Strong hands-on experience with datacenter servers and Linux troubleshooting.

* Working knowledge of server hardware, BIOS/BMC firmware and out-of-band management (IPMI, Redfish or similar).

* A record of writing runbooks, SOPs or troubleshooting guides that operations teams