I'm going through the interview process this week at two different companies. One of the companies I found through an ad on Stack Overflow whereby they publish two programming "exercises/puzzles" with the opportunity to earn $100 for a correct answer to each puzzle ($200 total for two correct answers). While I spent more than eight hours on both puzzles, I found them to be thought provoking and I learned stuff in the…
The flip side of this is that not everyone has the luxury of that much free time to focus on puzzle-type exercises just to get a foot in the door. This process seems to select for single people with a good amount of free time, which, depending on who you ask, is possibly what they want (if e.g. frequently greater than 40hr work weeks are expected). Edit: thinking more about this, it's good to see that it's a paid puz…
On asking job candidates to code
401–410 of 524 posts
Re: On asking job candidates to code
#402I just want to create a well documented simple resful API for applicants to use. If an applicant wants to apply for a job they have to write code in the language of their choice to apply using the API. Upon successful application, request their SSH public key and supply a git repository they can check their code into. A hook script will email me upon successful commit. A moderately experienced dev will not spend much…
This sounds like a great idea! One caveat being that the it probably caters more to web/mobile devs. Eg. you probably wouldn't use this challenge for a database engineer, or machine learning role. You could, but it wouldn't tell you much about their skills in the domains you're interested in. Still definitely worth trying for roles where it makes sense. I might try this.
It does make me wonder how hard it would be to come up with basic challenges for different roles to simply apply to the job using their skills. I guess for some rolls harder than others. :-)
The goal wouldn't be a hard challenge, just one that shows basic competency and problem solving ability within their field.
Still this would take time and effort to create. That said, the last time I hired someone I probably spent 100 hours reading resumes, filtering candidates, and interviewing people.
Re: On asking job candidates to code
#403Earlier quoted context omitted.
Wow, they are leaving a lot of great EE/CS schools out. No worries, the competition will hire them ;)
CalTech didn't make it, so I guess Knuth would be out of the running ;-)
Re: On asking job candidates to code
#404Earlier quoted context omitted.
"The one thing that isn't immediately clear from your GitHub is if YOU wrote the code and HOW you wrote the code." Spend a few minutes looking at the commit history and all shall be revealed...
History shows when you forked from somewhere, not copypasta.
Re: On asking job candidates to code
#405I just want to create a well documented simple resful API for applicants to use. If an applicant wants to apply for a job they have to write code in the language of their choice to apply using the API. Upon successful application, request their SSH public key and supply a git repository they can check their code into. A hook script will email me upon successful commit. A moderately experienced dev will not spend much…
Re: On asking job candidates to code
#406Earlier quoted context omitted.
I've noticed that your github profile doesn't even get looked at until you jump through all the standard phonescreen/homework hoops. Even after than many interviewers look at your resume like 10 minutes before the interview there is no chance that they would read through your code on github. github as your resume is overrated. I am curious to know if people hire or get hired purely based on their github profile witho…
I'm a professional software developer. I don't use GitHub, or StackOverflow. At all. I don't think that reflects on my skills.
Re: On asking job candidates to code
#407Re: On asking job candidates to code
#408A lot of people here seem to suggest it is unreasonable to ask someone to do some coding in an interview given that you've shown a series of projects and provided references. Unfortunately I've been through a variety of interviews where I feel the conditions which I was asked to code were unreasonable (whiteboard, overly complex problems while under pressure, using a language I was not comfortable with or just academ…
Not trying to be a smart ass, but being average is not only the developers fault, it could also be the company's.
Re: On asking job candidates to code
#409I try to ask questions that aren’t completely ridiculous, but definite tests of knowledge. And in my mind I judge correctness not so much on remembering obscure syntax but on how they approached the problem, and how much time it seemed to take them to start doing something. I always ask about things like how they approach debugging, testing, etc. because these are important too and they tell you a lot about how likely the person is to be able to handle any problem you come up with.
Re: On asking job candidates to code
#410Earlier quoted context omitted.
I have tried hiring. Many times. As recently as yesterday. Using a combination of (semi-)rigorous personality profiling (time constrained), and mapping the abstract problem domain of their prior work to the problems I actually have for them to work on, it's been possible to align new people with the work such that they're intrinsically motivated, and make sure all the bases are covered for the necessary roles (hacker…
Can you elaborate more on your middle paragraph? It sounds very interesting.
Like for instance, if you were to meet me, you would probably immediately peg me as high on extroversion. While understandable given the outward traits I project, you'd have needed to really thoroughly created a controlled environment during an interview (requiring a series panel, a day-long engagement, and an intentional highly-social event in the middle) to figure out that I'm actually introverted, but have just learned how to benefit myself by projecting extroverted traits.
Now the richness of any assessment is bound by time, planning, training, and practice. If you want to get really good at it, you learn to do it in realtime by assessing people you know well, assessing yourself, then moving on to acquaintances, and eventually onto strangers. In each step you need to be aware of where your assessments are drifting from the model. Like if you assess yourself or someone else as high on agreeableness because you find that you're very typically conciliatory or trend toward diplomacy and keeping the peace amongst your peers, but you also are prone to "blow-ups" where you drop the hammer on people in rare, but consistent, circumstances (when you've "been pushed too far"), then you're probably not as high on agreeableness as you think, and are probably higher on neuroticism than you think you are.
Given enough inputs and hypotheses you can get pretty good at this. Good enough to provide useful points for making decisions given otherwise limited information. More importantly you can get good at how you setup your environments and your interactions to get higher quality signals from your limited information. For instance, say I wanted to assess someone's "Openness" because I wanted to bring them onto a team where their primary responsibility will be in driving phases of invention. The simplest pass would be to just ask them about personal activities and look for signals of risk-taking. However, one needs to control for the difference between risk-taking due to openness to experience and risk-taking due to self-destructive traits. The former would be awesome for the job role and the latter will bring down the whole ship. To control for that you'd want to put additional emphasis on assessing neuroticism and conscientiousness. Doing that can be as simple as leaving a lot of awkward pauses in the conversation and see how they deal with it. Does it make them uncomfortable? Do they feel compelled to fill the air with something? What do they fill it with? Relatable stories, trivia about their work history, etc. When they talk about anything, not just work-related things (sometimes specifically not work-related things), what level of detail do they provide? Is it consistent? Is it always TMI, always 30k ft view, or can they move fluidly from one to the other?
Things like that. Different kinds of job roles require a different kind of personality profile to be successful, and more important than that, the composite of personality profiles filling those job roles is a requirement for a healthy team where each person is competitive with themselves, but cooperative with their peers, and has the right mix of people to own each phase of the development and business process.