I will not do a tech interview
medium.com
I will not do a tech interview
1–10 of 554 posts
Re: I will not do a tech interview
#2Very cool! I suffer from the same problem :(
I had an interview with a small startup I adore and had to code a simple python scrapper with the startup's CEO. I was so freaked out I totally bungled it up. Needless to say, my confidence went down the toilet.
I think I should accept that I don't do the traditional tech interview well. Next time, I find myself in such a situation, I'll suggest the short contract or coding exercise.
Re: I will not do a tech interview
#3I've always been great at interviews. I'm naturally outgoing, love to talk tech, and really try to show, rather than tell, why I'm a good fit for any particular team or project. That said, I hate traditional interviews. I hate begging for a job, and I hate having to kiss ass to some manager who has no technical competence. I have been fortunate in that I've landed three awesome jobs so far in my life. Two were short-term gigs but one of those gigs helped me network and was a huge factor in my landing my current position. All three of these jobs involved me saying "Hey, show me a problem and let me see if I can fix it for you." I don't believe in performing gymnastics for someone like a monkey, because I'm not looking for a spot in a zoo or a carnival. I like solving problems and I like helping other people solve there problems. So I agree 100% with this sentiment.
Re: I will not do a tech interview
#4Well, I need to interview candidates because I need to know if they are up for the job when systems breaks. If a table query fails because it needs a btree index due to range searches, I want the candidate to know how a btree index works and why it fixes the issue. Also If somebody cant tell me the difference between http udp and tcp, its a no hire for me.
So for me, I really want to interview somebody before he can work with me.
Re: I will not do a tech interview
#5well you better have something to show then such as a public github repo.
Re: I will not do a tech interview
#6Well, I need to interview candidates because I need to know if they are up for the job when systems breaks. If a table query fails because it needs a btree index due to range searches, I want the candidate to know how a btree index works and why it fixes the issue. Also If somebody cant tell me the difference between http udp and tcp, its a no hire for me. So for me, I really want to interview somebody before he can…
If only there were some way an employee could learn about btree's after taking a job...
Re: I will not do a tech interview
#7Well, I need to interview candidates because I need to know if they are up for the job when systems breaks. If a table query fails because it needs a btree index due to range searches, I want the candidate to know how a btree index works and why it fixes the issue. Also If somebody cant tell me the difference between http udp and tcp, its a no hire for me. So for me, I really want to interview somebody before he can…
If only there were some way an employee could learn about btree's after taking a job...
I don't want my employees to have to learn everything just-in-time. By that logic, the people you hire wouldn't need to know anything. In addition, they don't know what they don't know, so they may not even know that they need a btree index.
Re: I will not do a tech interview
#8I like oracle way of hiring. You got a degree from a decent college with decent GPA you are in. Very clear and straight forward. If you got in a decent college and graduated with a decent GPA - you are smart and somewhat hardworking, you should be doing well in your job.
Re: I will not do a tech interview
#9well you better have something to show then such as a public github repo.
If this approach became popular enough, it seems like this method could be easily gamed via outsourcing.
Re: I will not do a tech interview
#10Well, I need to interview candidates because I need to know if they are up for the job when systems breaks. If a table query fails because it needs a btree index due to range searches, I want the candidate to know how a btree index works and why it fixes the issue. Also If somebody cant tell me the difference between http udp and tcp, its a no hire for me. So for me, I really want to interview somebody before he can…
I suppose if you're a network engineer http/udp/tcp is necessary to know maybe off hand but not really, http isn't even in the same network layer so I'd find it strange to even ask about the 'difference'. UDP and TCP differences are more or less a well known question but even then I've had some ask the question expecting the most basic of differences and others with the minutiae.
btree index is also something that can be learned conceptually in about 10 minutes.
It is far more important for me to see that someone can explain a project that they've worked on in the past with enough details to demonstrate sufficient technical knowledge than a litmus test based on somewhat arbitrary facts. 'don't know what lsof is? Not hired, I don't want someone who can't use shell'