NOC Engineer / SRE

NICE
United Kingdom
Remote

Who this role is best for

Candidates with strong Linux systems administration and incident management experience will find this hybrid NOC/SRE role challenging, especially in a remote setup with 24x7 on-call responsibilities.

Best fit for

  • Candidates with a background in traditional NOC roles transitioning to SRE practices
    — “Prior migration from traditional NOC → SRE model”
  • Individuals who can engineer solutions to reduce operational toil and automate workflows
    — “engineer problems away, not just respond to alerts”
  • Professionals skilled in monitoring, alerting, and observability tools with a focus on SLIs/SLOs
    — “Design and maintain alerting strategies that align with SLIs/SLOs”

Things to consider

  • This role demands a high level of availability due to 24x7 on-call responsibilities
    — “Act as a primary or escalation responder in a 24x7 on‑call rotation”
  • Remote work is expected, but the candidate must be available for coordination across global teams
    — “Coordinate across Engineering, Infrastructure, Security, and Product teams”

How to stand out

  • Highlight experience in reducing alert fatigue and improving signal-to-noise ratios in monitoring systems
    — “Reduce alert fatigue through signal‑to‑noise improvements”
  • Emphasize contributions to self-healing systems and automation of operational tasks
    — “Implement self‑healing and auto‑remediation where possible”
  • Showcase your ability to lead or support major incident responses with clear examples
    — “Lead or support Major Incident (MI) response, including triage, mitigation, and resolution”
  • Demonstrate experience with infrastructure and cloud platforms, especially AWS
    — “Experience with Cloud infrastructure (AWS preferred)”
  • Include examples of improving runbooks and operational processes
    — “Comfort working from runbooks—but improving them when they fall short”
Pace · Fast PacedCollaboration · HighAutonomy · MediumDecision Impact · Team

Derived from job-description analysis by Serendipath's career intelligence engine.

What success looks like

  • Reduced mean time to detect (MTTD) and mean time to resolve (MTTR)
  • Improved service reliability through automation
Typical background
Experience in NOC or SRE rolesStrong Linux systems administration background

Skills & requirements

Required

Linux Systems AdministrationIncident ManagementProduction SupportCloud InfrastructureContainers & OrchestrationMonitoring & AlertingScripting Or Programming

Preferred

Slos / SlisSecurityCompliance

Stack & domain

Linux Systems AdministrationIncident ManagementProduction SupportCloud Infrastructure (AWS Preferred)Containers & Orchestration (docker, Kubernetes)Monitoring/alerting PlatformsScripting Or Programming Experience In Python, Bash, GoNetworking Fundamentals (dns, Tcp/ip, Load Balancing)Ability To Handle High-pressure Incidents Calmly And EffectivelyStrong Written And Verbal Communication For Incident CoordinationNetwork Operations Center (noc)Engineering-driven Reliability PracticesService ReliabilityIncident ResponseOperational AutomationObservabilityReliability EngineeringAutomationPlatform & Infrastructure Support

About the role

Original posting from NICE via Greenhouse

At NiCE, we don’t limit our challenges. We challenge our limits. Always. We’re ambitious. We’re game changers. And we play to win. We set the highest standards and execute beyond them. And if you’re like us, we can offer you the ultimate career opportunity that will light a fire within you.

So, what’s the role all about?

The SRE – NOC role sits at the intersection of traditional Network Operations Center (NOC) responsibilities and engineering‑driven reliability practices. This role focuses on 24/7 service reliability, incident response, operational automation, and observability, while actively reducing operational toil through software and automation.

Unlike a traditional NOC analyst, an SRE‑NOC is expected to engineer problems away, not just respond to alerts.

How will you make an impact?

Incident Response & Operations

Act as a primary or escalation responder in a 24x7 on‑call rotation

Lead or support Major Incident (MI) response, including triage, mitigation, and resolution

Coordinate across Engineering, Infrastructure, Security, and Product teams

Execute and improve runbooks, playbooks, and escalation paths

Drive blameless post‑incident reviews (PIRs) and track corrective actions

Monitoring, Alerting & Observability

Own service health monitoring across infrastructure, applications, and dependencies

Design and maintain alerting strategies that align with SLIs/SLOs

Reduce alert fatigue through signal‑to‑noise improvements

Build dashboards using tools such as:

Grafana

Prometheus

Datadog / Splunk / CloudWatch

Reliability Engineering & Automation

Automate repetitive operational tasks to reduce manual toil

Improve mean time to detect (MTTD) and mean time to resolve (MTTR)

Develop scripts and tools (Python, Bash, Go, etc.) to support NOC/SRE workflows

Implement self‑healing and auto‑remediation where possible

Partner with engineering teams to improve system design for reliability

Platform & Infrastructure Support

Support and troubleshoot:

Linux‑based systems

Cloud platforms (AWS, Azure, GCP)

Kubernetes / containerized environments

Assist with capacity planning and availability reviews

Ensure operational readiness for production releases

Have you got what it takes?

Technical

Strong Linux systems administration

Experience with incident management and production support

Familiarity with:

Cloud infrastructure (AWS preferred)

Containers & orchestration (Docker, Kubernetes)

Monitoring/alerting platforms

Scripting or programming experience in Python, Bash, Go, or similar

Understanding of networking fundamentals (DNS, TCP/IP, load balancing)

Operational

Experience working in 24x7 NOC or production operations environments

Ability to handle high‑pressure incidents calmly and effectively

Strong written and verbal communication for incident coordination

Comfort working from runbooks—but improving them when they fall short

Preferred / Differentiators

Experience defining or operating to SLOs / SLIs

Prior migration from traditional NOC → SRE model

Infrastructure as Code experience (Terraform, Ansible, etc.)

Exposure to security, compliance, or regulated environments

Requisition ID: 11770.

Reporting into: Manager, Network Operations.

Role Type: Individual Contributor.

#LI-Remote

About NiCE

NICE Ltd. (NASDAQ: NICE) software products are used by 25,000+ global businesses, including 85 of the Fortune 100 corporations, to deliver extraordinary customer experiences, fight financial crime and ensure public safety. Every day, NiCE software manages more than 120 million customer interactions and monitors 3+ billion financial transactions.

Known as an innovation powerhouse that excels in AI, cloud and digital, NiCE is consistently recognized as the market leader in its domains, with over 8,500 employees across 30+ countries.

NiCE is proud to be an equal opportunity employer. All qualified applicants will receive consideration for employment without regard to race, color, religion, national origin, age, sex, marital status, ancestry, neurotype, physical or mental disability, veteran status, gender identity, sexual orientation or any other category protected by law.

Source: NICE careers (Greenhouse)

Similar roles

More roles at NICE