1

Reliability Engineer Jobs in Lenexa, KS (NOW HIRING)

SRE DevOps Engineer

Overland Park, KS · On-site

$110 - $130/hr

SRE DevOps Engineer Location: Overland Park, KS / Atlanta, GA / Frisco, TX (Onsite) Requirements * 4-9 years in SRE/DevOps/Systems Engineering as Senior or Principal Engineer * Strong hands‑on ...

New

Overview Garmin International seeks Senior Site Reliability Engineer (Olathe, KS; Multiple positions): Essential Functions * Establish and provide training to development teams on operational process ...

New

Overview We are seeking a full-time Senior Site Reliability Engineer at Garmin's U.S. headquarters in the Greater Kansas City area. In this role, you will be responsible for ensuring the integrity of ...

Sr. Systems Engineer - AI

Kansas City, KS · On-site

$100K - $137K/yr

Establish and enforce site reliability engineering (SRE) practices, including high availability and fault tolerance, capacity planning and auto-scaling, and redundancy and failover strategies

Senior Infrastructure Engineer

Overland Park, KS · On-site

$131.75 - $170.50/hr

  • Medical

  • Dental

  • Vision

  • Retirement

  • PTO

Senior Linux Platform Engineer - Join our Systems Platform Engineering team at Cboe Global Markets ... Manage and improve Linux‑based infrastructure emphasizing performance, reliability, and ...

New

Showing results 21-40

Reliability Engineer information

See Lenexa, KS salary details

$57.3K

$110.7K

$132.4K

How much do reliability engineer jobs pay per year?

As of Aug 20, 2026, the average yearly pay for reliability engineer in Lenexa, KS is $110,743.00, according to ZipRecruiter salary data. Most workers in this role earn between $96,200.00 and $121,100.00 per year, depending on experience, location, and employer.

What is a reliability engineer?

Reliability Engineers are professionals responsible for ensuring that systems, equipment, or processes function consistently and efficiently over time. They analyze data, identify potential points of failure, and develop maintenance strategies to improve system reliability and minimize downtime. Their work spans various industries, including manufacturing, energy, and technology, and often involves collaborating with design, operations, and maintenance teams. By implementing reliability-centered maintenance and predictive analysis, they help organizations save costs and increase safety.

What does a reliability engineer do?

As a reliability engineer, your duties are to test and evaluate the manufacturing of products and components and ensure that the procedures are efficient and do not lead to abnormally high maintenance or operational costs. Your other responsibilities are to find solutions to product reliability risks. You may manage risk in a supply chain, develop loss prevention strategies, and track the entire lifecycle of product development, from building prototypes to moving a product into full-scale production. You analyze information from department heads and recommend strategies to reduce risk and ensure that the product works reliably.

What are the key skills and qualifications needed to thrive as a reliability engineer, and why are they important?

To thrive as a Reliability Engineer, you need a solid background in engineering principles, failure analysis, and reliability modeling, typically with a degree in engineering or a related field. Familiarity with tools such as FMEA, Root Cause Analysis (RCA), reliability-centered maintenance (RCM) software, and certifications like Certified Reliability Engineer (CRE) are highly valued. Strong problem-solving abilities, attention to detail, and effective communication are crucial soft skills in this role. These skills ensure systems are dependable, downtime is minimized, and organizational performance and safety are optimized.

What are some typical challenges reliability engineers face when implementing preventive maintenance strategies?

Reliability Engineers often encounter challenges such as balancing preventive maintenance schedules with production demands, ensuring buy-in from operations teams, and accurately predicting equipment failures. They must analyze large sets of historical data to identify trends and root causes, which can be complex in facilities with diverse machinery. Collaboration with maintenance, operations, and engineering teams is essential to develop effective strategies that minimize downtime while optimizing resources.

What is the difference between Reliability Engineer vs Maintenance Engineer?

AspectReliability EngineerMaintenance Engineer
CredentialsTypically requires engineering degree, certifications in reliability or asset managementOften requires engineering or technical diploma, certifications in maintenance or equipment repair
Work EnvironmentFocuses on analysis, design, and improvement of systems for reliabilityHands-on maintenance, repair, and troubleshooting of equipment
Industry UsageCommon in manufacturing, energy, aerospace, and industrial sectorsPrevalent in manufacturing, facilities, and industrial plants

Reliability Engineers focus on designing and improving systems to prevent failures, using data analysis and modeling. Maintenance Engineers perform hands-on repairs and upkeep of equipment to ensure operational continuity. While both roles aim to optimize equipment performance, Reliability Engineers work proactively on system reliability, whereas Maintenance Engineers handle reactive and scheduled maintenance tasks.

Are reliability engineers in demand?

Reliability engineers are in high demand across industries such as manufacturing, energy, and aerospace due to their role in improving system performance and reducing downtime. Employers seek professionals with skills in data analysis, failure modes, and maintenance strategies, often requiring certifications like Certified Reliability Engineer (CRE). The job outlook is positive, with steady growth expected as companies prioritize operational efficiency and risk management.

How much do reliability engineers get paid?

Reliability engineers typically earn a median annual salary ranging from $70,000 to $110,000, depending on experience, location, and industry. Senior or specialized reliability engineers with certifications and advanced skills can earn higher salaries, often exceeding $120,000 annually.

What are the most commonly searched types of Reliability Engineer jobs in Lenexa, KS?

The most popular types of Reliability Engineer jobs in Lenexa, KS are:

What are popular job titles related to Reliability Engineer jobs in Lenexa, KS?

