|
|
|
|
|
by AnimalMuppet
1593 days ago
|
|
My current position. First there was a phone interview of about 45 minutes, IIRC. Then an in-person interview that lasted 2 hours. The first 30 minutes was general questions. Background, work history, that kind of stuff. A bit of "get to know you" kind of stuff stuff - hobbies or whatever. The next 30 minutes was, here's this half page of code. It's one function. It's not especially tricky. The function is named "foo" or something like that. What does it do? What inputs does it expect? What should it be named? What can go wrong in the function? What will happen if it does? The next 30 minutes was a little coding problem. It wasn't leetcode - you didn't have to "know the trick" to be able to get it. You could use any language you wanted. (I used perl because it did a bunch of the details for me.) If you had a bug, they'd ask questions until you realized it. The last 30 minutes was a design question. How would you design your software for this situation? It was a pretty open-ended situation, so no matter what you did, they could throw some additional details at you and see how you evolved your design in response. At the end of it, they knew: Can we work with this person? Can they read code? Can they write code? Can they design code? |
|