1

Junior Reliability Engineer Jobs in Indiana (NOW HIRING)

Senior Software Engineer

Crane, IN · On-site

$122K - $161K/yr

The ideal candidate is a disciplined engineer who values clarity, reliability, and thoughtful ... Mentor junior software engineers and help establish a culture of engineering excellence. Required ...

Senior Software Engineer

Crane, IN

$122K - $161K/yr

The ideal candidate is a disciplined engineer who values clarity, reliability, and thoughtful ... Mentor junior software engineers and help establish a culture of engineering excellence. Required ...

Senior Controls Engineer

Portage, IN · On-site

$89K - $117K/yr

... reliability and performance. * Direct the optimization of control systems to achieve superior ... Mentor junior controls engineers and technical staff, fostering a culture of continuous learning ...

The successful candidate will oversee initiatives from concept through construction, mentor junior ... Our team of experts takes pride in our commitment to reliability in design, connection to our ...

Senior Data Engineer

Zionsville, IN · On-site

$102K - $139K/yr

... reliability * Establish data quality frameworks and validation processes to ensure accuracy and completeness of data across the organization * Mentor junior and mid-level engineers on data ...

next page

Showing results 1-20

Junior Reliability Engineer information

See Indiana salary details

$31.9K

$68.3K

$104.2K

How much do junior reliability engineer jobs pay per year?

As of Jul 11, 2026, the average yearly pay for junior reliability engineer in Indiana is $68,322.00, according to ZipRecruiter salary data. Most workers in this role earn between $46,200.00 and $76,100.00 per year, depending on experience, location, and employer.

What are the key skills and qualifications needed to thrive as a Junior Reliability Engineer, and why are they important?

To thrive as a Junior Reliability Engineer, you need a solid understanding of engineering principles, data analysis, and reliability concepts, often supported by a bachelor's degree in engineering or a related field. Familiarity with reliability modeling software, failure mode and effects analysis (FMEA) tools, and data collection systems is typically important. Strong problem-solving skills, attention to detail, and effective teamwork make someone stand out in this position. These skills and qualities are vital for accurately identifying potential failures, improving system performance, and ensuring equipment reliability in various industries.

What is the difference between Junior Reliability Engineer vs Reliability Technician?

AspectJunior Reliability EngineerReliability Technician
CredentialsTypically requires a degree in engineering or related fieldUsually has technical certifications or vocational training
Work EnvironmentInvolves analysis, planning, and collaboration with engineering teamsHands-on maintenance and troubleshooting of equipment
Employer & Industry UsageUsed in manufacturing, energy, and industrial sectors for proactive reliability

The Junior Reliability Engineer focuses on analyzing data, developing reliability strategies, and working with engineering teams to improve system performance. In contrast, the Reliability Technician performs direct maintenance and repairs. Both roles support equipment uptime but differ in their responsibilities and required qualifications.

What are some common challenges faced by Junior Reliability Engineers in their first year, and how can they overcome them?

Junior Reliability Engineers often encounter challenges such as understanding complex equipment systems, learning to use reliability analysis tools, and adapting to fast-paced problem-solving environments. It's important to proactively seek mentorship from senior engineers, participate in hands-on training, and familiarize yourself with key reliability metrics and predictive maintenance techniques. Collaborating closely with maintenance teams and other engineering departments will also help you gain practical insights and contribute effectively to reliability improvement initiatives.

What does a Junior Reliability Engineer do?

A Junior Reliability Engineer assists in evaluating the reliability and performance of products, systems, or processes to ensure they meet quality and safety standards. Their responsibilities often include collecting and analyzing data, identifying potential failure points, and supporting the development of maintenance strategies. They work under the guidance of senior engineers to improve equipment reliability and reduce downtime. This role typically involves collaboration with other engineering and operations teams to implement solutions and monitor improvements.
What are the most commonly searched types of Reliability Engineer jobs in Indiana? The most popular types of Reliability Engineer jobs in Indiana are:
What cities in Indiana are hiring for Junior Reliability Engineer jobs? Cities in Indiana with the most Junior Reliability Engineer job openings:
Senior Network Reliability Engineer

Senior Network Reliability Engineer

Group 1001

Indianapolis, IN • On-site

Full-time

Posted 27 days ago


Group1001 rating

9.5

Company rating: 9.5 out of 10

Based on 8 frontline employees who took The Breakroom Quiz

9th of 281 rated insurance


Job description