For Reliability Engineer jobs in Lenexa, KS, the most frequently searched job titles are:

What job categories do people searching Reliability Engineer jobs in Lenexa, KS look for?

The top searched job categories for Reliability Engineer jobs in Lenexa, KS are:

What cities near Lenexa, KS are hiring for Reliability Engineer jobs?

Cities near Lenexa, KS with the most Reliability Engineer job openings:

Infographic showing various Reliability Engineer job openings in Lenexa, KS as of August 2026, with employment types broken down into 88% Full Time, 7% Part Time, 1% Temporary, and 4% Contract. Highlights an 85% Physical, 6% Hybrid, and 9% Remote job distribution, with an average salary of $110,743 per year, or $53.2 per hour.

SRE DevOps Engineer

Highbrow LLC

Overland Park, KS • On-site

$110 - $130/hr

Other

Posted 2 days ago

New


Job description

SRE DevOps Engineer

Location: Overland Park, KS / Atlanta, GA / Frisco, TX (Onsite)

Requirements
  • 4–9 years in SRE/DevOps/Systems Engineering as Senior or Principal Engineer
  • Strong hands‑on experience with Kubernetes, container orchestration, and API management.
  • Working knowledge of WAFs, networking security, and database technologies (SQL/NoSQL).
  • Proficient in automation and scripting (Python, Go, Ansible, Terraform, etc.)
  • Strong observability/monitoring experience.
  • Experience with CI/CD pipelines, GitOps, and infrastructure as code.
  • Solid problem‑solving and collaboration skills.
Job Responsibilities
  • Resolve escalated incidents across Kubernetes, API Proxy, WAF, DBs, and infra platforms.
  • Design and improve runbooks, automating manual steps wherever possible.
  • Lead and contribute to building self‑healing systems and self‑service tooling for users.
  • Analyze incident trends, propose improvements in monitoring, capacity, and reliability.
  • Collaborate with engineering teams on deployment, upgrades, and performance optimization.
  • Conduct postmortems, document RCA, and ensure learning is captured.
  • Mentor and coach L1 engineers.
SkillsMandatory Skills (Must-Have)
  1. Advanced Incident Troubleshooting & Resolution

    Expectation: Diagnose and resolve escalated incidents that L1 cannot handle, often across multiple layers (infrastructure, application, network).

    Example: For an API outage, identify if the root cause is in Kubernetes pod networking, APIgateway misconfig, or backend DB latency — and apply fixes.

  2. Kubernetes & Container Orchestration Expertise

    Expectation: Comfortable with deployments, scaling, networking, and debugging cluster‑level issues.

    Example: Troubleshoot why pods are pending by checking node capacity, taints/tolerations, and cluster autoscaler logs.

  3. Automation & Scripting (Python, Go, Bash, Ansible, Terraform)

    Expectation: Write scripts and automation to reduce manual toil, enhance monitoring, and improve incident resolution speed.

    Example: Develop a Python script to automatically collect pod and system logs when a service crashes.

  4. Observability & Monitoring Tooling

    Expectation: Deep understanding of monitoring, alerting, tracing, and logging systems.

    Example: Build Prometheus alert rules to detect DB query spikes; configure Grafana dashboards for API latency.

  5. CI/CD & Infrastructure as Code (IaC)

    Expectation: Familiarity with GitOps workflows, CI/CD pipelines, and infrastructure provisioning.

    Example: Enhance Jenkins pipeline to add automated smoke tests before promoting Kubernetes deployments.

  6. Database Troubleshooting (SQL & NoSQL)

    Expectation: Identify performance bottlenecks, connection issues, and basic tuning opportunities.

    Example: Run queries to detect slow‑running SQL statements causing latency in an application.

  7. Incident Management & RCA

    Expectation: Act as incident commander for escalated issues, lead bridge calls, and produce Root Cause Analyses.

    Example: After a WAF misconfiguration causes downtime, lead the investigation, document the timeline, and propose preventive actions.

  8. Mentorship & Runbook Improvement

    Expectation: Coach L1 engineers, refine runbooks, and introduce new automated workflows.

    Example: Update a runbook to add automated Kubernetes log collection instead of manual steps.

Preferred Skills (Nice-to-Have)
  1. Cloud Platform Engineering (AWS, Azure, GCP)

    Expectation: Hands‑on skills in provisioning, scaling, and securing cloud workloads.

    Example: Diagnose why an AWS ALB is misrouting traffic after a deployment.

  2. Security & WAF Management

    Expectation: Understand WAF rules, common attacks (SQL injection, XSS), and how to apply fixes.

    Example: Investigate false positives in WAF logs and adjust rule sets with security teams.

  3. Capacity & Performance Engineering

    Expectation: Anticipate scaling needs, tune resource utilization, and propose optimizations.

    Example: Identify that a Kubernetes deployment is CPU‑throttled and adjust HPA (Horizontal Pod Autoscaler) configs.

  4. Automation Platform Integration (AIOps, ChatOps)

    Expectation: Integrate AI/ML‑powered tools for anomaly detection and auto‑remediation.

    Example: Implement a ChatOps bot that runs predefined Kubernetes troubleshooting commands in Slack.

  5. Cross‑Platform Expertise (Hybrid Infra)

    Expectation: Experience supporting both on‑prem and cloud environments seamlessly.

    Example: Compare latency patterns between on‑prem DBs and cloud‑hosted APIs to identify bottlenecks.

#J-18808-Ljbffr