Suggested rewrite: Led a cross-functional initiative that improved [business outcome] by [measurable result], demonstrating experience relevant to this role...
Senior Site Reliability Engineer (DevTools)
Review the role, location requirements, compensation details, and application process before deciding whether this opportunity fits your next career move.
- Salary
- Undisclosed
- Department
- DevOps & Infrastructure
- Employment
- Full Time
- Experience
- Senior
- Published
- Apply before
- 27 Nov 2026
- Listing views
- 40
- Application actions
- 4
Make your next move.
Prepare your resume, explore your fit, and draft a cover letter for this opportunity.
The role, at a glance.
Nebius is hiring a Senior Site Reliability Engineer for its DevTools team to operate and improve developer infrastructure at substantial scale. The role combines SRE and software engineering work equally, supporting GitLab, TeamCity, Artifactory, CI pipelines, and a large monorepo. Key work includes building self-healing systems, improving performance, reducing developer friction, and translating user feedback into measurable service improvements. Candidates need strong Unix/Linux and JVM knowledge plus practical coding ability in Java, Kotlin, Go, Python, or Ruby. The team works in a fast-changing AI-cloud environment and includes coding interviews in its selection process.
Role DNA
A quick view of the complexity, pace, ownership and collaboration implied by the job description.
Pace & Pressure
5/5Autonomy Level
4/5Communication Load
4/5Salary analysis
Estimated compensation compared with the broader US market for similar roles.
Core skills
Skills and capabilities most closely associated with this opportunity.
Sample interview questions
I would first segment failures by agent pool, build configuration, error class, repository, and time window to distinguish infrastructure faults from code-related failures. I would review agent capacity, logs, dependency availability, network and artifact-service latency, then prioritize mitigations such as isolating unhealthy agents, increasing constrained capacity, or rolling back a recent platform change. Finally, I would add alerts and service-level metrics that detect the leading indicators earlier.
I would define the component's health signals, dependencies, failure modes, and recovery objectives before choosing automation. The design would use redundant instances, readiness and liveness checks, safe automated restarts or failover, idempotent recovery actions, and circuit breakers to prevent cascading failures. I would also ensure that automated remediation is observable, rate-limited, and paired with escalation when recovery attempts fail.
I would examine CPU saturation, heap usage, garbage-collection frequency and pause times, thread states, blocked threads, file descriptors, connection pools, and request latency. Thread dumps and Java Flight Recorder can reveal lock contention, inefficient I/O, excessive allocation, or exhausted pools. I would correlate JVM findings with host, database, network, and downstream-service metrics before making a targeted change.
I would translate the reported friction into a specific user journey and measurable outcome, such as build-start latency, artifact-download success rate, or time to recover from a failed pipeline. I would establish a baseline, identify contributing system metrics, implement and test an improvement, and compare results after release. I would close the loop with affected users to verify that the metric improvement resolved the original problem.
I would first determine whether configuration, an extension point, or an upstream contribution can meet the need before maintaining a fork. If a patch is necessary, I would keep it small, well-tested, documented, and isolated from unrelated changes, while tracking the upstream version and compatibility risks. I would automate regression testing and maintain a clear upgrade process so the customization does not become unmanageable technical debt.
About this role.
About Nebius:
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.
The Role
We’re an SRE team within DevTools, looking for someone ready to help maintain and grow our systems. We run 25k builds a day in TeamCity, store 100 TB of artifacts in Artifactory, and work with a massive monorepo in GitLab — comparable in scale to what you’d find at FAANG companies. We modify GitLab and build our own TeamCity plugins to give users a product that meets their needs. We’re also experimenting with AI — we have our own RAG setup and are figuring out how to operate in the age of agents. Our goal: understand users’ problems and requests, define metrics that capture the problem, improve those metrics, and verify that the user’s problem is actually gone.
Your responsibilities will include:
Improving services based on user feedback
Building fault-tolerant, self-healing architecture
Finding ways to speed up our systems and reduce user friction
Modifying well-known closed- and open-source solutions Supporting our users
We expect you to have:
A combination of SRE and SWE experience (for us that’s a 50/50 split). Our code is in Java/Kotlin, Go, Python, and Ruby
An understanding of what’s happening under the hood in Unix-like systems and the JVM
A passion for improving the user experience
The ability to adapt quickly on the fly in a fast-changing environment
It will be an added bonus if you have:
Experience in Platform Engineering
Experience operating GitLab (or another VCS) and TeamCity (or another CI system)
Experience with Spring and operating Java monoliths
We conduct coding interviews as part of the process.
Benefits & Perks:
- Competitive compensation
- Career growth and learning opportunities
- Flexibility and ownership
- Collaborative and innovative culture
- Opportunity to work on impactful AI projects
- International environment and talented teams
What’s it like to work at Nebius:
Fast moving – Bold thinking – Constant growth – Meaningful impact – Trust and real ownership – Opportunity to shape the future of AI
Equal Opportunity Statement:
Nebius is an equal opportunity employer. We are committed to fostering an inclusive and diverse workplace and to providing equal employment opportunities in all aspects of employment. We do not discriminate on the basis of race, color, religion, sex (including pregnancy), national origin, ancestry, age, disability, genetic information, marital status, veteran status, sexual orientation, gender identity or expression, or any other characteristic protected by applicable law.
Applicants must be authorized to work in the country in which they apply and will be required to provide proof of employment eligibility as a condition of hire.
If you need accommodations during the application process, please let us know.
Annual salary information is not provided for this position. Explore salary ranges for similar roles in our Salary Directory ›
This job listing has been manually reviewed by the Jobicy Trust & Safety Team for compliance with our posting guidelines, including verification of the company's legitimacy, accuracy of job details, clarity of remote work policy, and absence of misleading or fraudulent content.
Apply now.
Follow the employer’s application method and review Jobicy’s safety guidance before sharing personal information.
Continue on the employer website
Protect your personal information and never pay to secure an interview or job offer. .
