First, there was a short screen call with the recruiter.

The second phase was a 1-hour coding interview. This involved a number of questions requiring you to write some code. The questions increased in complexity, and I was also asked some solution-specific questions. By the end of the interview, I had reached the 6th question. In general, I had a good experience with it. They use CoderPad as the platform. The only drawback I would mention is the lack of preparation materials compared to other companies (like Facebook or Google). After that, the interviewer contacted me the next day and scheduled the next interview.

The third interview was systems-design-like. There were three questions. As with the previous interview, there was not a lot of preparation material. I was given a link to Google's SRE book, but I can't say that it was very useful. Although, it did help me to understand what kind of answers they were expecting from me. Another point is that they do not use any tool to write down the questions. It was a pure phone call, so I spent some time trying to figure out the details and what the questions were about. In general, that was also a positive experience. The only thing I did not like is that some questions were too vague, and you had a short time to answer them. After the interview, there was no follow-up from the recruiter.

1. Write a sort of FizzBuzz.

2. Use a REST API to get JSON and traverse it.

3. Parse a log file and process the data.

4. Parse the same file in a more advanced way (regex, grouping, etc.).

5. Parse the same file continuously (the file can be rolled over, etc.).

Side questions:

• Advantages and disadvantages of recursion.
• Rewrite a recursion in a non-recursive way (depends on what you write).

1. Explain in detail what happens when you type curl https://....

2. Copy a huge set of files over 10,000 nodes, keep the files updated, and check consistency.

3. How to organize monitoring in an n-node cluster running a web application.