| ▲ | ventana 43 minutes ago | |
Just don't ask brain teasers when you conduct an interview; I believe they give no valid signal at all, and I also believe Microsoft does not ask them anymore. The coding questions that require an "aha!" moment are very similar to brain teasers, and should also be avoided. When I conducted interviews for FAANG, I asked somewhat simpler coding questions, something around DFS and/or topological sorting (without calling it by name, of course), because those are thing which you might actually need to implement at work: people sometimes traverse JSONs, and people sometimes resolve dependencies. No one has ever told me "oh, I know this problem, it's DFS", because surely I know they know it. Just show me that you can write the code. | ||
| ▲ | viccis 30 minutes ago | parent [-] | |
>The coding questions that require an "aha!" moment are very similar to brain teasers, and should also be avoided. The problem with these is that their solutions always seem trivial when you are shown them (or spend time solving yourself) and then mull over them for a while. | ||