ZipRecruiter

Log In

1

Linux Site Reliability Engineer Jobs in Washington, NC

Domtar

Engineering Manager

Plymouth, NC · On-site

Responsible for mill reliability processes including alignment, balancing, lubrication, vibration ... Candidate must be an exceptional engineer with demonstrated leadership skills as well as experience ...

Domtar

Engineering Manager

Plymouth, NC · On-site

Responsible for mill reliability processes including alignment, balancing, lubrication, vibration ... Candidate must be an exceptional engineer with demonstrated leadership skills as well as experience ...

MrBeast

Studio Technology Engineer

Greenville, NC · On-site

Studio Technology Engineer MrBeast / Beast Industries Greenville, NC (on-site) Full-time IT Studio ... Certifications (CompTIA A+/Network+, Google IT, Apple, Microsoft, Linux) are a plus, not a ...

ALTEN Technology USA

IT/OT Engineer

New Bern, NC · On-site

Ensure high availability and reliability of plant systems. * Support manufacturing and automation ... Support site digitalization and modernization projects. * Develop technical requirements, test ...

ALTEN Technology USA

IT/OT Engineer

Greenville, NC · On-site

Ensure high availability and reliability of plant systems. * Support manufacturing and automation ... Support site digitalization and modernization projects. * Develop technical requirements, test ...

Domtar

Mechanical Engineer

Plymouth, NC · On-site

Recommend and implement upgrades or modifications to improve equipment performance and reliability ... To learn more about our company, consult the Domtar Company Web Site and follow us on LinkedIn ...

Domtar

Mechanical Engineer

Plymouth, NC · On-site

Recommend and implement upgrades or modifications to improve equipment performance and reliability ... To learn more about our company, consult the Domtar Company Web Site and follow us on LinkedIn ...

next page

Showing results 1-20

All JobsLinux Site Reliability Engineer JobsLinux Site Reliability Engineer Jobs in Washington, NC

Linux Site Reliability Engineer information

See Washington, NC salary details

$9

$55

$79

How much do linux site reliability engineer jobs pay per hour?

As of Sep 9, 2026, the average hourly pay for linux site reliability engineer in Washington, NC is $55.40, according to ZipRecruiter salary data. Most workers in this role earn between $47.64 and $63.32 per hour, depending on experience, location, and employer.

What is a Linux Site Reliability Engineer?

A Linux Site Reliability Engineer (SRE) is an IT professional responsible for ensuring the reliability, scalability, and performance of systems running on the Linux operating system. They bridge the gap between software development and operations by automating processes, monitoring infrastructure, and managing incidents. Linux SREs focus on system availability, building tools for deployment and monitoring, and improving system robustness through best practices and automation. Their work helps organizations deliver reliable online services and quickly recover from outages or system failures.

What are the key skills and qualifications needed to thrive as a Linux Site Reliability Engineer?

To thrive as a Linux Site Reliability Engineer, you need deep expertise in Linux system administration, scripting (such as Bash or Python), and a solid understanding of networking concepts, usually backed by a computer science degree or equivalent experience. Familiarity with configuration management tools (like Ansible, Puppet, or Chef), containerization (Docker, Kubernetes), and cloud platforms (AWS, GCP, or Azure) is typically required, along with relevant certifications like RHCE or AWS Certified SysOps Administrator. Strong problem-solving skills, effective communication, and the ability to work under pressure are crucial soft skills for this role. These competencies ensure the reliability, scalability, and security of complex infrastructure, minimizing downtime and supporting seamless operations.

What are some common challenges faced by Linux Site Reliability Engineers when scaling infrastructure, and how can they be addressed?

Linux Site Reliability Engineers often encounter challenges related to maintaining system stability and performance as infrastructure scales. Issues such as configuration drift, automation bottlenecks, and monitoring gaps can arise when managing numerous servers or services. Addressing these challenges typically involves implementing robust configuration management tools, investing in automated deployment pipelines, and enhancing observability through comprehensive monitoring and alerting solutions. Collaboration with development and operations teams is essential to ensure that scalability solutions align with business needs and technical requirements.

What is the difference between Linux Site Reliability Engineer vs Linux DevOps Engineer?

AspectLinux Site Reliability EngineerLinux DevOps Engineer
CredentialsLinux certifications, SRE-specific trainingLinux certifications, DevOps tools certifications
Work EnvironmentFocus on system reliability, monitoring, incident responseFocus on automation, CI/CD pipelines, deployment
Employer & IndustryTech companies, cloud providers, large enterprisesStartups, tech firms, software development teams
Search & Comparison IntentUnderstanding reliability roles, incident managementAutomation, deployment, continuous integration

While both roles involve Linux expertise, a Linux Site Reliability Engineer primarily focuses on maintaining system reliability, monitoring, and incident response. In contrast, a Linux DevOps Engineer emphasizes automation, continuous integration, and deployment processes. Both roles require Linux skills and often overlap, but their core responsibilities differ based on organizational needs.

What cities near Washington, NC are hiring for Linux Site Reliability Engineer jobs?

Cities near Washington, NC with the most Linux Site Reliability Engineer job openings:

Linux Site Reliability Engineer jobs near you

AI Agent Trajectory Annotator and Reviewer

Greenville, NC

Bespoke Labs
See more jobs at Bespoke Labsexternal

$20 - $30/hr

Full-time

Posted 9 days ago

Job description

Type: Contract, hourly

Location: Remote

Hours: 20–30 per week

Pay: $20–30/hour, based on experience and language coverage

Start: Immediate

ABOUT THE ROLE

We evaluate how well advanced AI coding agents solve real engineering problems. An agent is given a real open source codebase inside a container and a hard task, then works on its own for 80 to 250 steps. A trajectory is the full record of that run — every command, result, and decision.

You will do two jobs, and you should expect either on any given day.

•Annotate — Read a trajectory nobody has looked at yet and judge it step by step.

• Review — Take an existing annotation, written by our AI tooling or another person, and confirm, correct, or reject it.

TASKS YOU'LL SEE

• Feature build — Add a working feature to a live library without breaking anything that already worked.

• Rebuild — Work out what a compiled tool does by running it, then rebuild it to match its output, exit codes, and file effects.

• Bug hunt — Find and fix twenty undocumented bugs across a dozen files with no test suite, then record what caused them.

Mostly Python and Go, with some Rust, C, and Ct+. A trajectory runs about 100 steps.

WHAT YOU JUDGE IN A TRAJECTORY

• Was the command right for the state the environment was actually in?

• Did the agent read the previous output correctly?

• Was the step wrong, or only inefficient — these are scored differently.

• Where did the run first go off course — usually earlier than where it visibly broke.

• Did the agent notice its own mistake and recover, or keep building on a false assumption?

• Did it game the grader instead of solving the task (e.g., weakening a test or hardcoding an expected value)?

WHAT WE NEED FROM YOU

• Experience — 2+ years in software engineering, DevOps, or site reliability, with real debugging in real codebases.

• Languages — Strong in Python or Go, and able to read a language you've never used.

• Linux — Comfortable with logs, running processes, build failures, and containers.

• Workflow — Everyday Git, diffs, pull requests, and issue tracking.

• Debugging — Able to work with no test suite and no error message pointing at the cause.

• Focus — Able to hold context across a long run, because step 74 can depend on step 12.

• Writing — Clear English, since every judgement needs an explanation another engineer can check.

Apply