4 ms·
I'm going to reference coding tests specifically, because I'm not against them but I'm against them implemented poorly: - If I have an extensive github, and my
by debacle 8y ago
I'm going to reference coding tests specifically, because I'm not against them but I'm against them implemented poorly:
- If I have an extensive github, and my github is on my resume, and you don't have the time to look at it, I don't have time for your coding test.
- If your coding test asks thinly veiled lateral thinking questions, I will not be accepting a job with your company.
- If you spend more than 60 seconds of the interview asking me what I think of your coding test, I will not be accepting a job with your company.
- If I'm interviewing for a position where I'm going to be mostly developing CRUD apps, don't ask me to implement a bubblesort. Interview for the job you're actually hiring for.
- Ideally, let someone else design your coding test. There's plenty of companies that do these now, and they'll be better at it than you are.
- duxup 8y ago>If you spend more than 60 seconds of the interview asking me what I think of your coding test, I will not be accepting a job with your company. Is that a big enough deal to rule out a whole company?
- debacle 8y agoFrom what I have seen, companies that fetishize their coding tests have toxic social dynamics, and they always interview poorly in other ways (e.g. haughtily dismissing industry accepted best practices).
- rajacombinator 8y ago>thinly veiled lateral thinking questions What does this mean? (Genuinely curious.) >etc... more than 60 seconds...etc.. Why do you not like this? I’ve never been asked this but I think it’s a great question from both an interviewee and interviewer perspective, allows some great meta dialogue into understanding how each other think.
- debacle 8y agoLateral thinking questions are "gotcha" questions that masquerade as critical thinking questions. You can google reams of them. IMHO a programming test is a prophylactic and nothing more. It's fine if you ask me e.g. why I used an anonymous function in one spot, or why I didn't check for a certain exception, but it shouldn't be the focus of a technical interview.