The interview consisted of the following steps:

• Phone screen with HR: typical HR questions about your previous positions and plans for the future.
• Call with the director of engineering: short introduction, describe what you achieved so far, mainly focused on cultural fit.
• Call with a tech employee: technical discussion, describe some previous challenges, solve an algorithm problem.
• Call with a tech employee: technical discussion, focus on distributed systems and design, handling a large amount of data, CAP theorem.
• Call with the manager: describe something you contributed to at all your previous jobs from the very beginning of your career.
• Coding assignment: soft deadline of 4 hours (you are expected to finish the entire assignment), REST API. It was required to jump on a call each time after finishing a requirement from the assignment.

Display the next smaller element in an array of integer numbers. The next smaller element for an element x is the first smaller element on the right side of x in the array. The next smaller element for elements for which no smaller element exists should be considered -1.

Consider that you have an API called from the UI to display some data using pagination. How would you change the API call if for a non-UI client, you need to retrieve all data at once without pagination (petabytes of data)?

How would you design a video sharing application (key terms: replication, master-slave, CAP theorem, consistency, bandwidth, availability)?

Implement a REST API for storing file metadata and file dependencies. It is mandatory to use Redis as the DB. You had to implement CRUD calls for file metadata and file dependencies, and then 3 separate calls that would query the data (one of them being a BFS/DFS variation). File dependencies looked like a directed graph.