Failing to be recruited…


Enrico Spinielli


August 29, 2014

This post title to be frank should have been “Impressions about the selection process of a big Internet company (and my failure to go to the next steps after initial engagement),” but that is obviously too long.

So I only kept the failure part with the aim to bring home some lessons from it ! :smirk:

Chronology, more or less

It all started with an email at the end of July 2014 from the company’s recruiter, let’s call her Alice.

My first reaction was: SPAM!!!! :scream:

Well, no. It was a genuine ping with too many realistic references about me (not that difficult given my CV is public on LinkedIn) and about her…but I could only reply when back home from my first slot of holidays: the family still at the beach, I am home alone, with tons of projects accumulated throughout the year (yes, year) since last summer…and this email!

Now, I am not at all looking for changing job: I know for sure my current employment conditions and benefits are extremely difficult to match. Even by big Internet companies.

But I am definitely piqued by the technical side of it! (Good job Alice!)

So we exchange few email with various links to job/site descriptions/videos from Alice and few replies from me with links (web presence/open source/tinkering around) and attachments to describe myself.

I am delighted when Alice tells me the position she is selecting for is about managing a team but it involves coding (“Good” I think, “I love that”…and say I do it too, even if just in my limited free time – 4hr per weekend; hey I have 4 kids! –). Once she mentioned people in the position spend 30 plus % of time coding, then later she mentioned few times 20%…anyway much much better than 0% I am currently stuck with at work.

Then we come to fix a video conf with the following declaration of intents:

Our chat will be more of an open discussion than a formal interview - we will discuss your current situation, the roles at XYZZY and if at that point there is a mutual interest, we can proceed to a technical chat.

To prepare for it I am handed a self evaluation form with scales from 0 (unfamiliar with the subject area) to 10 (Wrote the book in the subject area or similar expertise.) and subject areas from TCP/IP to People and Project Management going through C/Java/Go/SQL.

Good, I can fill a form and, as suggested, keep modest: for sure I know I know nothing but there are good search engines around and lots of people to ask and collaborate with ;-)

A week later we set for the video conf and start the business chat, things like whether I had to recruit or fire people, team size, sort of chit-chatting ;-)

And then the technical questions starts: and frankly it has been a disaster!

Even on questions (Unix file system and inode [4.14 of Advance Programming in the UNIX Environment {yes, I still have the 1992 edition!}]) I used to ask to people I was recruiting some 12 years ago!

Lessons learnt for when I am recruiting

  • Make sure the context of the interview is clear: subject, what is expected, timing, steps, process. I usually do this but we all tend to forget. This is a reminder for myself.

Lessons learnt (for when I want to be recruited ;-)

  • I should have clearly asked to separate the chat on current/future position from the technical chat as in the declaration of intents above. Maybe I assumed it would have been in 2 separate sessions but I was taken off balance by it happening in the same video conf. Never ASS U ME
  • I should have asked more about the technical interview, i.e. examples of questions
  • I should have asked more time to prepare if I felt I was too rusty on the subjects

Observations about the specific recruiting techniques

  • I was positively impressed by the fact I follow similar steps as in big Internet companies: we have a phone interview to assess the minimum level of technical competencies before we proceed with deeper hands-on assessments.
  • The post and place descriptions and the videos were good. We should prepare more material (web based and videos) to describe the consultants positions we look for. But here we are limited by our IT infrastructure, the framework contract we have for recruiting…
  • I liked the video conf (Skype and the likes): I have used it only when interviewing a Canadian (and even then he had the support from his university to use their video conference) but we should do it more…if only our IT infrastructure/policies would permit it (we have WebEx but I have never seen it used for recruiting…can we?)
  • I really disliked the narrowness of some of the questions I have been asked, things like the signature of certain Unix sys calls. This, I hope, was probably suited for the very specific needs of the job at hand, but in general IMHO they do not show anything about the capabilities of the person you are selecting. When I select people I prefer to watch/discuss about their journey to the destination/solution: the destination itself doesn’t tell me anything about how they do reason/think. (That is why I am usually happy with – and I also ask about – a book they would pick up to find some inspiration or the kind of web search they would use to start tackling a problem…)

Feedback from friends

Few friends working at the same big Internet company (both in USA and Europe) told me that they were not surprised of the outcome because, even if they think I could have made it, the whole selection process is skewed towards the negative: it only takes one no from the interview panel to get a negative feedback.

Well, I am sure I got more than one no!

No matching items