I can't share specifics, but I had one classic brain teaser over the phone, and pure technical questions at the interview, some regarding algorithms for sorting real-time input. The hardest question was probably a systems problem, where I really had to ask a lot of questions.
Question difficulty level similar to the ones in Cracking the code interview.
1) Array has one unique number and all other numbers coming twice. Find the unique number. 2) A question for implementation of atoi 3) Clone a linked list in which every node has two pointers. One pointer points to next node and other pointer points to any random node. 4) Reverse a doubly linked list of length in chunks of size k. 5) Design a system wherein at any point of time you need to maintain 10 most typed words in current document in MS Word
1) How do you test a paper cup? Then I was presented with a networked client software with an error dialog with user logged in as a standard users without administrator privileges and I was asked it was a bug. 2) How do you test a parking meter? Then I was asked a coding question on how to write a nested loop function to manipulate two arrays set of numbers
Threading (Auto/Manual reset )
Current work style and how you can benefit RBS.
Core Java spl Collections Multi Threading Spring
What is deadlock? Thread management
The interviewer keeps on drilling and digging into each and every word you say or technical term you use
Asked me to write the part of code from my undergrad project.
Viewing 251 - 260 interview questions