
Lightspeed Site Reliability Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 12 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Lightspeed.
Site Reliability Engineer
I started with HR, answered some standard questions, and passed that. Then, I had a technical interview with manager Keith and two senior engineers, Charles and Xavier. It was a really positive experience; Keith made me feel comfortable and smart. Charles and Xavier were respectful, even when I didn't have the right answers. They asked a lot of verbal questions about troubleshooting, design, and K8S. The only hands-on part was writing a function to parse URL results, and they provided all the necessary tools, which was great. Keith encouraged using any tools needed, making it a fantastic interview. Unlike other places that expect you to know everything, Lightspeed acknowledged that using the internet is realistic. Even though I probably didn't get the job, the experience was refreshing and made me feel good about my current standing.
- Troubleshooting questions about Linux, K8S, and Databases.
- Questions about architecture and how you would handle various scenarios.
- A coding exercise involving passing a URL to a function via CLI to parse and return content, with some challenges.
Site Reliability Engineer
The interview process had four main parts: first, a chat with the recruiter. Then, a technical assessment where I did coding exercises and answered technical questions with the team. After that, I interviewed with the team manager. Finally, there was a session with the technical team focusing on architecture and problem-solving discussions. The team at Lightspeed really designs questions that make you think critically and show how you approach problems. It's a good way to show what you know without feeling like you have to get it perfect right away. The conversations were good, and the team made it comfortable to show my skills.
- We'll discuss SRE architecture designs, best practices, and your experiences.
- Describe how an SRE implementation could work in an end-to-end environment.
- We'll do some coding exercises.
Site Reliability Engineer
The interview process stretched over six weeks, which felt excessively long. The team was unresponsive to follow-up questions or feedback requests after interview stages, yet they proceeded to invite me to subsequent stages. The initial phase involved an HR interview, followed by a one-hour technical interview, and then a 1.5-hour architect interview. While the interviewers were pleasant and friendly, the company appeared disorganized. Initially, the role was advertised as remote in the UK, but then they unexpectedly decided to conduct an on-site interview in Belfast, which ultimately led to me not moving forward. It was quite a mess. I would expect a large company like Lightspeed to have sufficient staff to manage the interview process and provide timely responses to candidates.
- Could you design an architecture for deployment pipelines targeting Kubernetes clusters?
Lightspeed Site Reliability Engineer Interview Questions
Quoted word for word from Lightspeed interview reports.
“Can a Dockerfile be created from a running container?”
Read reports →“Can you write a script to pull data from an open API and then format it nicely?”
Read reports →“Could you design an architecture for deployment pipelines targeting Kubernetes clusters?”
Read reports →“Describe how an SRE implementation could work in an end-to-end environment.”
Read reports →“What's your perspective on managing costs when working in the cloud?”
Read report →“What is your experience with Kubernetes?”
Read report →“Was there an HR Screening?”
Read report →“Do you have any questions related to the SRE field?”
Read report →“Can you walk me through the small coding exercise?”
Read report →Formats, difficulty and experience
Across all 12 Lightspeed interview reports.