1. Codelity : 4 questions on Angular, sql, .net and java. They are moderate, one could do it with minimum preparation.
2. Telephonic Screening - They will focus on your codelity round and your approaches. They
asked 2-3 coding questions. The level of these questions depends on the interviewer. For me,
I felt 2 of them were easy and the other took some time but I could do it.
3. Onsite Interview:
1. Behavioural - stay cool and answer them how you usually handle within your team
efficiently.
2. Quality Assurance - They focus on your approach for coding to minimize bugs and how
efficiently you could code within the deadline.
3. OOPS - Basic java questions on oops concepts and given a problem and the interviewer will
assess your approach in achieving it. Mostly it is whiteboarding but if you are good at oops
concepts, you are fine.
4. Algorithms: Interviewer asked me about Graphs and graph traversing algorithms. He
asked me to write pseudocode for a few of them. I missed handling a few edge cases, but he
sounded okay.
5. This is where I think I got screwed up, some other manager has come along with the interviewer. He didn't let her ask any questions and he took all the time asking basic questions which I did well and I was appreciated.
Got a response from HR that am good in algorithms but not in databases and data structures and database. None of the interviewer panels asked me any question regarding Database. I solved my algorithm questions using Data structures (Arrays, Queues, Stack). I don't know how they had concluded that am good in algorithms but not in Data structures and Databases.
Remembering the coding question about finding a peak element gives me a sense of relief. It was nearly the same as one I had practiced on PracHub a few days prior. The interview process began with a recruiter screening my resume, followed by a technical phone interview where we discussed data structures and algorithms. The onsite included two additional rounds focusing on coding and behavioral questions. Overall, the experience was straightforward, and I felt well-prepared, ultimately leading to an offer that I happily accepted.
2 Technical Coding Screen, followed by onsite. Interesting problems and role related. Friendly recruiting coordinator. On site - in person, several rounds, includes presentation and question & answers. Highly role related and based on past experiences.
pretty chill. asked about evaluation metrics, calculate 2 metrics given a data log. has_collided, radial TTC. A few questions from my resume. How did you determine xyz, what are the factors, and what could be some other factors?
Bowls
Get actionable career advice tailored to you by joining more bowls.
Want the inside scoop on your own company?
Check out your Company Bowl for anonymous work chats.