I applied online. The process took 5 days. I interviewed at FutureLearn in Oct 2021
Interview
Had an initial call with two Engineering Managers / Tech Leads.
Questions asked were more about situations I had been in rather than any real technical talk - like "describe a time where you were teaching someone who was struggling to learn something" and "tell us about something you recently learned".
From experience, any company that asks those sorts of useless questions in an interview is one to be avoided.
The rejection email simply mentioned I wasn't a good fit for the role. For a company who's business is in the Education space, the least they could do is provide some honest interview feedback so that people can hope to learn something from them rather than maintain an air of mystery around what they are even looking for in a candidate.
Bullet dodged, most likely.
Interview questions [1]
Question 1
describe a time where you were teaching someone who was struggling to learn something and tell us about something you recently learned.
I applied through a recruiter. The process took 1 week. I interviewed at FutureLearn in Aug 2021
Interview
My experience of the interview process was excellent, as a caveat the position was found for me via a recruiter.
The interview process and what was expected was well explained upfront. The interviewers were very welcoming and the questions asked were probing and interesting to discuss.
Overall it felt like a genuine 2-way process.
Interview questions [1]
Question 1
Initial discussion with VP of Engineering and Engineering Manager.
More detailed technology discussion with senior members of the team.
Pairing exercise with another engineer on the team the position was in.
I applied online. The process took 1 week. I interviewed at FutureLearn (London, England) in Feb 2020
Interview
The process was a 45-minute video call with two of the engineering managers, followed by a half-day in their offices. The in-person part comprised of a technical interview with one of the lead developers and a software architect, some pairing with one of the engineers, and an informal chat with some of the wider team (someone from marketing, and someone from accounts if I remember correctly).
It was all very friendly and not at all like some of the high-pressure technical interviews I've done with other companies.
Interview questions [1]
Question 1
Specific Ruby on Rails knowledge during the pair programming session, plus software architecture & design topics during the technical interview.
