News for hackers. Stuff that matters.
Re:Guide to scaling engineering organizations by patio11 on Wednesday December 05, 2018 @10:12AM (#18608856)
(I work at Stripe and, while I don’t do engineering interviews, have strong views on the topic, which may or may not be equivalent to our views. I believe the following is substantially accurate regarding factual representations.)

We don’t do whiteboard interviews for coding. If we have a coding interview, candidates can do it on their choice of their machine or a loaner machine from us with one of a few environments installed.

Most interview loops have approximately two 45 minute coding interviews. The other interviews might focus on (depending on job/seniority/etc) design, architecture, product sense, industry knowledge, communication style, etc. (Each interview tests one cluster of skills against a rubric, as explained in the linked article.)

Re:Guide to scaling engineering organizations by ppeetteerr on Wednesday December 05, 2018 @10:16AM (#18608893)
Thanks for clarifying mate. It's nice to hear your company is changing the status quo.
Re:Guide to scaling engineering organizations by ummonk on Wednesday December 05, 2018 @11:57AM (#18610065)
This actually seems to be the norm at most startups. Coding exercises on laptop, and design and behavioral interviews.

I’ve mostly seen algorithm / data structure questions at megacorps, which are probably too big with too much inertia to quickly reform their processes.