Tip 1: Be well aware of the tech stack you use in your day-to-day work.
Tip 2: If you have any scheduled interviews, pull up the latest 50/100 asked questions from coding ninja and practice it way
Tip 3: You must practice system Design. In my case, I used to discuss various system design problems with my office colleagues every evening. This personally helped me a lot.
Tip 1: Show the impact of your work
Tip 2: You must include required stats and keywords in your resume
This round started with the introduction, followed by the overview of the work I do in my role currently along with the tech stack I use.
Then it got two medium level hashMap/string related DSA problem.



Suppose given input is "abacb", then the length of the longest substring without repeating characters will be 3 ("acb").
I started off with basic approach and then kept on optimising it. I don't remember the exact things i did but this is the approach that i follow in general.
Here, there were 2 sections of this round, in first half, I got a problem statement that I had to solve using the OOPs concept.
In the second half, we had discussion around kafka (this being the major component of my current work profile). The discussion included the basis and in depth questions about topics, partition, broker, messaging queue along with the scenario based problem. If you have worked with kafka, you should be smoothly able to deal with this
Design and Implement a Chess Game . (Learn)
Tip 1: You don’t need to present the whole working solution just make sure to explain everything you are thinking with example along with the pseudo code of the approach.
It was a total design based round, where I was asked to design a whatsapp like system where user should be able to chat, group-chat, voice-call, video-call and set the status.
I was asked to design a whatsapp like system where user should be able to chat, group-chat, voice-call, video-call and set the status.
Tip 1: Clearly call out the usecases and requirements before starting
Tip 2: Think out loud so that interviewers can correct you if you go in wrong direction.
It was a total design related round. In the first 30min, I was asked the question to make a DBaaS.
In the next half, I was given a table structure and was asked to write a SQL query to get the required data from the table.
It followed up with the discussion around database topics like Unique key, primary key, advantages-disadvantages of sql vs no-sql(Learn), indexing(Learn) and sharding(Learn).
Expose an API solution where clients will have the flexibility to choose any kind of database they wish(SQL, No-SQL, Cache, DocDB etc.) along with the flexibility to do CRUD operation on their data.
Tip 1: Clear the requirements before starting.
Tip 2: Keep the interviewer on the same page, otherwise it creates a lot of problems
This round was more of like a behavioural round to check the cultural fit. I was asked a lot of scenario based question and decision taking challenges. It was nothing different from other companies behavioural round.
After this, I got a call from HR next Monday with the acceptance news and we discussed about the compensation.
Tell me a good and bad thing about your colleagues
Tip 1: Be realistic and explain the reason for your choice. If possible, give the real incident that supports your answer

Here's your problem of the day
Solving this problem will increase your chance to get selected in this company
What is recursion?