4 ms·
I consider myself to be one of these product oriented developers (not sure about being 10x though). Interestingly, while interviewing this has always been my b
by haspok 4y ago
I consider myself to be one of these product oriented developers (not sure about being 10x though).
Interestingly, while interviewing this has always been my bane, as the typical interviewing process goes along the tech stack and tech-related trivia (probably because it is easier to assess), and almost never towards the product side of things.
And with the tech stack questions those are always in favour who are interested in the latest version of framework X, as opposed to real world problem solving. And don't even mention leetcode :)
- WorldMaker 4y agoI've felt this a lot myself. So many interviewers hate being asked "why?" "Why this problem?" "What is the reasoning behind this problem?" I've learned some fascinating things about company attitudes in asking these "why?" questions. It turns out that Not-Invented-Here syndrome really can be deep enough in corporate culture you can hear it in interview questions if you ask follow up questions. ("That's just what we do, we don't trust the library solution at our scale." Cool, rewriting platform libraries orthogonal to your business delivers real value to your consumers I'm sure.~) So I'm probably still going to ask a lot of "why" questions in interviews, because it yields useful information. But I'm painfully aware from rejections how much interviewers seem to hate it.