Taro Logo

Site Reliability Engineer Interview Experience - Bengaluru, India

November 1, 2019
Positive ExperienceGot Offer

Process

I was contacted by one of the HRs on LinkedIn, who told me about the company and the interview process. I had heard about the company before and was interested in interviewing.

There were a total of 5 rounds:

  • Coding Round
  • Scripting Round
  • Operational Round
  • Design Round
  • Behavioral Round

Each round was 1 hour long and conducted on Zoom. The HR was very helpful in scheduling and rescheduling interviews, especially since I was on vacation after my first interview.

Overall, it was a great experience. The interviewers were quite knowledgeable and experienced, going in-depth as much as possible.

My first round was the coding round, taken on CoderPad. I was given two different CSVs to parse and merge based on certain rules, filter out specific data according to certain rules, calculate a mathematical entity, and finally sort them in decreasing order, printing the corresponding metadata of the processed data. The interviewer was helpful in giving clues and correcting mistakes.

The second round was the scripting round, where basic and in-depth questions related to Linux were asked. In addition, in-depth questions about Docker, its working, orchestration, clustering, and scheduling capabilities were covered.

The third round started with a very basic system layout, and I was asked to expand the system, considering new resource additions and changing user requirements.

The fourth round was the design round. I was given a design question three days prior to the interview and had to prepare a report, describing everything from scratch: service dependencies, data modeling, cloud architecture, etc. Again, the interviewer went in-depth, which was quite good.

Overall, the company is run and managed by some really good people. They are systematic, smart, and very professional. I believe I had the best interview experience with this company.

Questions

Parse two different CSVs and merge them based on certain rules. Filter out data based on specific criteria. Calculate a designated mathematical entity, then sort the results in decreasing order and print the corresponding metadata of the processed order.

Difference between Docker daemon, Docker Machine, and Virtual Machine.

Networking questions for debugging, such as how traceroute and ping can assist in debugging.

Describe the layering concept in Docker.

Given a game running on an instance with MySQL installed locally, and with the game's popularity increasing, suggest ways to ensure it remains highly secure and highly available. Include considerations for using JWT, its applicability, and session maintenance.

Was this helpful?

Interview Statistics

The following metrics were computed from 1 interview experience for the Confluent Site Reliability Engineer role in Bengaluru, Karnataka.

Success Rate

100%
Pass Rate

Confluent's interview process for their Site Reliability Engineer roles in Bengaluru, Karnataka is incredibly easy as the vast majority of engineers get an offer after going through it.

Experience Rating

Positive100%
Neutral0%
Negative0%

Candidates reported having very good feelings for Confluent's Site Reliability Engineer interview process in Bengaluru, Karnataka.

Confluent Work Experiences