Synchronoss Site Reliability Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 8 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Synchronoss.
Synchronoss
Site Reliability Engineer
Senior Average Neutral experience Accept offer 2 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Behavioral Technical
It started with a quick phone screen, then moved on to about 2-3 hours of in-person interviews. It was pretty typical, no curveballs. Mostly, they wanted to hear about my past experiences and how I handled issues. The focus was more on my thinking and problem-solving skills, not really on specific algorithms or software. Oddly, none of the questions seemed directly related to Site Reliability Engineering, which is what I applied for. Soon after, they announced a hiring freeze, which I figured meant they weren't interested. Then, out of the blue, two months later, they called to see if I was still interested. I'm still convinced they couldn't find anyone better or cheaper. Some of the interviewers seemed unprepared, without questions or knowledge of my resume.
Confirmed questions1 question
- Can you describe a time you managed a critical production outage (sev 1)?
Synchronoss
Site Reliability Engineer
Mid Difficult Positive experience Accept offer 5 rounds
Interview process
Phone screen Onsite
Interview formats
Technical Coding
So, I went through about 3 or 4 phone screens, and then there was one in-person interview. They asked me stuff about using Python, Ruby, and shell scripting for automating infrastructure. I also had to answer questions about using AWS CloudFormation templates, RDS, and RAID disks. The whole thing felt pretty friendly and straightforward, they made me feel super comfortable and at ease. The on-site part was like 3-4 hours, and the phone calls were each about 30 minutes.
Confirmed questions2 questions
- Could you describe how you'd use a Chef recipe to automate Nginx webserver deployment?
- Explain the process of adding a disk to a RAID 0 array on AWS EC2 using Linux.
Synchronoss
Site Reliability Engineer
Mid Average Positive experience Decline offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Technical Behavioral
The interview process was positive. The team was knowledgeable and it was a good conversation. They asked a lot of standard questions, some probing deeper. Most were technical, but there were a few situational ones about customer interactions. The Seattle office seemed small, which I liked.
Confirmed questions4 questions
- Questions about Chef scripting.
- Questions about Python scripting.
- A few questions about how you've interacted with customers.
Synchronoss Site Reliability Engineer Interview Questions
Quoted word for word from Synchronoss interview reports.
“If a file named '-rf /' exists on the root of a drive, what steps would you take to remove it?”
Read reports →“Suppose a machine reports its disk is full, yet the 'df' command indicates the drive is not full. What other potential issues could be causing this discrepancy?”
Read reports →“How would you determine the list of servers and their filesystem utilization?”
Read reports →“Can you list the different types of SSL certificates?”
Read reports →“Using a shell script, what would be your approach to find the servers and check filesystem utilization?”
Read report →“What are the methods for package management on Linux?”
Read report →“Could you walk me through the Linux boot process?”
Read report →“Can you explain LVM?”
Read report →“Could you describe how you'd use a Chef recipe to automate Nginx webserver deployment?”
Read report →Formats, difficulty and experience
Across all 8 Synchronoss interview reports.