
Redis Technical Support Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 11 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Redis.
Technical Support Engineer
After the home assignment, you get to a whiteboard session. There, for 1.5 hours, you get to discuss scenarios. They essentially describe how Redis works. The last stage is a mix of tech and behavior questions. Surprisingly it's the longest one and actually may last over 3 hours (supposedly 2). You might get asked for a pretty granular description of things that you might not essentially know.
- Could you explain how Redis AOF backup functions?
- What is the mechanism behind Redis HA?
- How is Redis cluster configured and operated?
Technical Support Engineer
The interview started with an HR screen, followed by a call with the hiring manager. Unfortunately, the hiring manager missed the initial scheduled interview, requiring a reschedule. The subsequent call with the hiring manager was a rapid-fire session focused on their preferred Linux commands, with no situational questions asked. I had to debate with the hiring manager about alternative correct methods for executing commands in Linux. A technical assignment was then given, which involved configuring Redis on two servers, setting up replication, and writing simple code to inject and retrieve data using a specific data type. I successfully passed this assignment. The next stage was supposed to be an in-depth discussion of the assignment. However, after a brief 5-minute discussion about the assignment, the focus shifted to quizzing me on the optimal way to deploy Redis. Although I was given freedom in my deployment suggestions, my correct answers and explanations were dismissed. This occurred even when I described previously deployed scenarios and demonstrated strong knowledge. Following this, I was rejected. The entire process felt chaotic and disorganized, and the interview content didn't align with the job description. My impression is that the interviewers were solely focused on validating their own knowledge rather than assessing my suitability for the role, which I believe is a flawed approach to candidate interviews. This company appears to have a chaotic and stressful work environment.
- Regarding Redis, what data type would you select?
Technical Support Engineer
So, the interview process was like this: First, a video call on Zoom with the recruiter. They asked me some general Linux questions and commands. Then, there was a technical round where they asked about the boot process, Redis, and things on my resume. After that, I got a task to do in about 6-7 hours, which was to install and configure Redis-cluster and replicate data. There was another technical round, and finally, a round with the Hiring Manager.
- Recruiter asked general Linux questions and commands via Zoom video call.
- Technical round covered the boot process, Redis questions, and resume topics.
- Given a task to complete in 6-7 hours for Redis-cluster installation, configuration, and data replication between nodes.
Redis Technical Support Engineer Interview Questions
Quoted word for word from Redis interview reports.
“Create a Redis DB on Redis Enterprise Software.”
Read reports →“What are the differences between NFS and FTP?”
Read reports →“What is the mechanism behind Redis HA?”
Read reports →“Can you explain how nslookup functions?”
Read reports →“Describe the Linux booting process.”
Read report →“How is Redis cluster configured and operated?”
Read report →“How do emails work?”
Read report →“When and how would you use telnet?”
Read report →“How would you find indexes in a list using logic?”
Read report →Formats, difficulty and experience
Across all 11 Redis interview reports.