3 ms·
Talking about patterns, technologies, how I would architect/design a specific solution or how I would approach a technical problem is not a technical interview,
by koevet 11y ago
Talking about patterns, technologies, how I would architect/design a specific solution or how I would approach a technical problem is not a technical interview, IMO. And I would be glad to answer these questions, which are fair and interesting.
What I'm talking about are the quizzes and the puzzles, the invert-a-binary-tree riddles or, as it happened to a friend recently, to write a full blown application with tests and stuff and don't even bother explaining why the application was rejected.
It doesn't make sense anyway. In 25 years, the sheer amount of cowboys I have seen literally bringing down projects out of incompetence and lack of humility is staggering. And these guys were hired out of technical riddles.
- estefan 11y agoOh right. In that case fair enough. I'd far rather have a walkthrough of some of your github code to see your style and reasoning. As a Good Person, you should get taken on by clients who don't have this requirement while others who do lose you. I've only done one of those tests in the last couple of years because I wanted the (not insignificant) pay rise and it gave me an opportunity to learn something. It's all about negotiating power (they had more). But yeah, in general I don't have to bother with them. OTOH I don't see them as entirely negative because hopefully it should mean you'll be working with competent people (provided the tasks are small demonstrations and not full applications which smacks of incompetence).