I'm starting to wonder if design interviews are not only useless, but actually contributors to poor design. I'm still thinking through this, by my reasoning for this is:
-
Show this thread
-
There've been times where I've reduced the implementation effort of something by 100x to 1000x, producing in 1 day something that replaced ~1 year of work (proposed or actual). This has never been with "design interview" reasoning, it's always been domain knowledge.
2 replies 3 retweets 61 likesShow this thread -
This doesn't mean you have to be a deep domain expert, in the two most extreme cases, it was something I came to pretty soon after starting work in a new (to me) field. But it was still after much more time than you get in a design interview.
2 replies 1 retweet 13 likesShow this thread -
Interviewers sometimes try to get around this by saying you should questions assumptions, etc., but I don't think this would have worked in either case. In one case, the solution resolved something that had been an open problem in IR for decades, that's not interview material.
2 replies 0 retweets 8 likesShow this thread -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.