3 ms·
Step (1) Know what you need. I wish more companies were honest about the exact type experience they actually need. [A]: "I need someone to fix bugs. We're tal
by columbo 13y ago
Step (1) Know what you need.
I wish more companies were honest about the exact type experience they actually need.
[A]: "I need someone to fix bugs. We're talking head-scratching-mind-numbing bizarre behavior bugs. Most of the time you'll be starting out in the UI tracing connections back to the API then walking through the API into the core system until you can find out what actually happened."
[B]: "I need someone to make the application faster. It's an archaic enterprise system that is responsible for performing very important calculations. It's hundreds of thousands of lines of banking logic wrapped behind all sorts of enterprisey buzzwords. The first task you will have is to sort out why we are getting intermittent heap errors. You'll need to setup everything yourself as we have no dev environment."
Both these roles might be in the same technology space, and both will probably have identical resumes (5 years of experience with <foo>) but the types of people you will want to hire and the questions you will want to ask them are going to be vastly different.
- eshvk 13y agoI have thought about this problem for a while both as an interviewee and interviewer. Especially because this problem is magnified when you want to hire a data scientist; your ideal data scientist can be anyone from a SQL monkey to a statistician to a programmer who likes the title data scientist. The problem however is fear. Most small companies have short term goals that are in flux. So managers want this caricature of a human being: the ubermensch who does everything. The "best" of the "best". So the interview process is fucked up.