"I'll spend hours brushing up on Scheme just to test you on something completely irrelevant to the role just because I like playing Resumé Gotcha". Yeah that's a thanks but no thanks from me. I wouldn't work for this guy in a thousand years.
It's a good investment for the company, if the interviewer can red flag a candidate who is blatantly lying on his resumé because the candidate would assume no one would know said technology, it would save a lot of money from cutting ties with an employee in a later stage. As an anecdote, I used to work for a company and would require candidates to know some Ruby, for one guy with several years experience in Python we…
Dear Programming Job Applicants (2010)
101–110 of 199 posts
Re: Dear Programming Job Applicants (2010)
#102"I'll spend hours brushing up on Scheme just to test you on something completely irrelevant to the role just because I like playing Resumé Gotcha". Yeah that's a thanks but no thanks from me. I wouldn't work for this guy in a thousand years.
It's a good investment for the company, if the interviewer can red flag a candidate who is blatantly lying on his resumé because the candidate would assume no one would know said technology, it would save a lot of money from cutting ties with an employee in a later stage. As an anecdote, I used to work for a company and would require candidates to know some Ruby, for one guy with several years experience in Python we…
Re: Dear Programming Job Applicants (2010)
#103yep. :) all lot of applicants should take a note at this.
Re: Dear Programming Job Applicants (2010)
#104Re: Dear Programming Job Applicants (2010)
#105> He reasoned through the problem, wrote the code, it ran perfectly the first time. I hired him. I get the overall sentiment, but come on, "I hired him" sounds like self-absorbed anecdata - so this post is about how to quickly appeal to some manager dude on the interwebs? A more useful metric would be, did this hire survive the first two years, and what do the people around him have to say about his performance. > It…
Bullshit. It'll go like this: Interviewer: here, a laptop with vi Applicant: I've never used vi Interviewer: just hit "i" to be dropped into insert mode, then just navigate with the arrows and use backspace like in any other editor. Ask me when you're ready to save and I'll teach you the magic incantation. Applicant: types away If you're not able to code in what's essentially just a test box then that's a useful thin…
Interviewer: here, a laptop with vi
Applicant: I've never used vi
Interviewer: ....
Re: Dear Programming Job Applicants (2010)
#106Re: Dear Programming Job Applicants (2010)
#107Earlier quoted context omitted.
This is a great reason to learn vi for basic editing tasks. It's everywhere. Even if you typically use a different editor/ide, vi is a common ground. Disclosure: I'm an emacs user
It’s kind of weird to NOT know basic vi/vim if you get to a certain point in your career. If you can’t at least open the software, go into insert mode, and save/quit, have you ever had to ssh into a remote server and edit a config file before? Only excuse I could think of is if you literally did everything in windows for your entire career.
Re: Dear Programming Job Applicants (2010)
#108Earlier quoted context omitted.
Bullshit. It'll go like this: Interviewer: here, a laptop with vi Applicant: I've never used vi Interviewer: just hit "i" to be dropped into insert mode, then just navigate with the arrows and use backspace like in any other editor. Ask me when you're ready to save and I'll teach you the magic incantation. Applicant: types away If you're not able to code in what's essentially just a test box then that's a useful thin…
Have you seen some of the other comments in this thread? Seems like there's a good chance it would be more like: Interviewer: here, a laptop with vi Applicant: I've never used vi Interviewer: ....
Interviewer: REPENT, SINNER!
Re: Dear Programming Job Applicants (2010)
#109Earlier quoted context omitted.
ad 1.) yes, being a contributor doesn't automatically make you good programmer. But having 7 years of coding practice in several companies kinda does, because why else would those companies have you for so long? Yet these programming interviews are required even for them. Probation period is much much more telling about a programmer than the 15 minute coding task.
> But having 7 years of coding practice in several companies kinda does, because why else would those companies have you for so long? Several jobs in 7 years might very well imply several companies gave that person a chance and then gave up. I often got questions about that years ago, and it was completely reasonable, at one point I'd worked in 4 different positions in 5 years. (There were good reasons for it and I h…
Nobody "gives a chance" for a year. Either the problems were discovered during the probation period, or they were not as bad. Definitely not so bad that you'd have any chance discovering it during the interview. Besides, this high fluctuation is quite normal in IT.
Re: Dear Programming Job Applicants (2010)
#110> If you say you’re a master of network protocols, guess what, I’ve maintained a TCP/IP stack, and unless you’re really a master I’m going to bury you. The goal of interviewing is never under any circumstances to "bury" someone with obscure, difficult questions. Even as the OP is obviously impressed with his own skill set ("I've maintained a TCP/IP stack") I'm sure someone coming from a different vantage point could…
Exactly, it sounds like this guy sees interviews as a way to feed his ego and make himself feel smarter than the candidate. He would be a massive red flag to me as an indicator I don't want to work there.