In-person technical interview was among the easier that I've experienced. Was not asked to perform any on-the-spot data structures or algorithm type problem. Mostly asked simple technical programming questions. For example, if doing an SQL query using a left join, what results are returned? Or what's the difference between an interface and a abstract class?
Do you work well with others?
serialization,spring,sorting,collection
Let struct A{ int a; char b;...}. How can you get the offset of a, b
Implement a priority queue using a stack.
Play a game where you roll a die: what's the expected value? What if you can roll twice and either keep first roll or have to keep second roll? What about three rolls or infinite rolls?
1) 12% of 47 2) If I pick 2 cards from a shuffled deck (with no jokers) what is the probability that they are both a queen? 3) i) If I toss 4 fair coins, I get a dollar for every head, what is the value of this game? ii) If I have the option to re-toss all 4 coins and must take the value of the second rounds result, what is the value of the game now? 4) How confident are you that you got 0,1,2,3 or all questions correct, giving percentages 5) If two teams play a best 4 of 7 series and have 50% chance of winning each round, what is the probability that they will play to the 7th round?
2 millions minus 1021.
Three questions were mental math: 12,000,000 - 101; 24*24; 12% of 54. Then there was a probability question: you have 4 fair coins. If you flip all of them, what is the probability of getting at least 2 heads?
They always warm you up with an "easy" question or two. In my second interview, the warm up wasn't so easy. They first asked, "If I roll two dice and tell you that at least 1 is a 6, what is the probability that both are 6s?"
Viewing 1381 - 1390 interview questions