Job Summary:
Group 1001 is a consumer-centric, technology-driven family of insurance companies focused on delivering outstanding value and operational performance. They are seeking a Senior Network Reliability Engineer to build and implement Site Reliability Engineering practices, applying SRE principles to enhance the firm's network platform and ensure reliability across multi-cloud environments.
Responsibilities:
• Treat reliability as an engineered property. Define SLOs and error budgets for the network platform — DNS resolution, edge availability, mesh ingress success, cross-region path health — and use them to gate changes, not just to color dashboards. Lead postmortems with a focus on permanent remediation, not pattern-recognition. Alert on symptoms users feel, not on causes that may or may not produce impact.
• Move network state into code. Use Terraform (or Pulumi), Ansible, and Python to replace CLI-driven configuration with declarative, version-controlled, peer-reviewed change running through Infra CI/CD. This applies equally to the edge tier (Cloudflare), security platforms (Zscaler ZIA/ZPA, ZTNA policies, next-gen firewalls), the cloud network fabric (Transit Gateway, Cloud WAN, VPCs, Route53, IPAM), and increasingly the Kubernetes and service-mesh layer.
• Build network policy as intent, not rule lists. Express what flows are permitted, what segments are isolated, what egress is inspected, what zones share DNS — and engineer the compilers that turn that intent into per-vendor configuration. Use Policy as Code (OPA/Rego, Sentinel, Cilium NetworkPolicy) to catch invariant violations at plan time, not apply time.
• Infrastructure as Code (IaC): Design, deploy, and manage network infrastructure using Terraform or Ansible, moving the firm away from manual configuration to a code-first approach.
• Engineer the cloud network platform. Operate and extend our multi-account AWS Landing Zone — Cloud WAN segmentation, Transit Gateway peering, IPAM-driven CIDR allocation, shared private DNS, cross-account telemetry pipelines. Build the platform abstractions that make a new account or service land correctly with policy and connectivity composed from declarative inputs.
• Extend platform thinking into the container tier. Kubernetes networking, service mesh (Istio, Linkerd, Consul Connect), eBPF-based observability and policy (Cilium, Hubble), and the integration points where mesh-level authz meets cloud-tier identity. Recognize that an "internal" service is one logical hop on a chain of policy enforcement points and engineer for that explicitly.
• Improve telemetry and observability with intent. Build alerts as structured payloads with runbook links, suspected blast radius, and dependency-aware suppression. Author both system-health dashboards for operators and end-user monitoring dashboards that reflect actual user experience. Use Grafana, Elastic, Open Telemetry where each fits.
• Mentor and grow the team. Provide technical guidance to junior engineers, foster a culture of learning, and work out loud across Platform Engineering so the patterns you build cross-pollinate to adjacent domains.
• Handle hardware when required. Provide maintenance and configuration support for routers, switches, and firewalls at data centers and offices when needed — bringing code-first practices to physical hardware where possible (templating, change validation, zero-touch provisioning) and direct hands-on competence where it isn't.
• Incident Response: Serve as an escalation point for network issues, some complex and some basic but not yet covered by runbooks. Troubleshooting with a focus on root cause analysis and permanent remediation with a documentation-first mindset.
• Reduce toil and hand off cleanly. Repetitive operational tasks are scoped engineering problems with measurable payoff. Author runbooks and SOPs that the NOC can execute confidently; package routine work for L1/L2 handoff so engineering interrupt drops over time. Coordinate across Data Platforms, NOC/SOC, and Cyber Security so reliability practices spread instead of staying siloed.
Qualifications:
Required:
• Deep understanding of TCP/IP, BGP, OSPF, VPNs, and SD-WAN architecture.
• Proven experience with Terraform (state management, modules) and Ansible (playbooks, roles) – or similar – in a production environment.
• Proficiency in Python for automation and API interaction, or similar.
• Hands-on experience with Cloudflare, zScaler, and/or enterprise firewalls.
• Experience configuring monitoring tools (e.g., Datadog, Prometheus, Grafana) to create meaningful alerts and dashboards.
Preferred:
• Service mesh experience (Istio, Linkerd, Consul Connect, Cilium).
• eBPF-based observability (Hubble, Pixie).
• AWS Multi-account landing zone tooling experience (AFT, Control Tower, or equivalent).
• Policy as Code experience (OPA/Rego, Sentinel, Cilium NetworkPolicy).
• Documentation First: A strong belief that a job isn't done until the documentation in written.
• Toil Reduction: A mindset that actively seeks to automate repetitive tasks.
• Hybrid Capability: Willingness to handle physical hardware tasks when required while maintaining a software-centric engineering mindset.
Company:
Group 1001 is a collective that empowers companies to create positive growth. Our insurance and annuities are easy to understand and accessible to all. Founded in 2013, the company is headquartered in Zionsville, USA, with a team of 1001-5000 employees. The company is currently Late Stage.

What Group1001 employees say

Pay

Benefits

Hours and flexibility

Workplace

Get the full story on Breakroom