Applying for IT jobs at big companies – the recruitment tasks
Marcin Polkowski
Translated from Polish. Originally published on morony.pl on 5 Oct 2016.
In less than two weeks I'll be defending my PhD, and my adventure as a student will come to an end. I was offered a position at the university as a researcher, but even so – partly out of curiosity – I decided to send my CV to a few IT companies in Poland and in the USA. Working in the USA is one of my goals for the future. For now, any talk of moving has been put off, so that we can raise the kids at least a little (and a second daughter is on the way).
My first job-hunting adventure was with the Polish branch of Google. I sent my CV, and about a week later a recruiter from London got in touch. The first conversation with the recruiter lasted about half an hour. A few days later I was offered a date for a technical interview. I was allowed to choose the programming language (C++, Java or Python – I chose Python). The interview took place over the phone (the caller ID showed a Swiss number) and lasted 40 minutes. I wrote my answers in a Google Doc prepared specially for the purpose, which became read-only the moment the call ended and disappeared shortly afterwards. The first task was a simple puzzle (no coding required):
You're playing a coin-tossing game with some kids (you have plenty of coins at hand). The coins aren't perfect: the probability of tails is 3/7 and of heads 4/7. Suggest the simplest way for the kids to get a "more or less" fair result (i.e. one that comes up with a probability of about 0.5).
After that I got the actual programming task, and I have to admit it took me a while to understand what the author was after. Looking back now, the question is obvious and the solution trivial. The task was:
Your friend is running an endless physics experiment in which a numerical value is measured. Write him a program in Python that will continuously compute a moving average of these measurements. Propose an interface between the experiment and your program.
About a week later I got a phone call telling me the recruitment process would not continue.
Tesla Motors
My second attempt was for a maps and navigation software engineer position at Tesla Motors. Here all the contact was by e-mail, and the time between messages was measured in weeks. After 3 e-mails I was asked to solve a programming task (the Tesla Coding Challenge). The task was made available for download. I had a week to get around to solving it, but the time from download to submission was not to exceed 4 hours (3 hours recommended). The solution had to be in C++. The task was:
Write a command-line program that solves a system of equations stored in a text file. The simplifications were that the system has exactly one solution, the left-hand side of each equation contains only a single variable, and the right-hand side of each equation can contain other variables and positive integers. The only operation allowed on the right-hand side is addition. The program should solve the system and print the variables with their values in alphabetical order.
This is how my program worked: 
Three weeks later I got an e-mail saying they had concluded they needed someone right away, and I would have to be "brought over".
HSBC
I also sent my CV for a risk assessment specialist position at a bank – it was one of the few positions where knowledge of MATLAB was expected. Unfortunately the job was in Kraków, but I was invited to an interview by video conference at their Warsaw office. I was asked for samples of my MATLAB code, and since I have nothing that isn't a trade secret of my current employer, I was asked to solve a task instead:
-
Ask the user for a phone number.
-
On a phone keypad, each digit has several corresponding
letters (1: ABC, 2:DEF, 3:GHI, …, 9:XYZ, 0:space).
<- I changed this myself to match the layout of an actual phone keypad
- Create a MATLAB script that converts the digits into the
corresponding letters. (Each number gives many variants of the resulting word.)
- From the generated word variants, pick 3 interesting ones – e.g. by
connecting to Google and choosing the 3 that return the most search
results (or by connecting to any other data source – a dictionary or
the like – and choosing words that actually exist).
I don't know whether they received my solution, because I attached a large dictionary file from sjp.pl, but they never got back to me.
I'm not publishing my solutions for now – have a go yourselves, and one day I'll show you mine. To be honest, the job I regretted most was the one at Google. In my current situation I wouldn't decide to move the whole family either to the USA or (even less so) to Kraków. Google was right here. Unfortunately it was my first recruitment process – I had no idea what to expect, and I stumbled on a trivial task. They encouraged me to try again in the future, and I'll probably be tempted. For now, I have a new job.