Skip to main content
David Careers

Jr. Site Reliability Engineer (SRE)

Posted 2 days ago

acestackAddison (TX)
Computer Systems Engineers/ArchitectsComputer Systems Design Services

SENIORITY

Mid

Apply (opens in a new tab)

About the role

Job Description: Jr. Site Reliability Engineer (SRE)
Location: Addison, TXFull-TimeJob Description
We are looking for a motivated and detail-oriented Junior Site Reliability Engineer (SRE) to join our engineering team in Addison, TX. The ideal candidate will support the reliability, availability, performance, and scalability of applications and infrastructure. This role is suitable for someone with foundational knowledge of Linux, cloud platforms, scripting, monitoring, and troubleshooting who is eager to grow in Site Reliability Engineering and DevOps practices.
Key Responsibilities: Monitor application performance, system health, availability, and infrastructure metrics. Assist in identifying, troubleshooting, and resolving production incidents. Support incident management, root cause analysis, and problem resolution. Work with development and operations teams to improve system reliability and performance. Configure and maintain monitoring, logging, and alerting tools. Assist with automation of routine operational tasks using scripting. Support CI/CD pipelines and application deployment processes. Help manage cloud infrastructure and environments. Perform basic system administration tasks in Linux environments. Participate in on-call support and follow established incident response procedures, as required. Maintain technical documentation, operational runbooks, and troubleshooting guides. Identify repetitive manual tasks and recommend opportunities for automation. Follow best practices for system security, backup, disaster recovery, and operational reliability. Required Technical SkillsBasic knowledge of Site Reliability Engineering (SRE), DevOps, and IT operations. Familiarity with Linux/Unix operating systems and basic command-line troubleshooting. Basic scripting experience with Python, Bash, or Shell. Understanding of networking concepts such as DNS, TCP/IP, HTTP/HTTPS, and load balancing. Familiarity with monitoring and logging tools such as Grafana, Prometheus, Splunk, or ELK Stack. Basic understanding of cloud platforms such as AWS, Microsoft Azure, or Google Cloud Platform (GCP).Knowledge of Git and version control. Familiarity with CI/CD tools such as Jenkins, GitHub Actions, or GitLab CI/CD.Understanding of application troubleshooting, system performance, and incident management. Basic knowledge of containers such as Docker; Kubernetes exposure is a plus.
Preferred Qualifications:
  • Exposure to Infrastructure as Code (IaC) tools such as Terraform or Ansible.
  • Familiarity with Service Level Indicators (SLIs), Service Level Objectives (SLOs), and Service Level Agreements (SLAs).Understanding of high availability, scalability, fault tolerance, and disaster recovery.
  • Exposure to IT service management and ticketing tools such as Service
  • Now or Jira.
  • Basic knowledge of databases, SQL, and application server environments.
  • Internship, academic project, or professional experience in DevOps, cloud operations, system administration, or production support.

Before you apply

Applying takes about a minute. These four things decide how fast it moves after that.

Your profile is current

It's what we read first. Occupations, seniority and locations matter more than a long history.

Two examples you can talk through

Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.

A number in mind

What you're on now and what would make you move. We negotiate better when we know both.

Your notice period

Employers plan around it, and it's the question that stalls offers most often.

Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.

More like this