|
|
|
|
|
by beckler
1472 days ago
|
|
This is pretty similar to what we did. We didn’t offer a refactor problem though. We just had a basic problem to create a calculator from a string, only supporting addition and subtraction. Then a high-level question on how would you architect and scale a simple API/service. We didn’t reject people if they weren’t able to complete the algorithm, because it’s a lot of unrealistic pressure. For both questions, we mostly just want to see how they think things through, how they identify pain points, how open they are to feedback, and discuss their approach. Even though we would tell people this, I think they still put a lot of pressure on themselves because of the status quo of leetcode interviews. |
|