Site Reliability Engineer United States, Remote

Site Reliability Engineer

United States, Remote

Are you driven to be an innovative Site Reliability Engineer, and looking to join a team where open collaboration, customer focus, and a commitment to excellence are core values?

At , we work passionately and authentically, striving to win together and make a real impact for our customers and each other. Join us to elevate your career and help deliver innovative solutions in a dynamic, empowering environment.

Why this role matters:

The Site Reliability Engineering role is a blend of infrastructure, networking, operating systems, automation, development, and application administration. It is a hands-on technical position in a fast-paced atmosphere. The ideal candidate has prior experience managing cloud-based SaaS applications and strives to solve traditional operations problems through automation and software. More so, the candidate must possess a high standard of excellence, have a strong customer focus, and is capable of technical deep dives into code, app servers, databases, load balancers, operating systems, and networks.

Site Reliability Engineering (SRE) is a growing team that partners closely with Product Engineering, Security, and Support. We are responsible for the reliability, deployment, and continuous operation of the Cloud services. We need your help to take our existing platform to the next level with observability, release automation, chaos engineering, and more.

What you'll do:

Work 4 x 10-hour days (Wednesday through Saturday, approximately 9 AM to 8 PM U.S. Pacific Time, including lunch)

Deploy, manage, and secure production Software-as-a-Service (SaaS) environments in AWS and Azure

Work with a geographically dispersed, cross-departmental teams to solve difficult problems

Automate common and repetitive tasks

Write documentation and training material

Train other colleagues

Participate in on-call rotations for 24x7 coverage (follow-the-sun model) for incident response, issue triage, and problem resolution

What you will bring:

US citizenship and must be located domestically in the U.S.

A BSc in Computer Science, a related field, or equivalent practical experience

3+ years of relevant industry experience (2+ with an achieved BSc in Computer Science or Equivalent Degree)

Proficiency with Python and experience with one of the following languages:

Java

Golang

C#

Proficiency working with Bash or PowerShell programmatically

Familiarity with public cloud platforms (AWS or Azure preferred)

Experience troubleshooting Java and .NET applications

Experience troubleshooting network and storage infrastructure issues

Experience working with core Linux distributions (Debian, RHEL, SUSE, Slackware)

Experience working with Windows

Experience working with one or more: SQL Server, PostgreSQL, Redis, Kafka, MongoDB, Elasticsearch, or similar

Ability to configure and fine tune at least one: HA Proxy, Apache, Nginx, IIS, or similar

Ability to configure: New Relic, DataDog, Splunk, or similar monitoring tools

Familiarity with container orchestration technologies (AWS EKS or Azure AKS preferred)

Experience with deployment pipeline tools such as Ansible, Jenkins, and/or GitHub Actions

Proficiency working and developing Infrastructure as Code (IaC)

Working Place:

Remote, Oregon, United States

Company :

ESR Healthcare
Back to blog

Other Jobs To Apply

No other job posts for this day.

Common Interview Questions And Answers

1. HOW DO YOU PLAN YOUR DAY?

This is what this question poses: When do you focus and start working seriously? What are the hours you work optimally? Are you a night owl? A morning bird? Remote teams can be made up of people working on different shifts and around the world, so you won't necessarily be stuck in the 9-5 schedule if it's not for you...

2. HOW DO YOU USE THE DIFFERENT COMMUNICATION TOOLS IN DIFFERENT SITUATIONS?

When you're working on a remote team, there's no way to chat in the hallway between meetings or catch up on the latest project during an office carpool. Therefore, virtual communication will be absolutely essential to get your work done...

3. WHAT IS "WORKING REMOTE" REALLY FOR YOU?

Many people want to work remotely because of the flexibility it allows. You can work anywhere and at any time of the day...

4. WHAT DO YOU NEED IN YOUR PHYSICAL WORKSPACE TO SUCCEED IN YOUR WORK?

With this question, companies are looking to see what equipment they may need to provide you with and to verify how aware you are of what remote working could mean for you physically and logistically...

5. HOW DO YOU PROCESS INFORMATION?

Several years ago, I was working in a team to plan a big event. My supervisor made us all work as a team before the big day. One of our activities has been to find out how each of us processes information...

6. HOW DO YOU MANAGE THE CALENDAR AND THE PROGRAM? WHICH APPLICATIONS / SYSTEM DO YOU USE?

Or you may receive even more specific questions, such as: What's on your calendar? Do you plan blocks of time to do certain types of work? Do you have an open calendar that everyone can see?...

7. HOW DO YOU ORGANIZE FILES, LINKS, AND TABS ON YOUR COMPUTER?

Just like your schedule, how you track files and other information is very important. After all, everything is digital!...

8. HOW TO PRIORITIZE WORK?

The day I watched Marie Forleo's film separating the important from the urgent, my life changed. Not all remote jobs start fast, but most of them are...

9. HOW DO YOU PREPARE FOR A MEETING AND PREPARE A MEETING? WHAT DO YOU SEE HAPPENING DURING THE MEETING?

Just as communication is essential when working remotely, so is organization. Because you won't have those opportunities in the elevator or a casual conversation in the lunchroom, you should take advantage of the little time you have in a video or phone conference...

10. HOW DO YOU USE TECHNOLOGY ON A DAILY BASIS, IN YOUR WORK AND FOR YOUR PLEASURE?

This is a great question because it shows your comfort level with technology, which is very important for a remote worker because you will be working with technology over time...