Skip to main content

Better Interviewing Tactics

Job interviews start with the Posting.

Some years ago when I was starting to get into erlang (for the second time; the first time was a failure) I recall reading an article that suggested [prarphrazed] It is better to post a job for an erlang programmer instead of a java as you are (a) going to get fewer respondents (b) of higher quality and aptitude. I cannot find fault with this approach except that posting for an erlang position and then using C#, java or perl and you might actually keep the candidate if you manage to win the day.

In the past I had interview questions which I would say have their origin in the Silicon Valley way of thinking. Of which the author of this article [Phone Interviews] would have you believe is bad; and today I agree as my initial opinion has changed. In the end I realized that I have a good intuition when it came to interviewing. I think I ask questions that cover various median knowledge and aptitude; and some that are meant to gauge the interpersonal stuff... it is intuition after all.

The Phone Interview also links to two other interview articles that I think I might find interesting

The GitHub Hiring Experience (link)

The post makes an interesting point that other techniques might not. First Contact seems to be "brick and mortar" meaning that it's not your typical internal or 3rd party recruiters that busy "dressing flesh" in order to get candidates through the pipeline. It's an easy way to pre-screen potential candidates.

As for the interview process. That's a bit much too. In this case the candidate indicated that s/he met with 10-12 interviewers. If this is a typical 10a-4p interview day with an hour for lunch that's 10 people over 6 hours if everyone manages to show up on time and is prepared. That's going to work out to an average of 2 interviewers per meeting and a group or just the manager at lunch.

One thing that was not mentioned was "who" were the interviewers? Were they managers, architects, peers in the same or different departments, were any of the interviewers interns, or just learning to give interviews. I'm not sure that any of this works. At some point you have to savvy enough to:

  • stop doing the "ice cream man" dance
  • start selling the company, manager and job 
And that is simply impossible in an hour when there are so many departments, teams, and personalities involved.


Project Based Interviews Instead of GitHub (link)
"No one should ever require a Github profile in favor of a resume"
Resig makes a number of assumptions about "custom projects" for the specific interview. This is something I did when I presented candidates with "the impossible quiz". I suppose if you're interviewing at Google and you want to show your chops then doing a special project might have some value. It's also possible that recording a live pair programming session might have the same outcome. But these are exceptional cases and not the norm and it's not going to demonstrate the candidates interest in you market or stack. There are simply way too many variables for a project to be valuable.

However.

I have been known to provide a few programming assignments, both in advance or at the time of the interview. And from that POV I've asked decision questions. "why a hash instead of a list" etc... That usually leads to a better outcome.

Resig goes on to challenge the pressure of an individual interview. (I blew a few of those with the like of Google and Amazon). Frankly, unless you are simply desperate for a job (been there too) nervousness or lack of confidence can be an indicator for that candidate's abilities. And sadly with a little too much confidence the candidate might not have enough practical experience to know the difference. But a nice balance is good.

Comments

Popular posts from this blog

Entry level cost for CoreOS+Tectonic

CoreOS and Tectonic start their pricing at 10 servers. Managed CoreOS starts at $1000 per month for those first 10 servers and Tectonic is $5000 for the same 10 servers. Annualized that is $85K or at least one employee depending on your market. As a single employee company I'd rather hire the employee. Specially since I only have 3 servers.

The pricing is biased toward the largest servers with the largest capacities; my dual core 32GB i5 IntelNuc can never be mistaken for a 96-CPU dual or quad core DELL

If CoreOS does not figure out a different barrier of entry they are going to follow the Borland path to obscurity.

UPDATE 2017-10-30: With gratitude the CoreOS team has provided updated information on their pricing, however, I stand by my conclusion that the effective cost is lower when you deploy monster machines. The cost per node of my 1 CPU Intel NUC is the same as a 96 CPU server when you get beyond 10 nodes. I'll also reiterate that while my pricing notes are not currently…

eGalax touch on default Ubuntu 14.04.2 LTS

I have not had success with the touch drivers as yet.  The touch works and evtest also seems to report events, however, I have noticed that the button click is not working and no matter what I do xinput refuses to configure the buttons correctly.  When I downgraded to ubuntu 10.04 LTS everything sort of worked... there must have been something in the kermel as 10.04 was in the 2.6 kernel and 4.04 is in the 3.x branch.

One thing ... all of the documentation pointed to the wrong website or one in Taiwanese. I was finally able to locate the drivers again: http://www.eeti.com.tw/drivers_Linux.html (it would have been nice if they provided the install instructions in text rather than PDF)
Please open the document "EETI_eGTouch_Programming_Guide" under the Guide directory, and follow the Guidline to install driver.
download the appropriate versionunzip the fileread the programming manual And from that I'm distilling to the following: execute the setup.sh answer all of the questio…

Prometheus vs Bosun

In conclusion... while Bosun(B) is still not the ideal monitoring system neither is Prometheus(P).

TL;DR;

I am running Bosun in a Docker container hosted on CoreOS. Fleet service/unit files keep it running. However in once case I have experienced at least one severe crash as a result of a disk full condition. That it is implemented as part golang, java and python is an annoyance. The MIT license is about the only good thing.

I am trying to integrate Prometheus into my pipeline but losing steam fast. The Prometheus design seems to desire that you integrate your own cache inside your application and then allow the server to scrape the data, however, if the interval between scrapes is shorter than the longest transient session of your application then you need a gateway. A place to shuttle your data that will be a little more persistent.

(1) storing the data in my application might get me started more quickly
(2) getting the server to pull the data might be more secure
(3) using a push g…