The hiring process consists of one to two phone calls (one-on-one conversations with a technical leader hiring for their team) and a one-day on-site interview. The on-site interview is similar to Amazon interviews and also features the infamous "bar raiser" method.

The first phone call was a standard phone screen. The goal was to introduce the company and its hiring process, then talk about my experience and go over my skills. I was asked many technical questions; I was also given three design-related problems. Each of my answers was followed by another question (usually another constraint that hardened the problem).

As I was applying for a Back-End developer role, I was given problems about scalability, high throughput, and data storage optimization.

Unfortunately, I did not receive any feedback for this first phone interview. This should be a warning for anyone applying: it seems they have too many applications to afford such behavior. The interview was a waste of time for me.

You need to design a Twitter-like application.

Which design patterns would you use to make the system extremely scalable?

What caching strategy would you use?

What type of data storage?

The problem may not have been explained correctly, as I had to ask many clarifying questions.

You are designing a web service. This web service is linked to the user's browser. The content of the web service changes (on average) n...

You have two servers that are not physically connected (they do not have the same storage). You need to transfer a large file (about 50 GB) from one server to the other once a week. Currently, the file is transferred via FTP...