|
|
|
|
|
|
by oglop
905 days ago
|
|
|
> As soon as you hit strong cultural disagreement (e.g. "new technologies" is a minefield) I am not sure what you mean by this. This is a question I ask and I’m concerned there’s something I’m missing here. Could you elaborate? > I intentionally skip the CVs as much as possible), That seems very odd. How do you comb through and make an initial choice of who to interview then? Also, seems unfair to not look at the work they’ve done over all the years. Personally, I’m a GitHub person. Show me what you’ve written and how active you are. |
|
|
> I am not sure what you mean by this. This is a question I ask and I’m concerned there’s something I’m missing here. Could you elaborate?
Easy :). Take me: I hate Go and think Java is the best programming language there is. (My daily drivers today are C++ and Python.) NodeJs should've never been invented. I'm pretty opinionated when it comes to this. I'd still accept the position where I have to code in Go (been there and it was OK for both sides), but I wouldn't keep my mouth shut during the interview -- I wonder how that would go with 80% interviewers.
> How do you comb through and make an initial choice of who to interview then?
Sorry, I didn't put it explicit enough. I don't do the initial selection or leveling. This is done for me. The CVs are useful for this. But if you can avoid reading the CV (e.g. assessing only the raw skills), then you should.