Tip 1: Be confident in what you have learned so far.
Tip 2: Be consistent in learning.
Tip 3: Work on interview preparation and speaking skills.
Tip 1: Be honest about your resume.
Tip 2: Show numbers and measurable impact in your resume, especially in projects.
The round consisted of MCQs and a coding question. We had to sit at the allocated seats in the college labs and complete the test under the invigilation of the teachers. The MCQ duration was 120 minutes, and the coding duration was 60 minutes.
To solve the problem, first read the problem thoroughly and then dry run the test cases. Start with the brute-force approach and refactor or optimize it accordingly.
Flow graph of my thinking:
Go from 1 to m → check each number → add divisible numbers to one sum → add non-divisible numbers to another sum → finally, calculate the difference between the two sums.
This was a communication round. The questions were based on listening, reading, and communication skills. In the test, we needed to listen to the instructions and answer accordingly. We were required to sit in a quiet, well-lit room. The round was conducted online and was taken from our own rooms.
In the test, we had to answer the questions by listening to an auto-generated voice. We were asked to fill in the blanks based on what we heard. There was also a “speak about yourself” test for 5 minutes. Additionally, there was a reading test in the communication round.
Tip 1: Be careful while listening to the sentences.
Tip 2: Be confident and attentive.
Tip 3: Speak loudly and clearly.
This round was a managerial and HR round. The assigned interviewer joined at the scheduled time provided via email. They asked questions based on different scenarios, and the final offer rollout was decided based on this round.
Tip 1: Be confident in every question.
Tip 2: Be honest about yourself and your projects.
Tip 3: Work hard on your communication skills.

Here's your problem of the day
Solving this problem will increase your chance to get selected in this company
What's the main risk of a "Chat with Your Codebase" public API tool?