in communication, researching, meetings, brainstorming, trade off discussions.
I don’t disagree with your first treatment about Google’s treatment of employees.
Satyajit Malugu
1

Don’t you brainstorm your ideas, communicate them, and discuss tradeoffs *before* writing any code in your interview? I hope you do; if not, you probably won’t pass, which is why they always call for ‘thinking out aloud’.

Researching is tricky to evaluate in a 45 min interview though.

Look, none of the existing interviewing systems is perfect (you can probably find a bunch of Hacker News/Reddit posts whining about this). Tons of great engineers (e.g., homebrew author) fail in Google/FaceBook interviews. But my point is the system exists for a reason: it’s probably the most efficient and fairest one you can come up with.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.