HiLearn Interview Guide

Our interview process follows a principle that we want to test candidate's skills not their knowledge!

Also we don't want to surprise you and we want to see how you do when fully prepared, not when nervous, since that's what your job will look like.

This guide describes the types of questions we ask during the interview and what we're looking for.

Interview format

First we will schedule a 15-30 minute introductory session to talk about HiLearn and understand what position you will fit into, and make sure you understadn what the interview will be like.

The main interview is just talking to and sharing your screen (or using a collaborative coding environment, e.g. coderpad) with one of the HiLearn engineers over Google Hangouts. The interview is confidential, takes 1.5-2 hours and includes a short break. Depending on the your position and seniority it could consist of the following sections:

  • General Programming
  • Modeling/Algorithmic Thinking
  • Short-answer discussion

Note: Our guide is inspired by TripleByte's interview Guide

General Programming

The general programming section involves writing a small console application.

We're looking for your ability to write clean, correct code, while productively making progress against our specification.

You can prepare by practicing building small, well-defined programs in a limited amount of time.

Modeling/Algorithmic Thinking

The modeling algorithmic section involves writing a small console application that models a certain mathematical/statistical phenomenon.

We're looking for your ability to understand the come up with a mathematical/statistical/Machine Learning model that describes the underlying problem, explain the decision and understand the tradeoff space of the model.

You can prepare by playing with simple models on read data sets, e.g. understand all the intricacies of a Linear Regression.

Short-answer discussion

This section usually is a short section that tries to test the breadth of your knowledge, and the ability to communicate with other engineers.

This section is difficult to prepare for specifically. A wide range of experience in building software is the best preparation. Practice speaking concisely about technical topics you already know about with your peers.

After the interview

After the interview we will email you about the next steps.