1. Write a sort of FizzBuzz 2. Use rest api to get a 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. The same file but parse it continuously (the file can be rolled-over, etc.) Side questions: advantages and disadvantages of a recursion, rewrite a recursion in a non-recursive way, etc. (depends on what do you write)
You will be asked to role play a scenario where the number of registrations for a service has dropped to 0 for the past 6 or so hours, setting off an alert. You will have to go through an incident response and elevation. You will be asked to write simple reports that are suitable for giving high-level status to a manager.
Coding test: Parse a (syslog) file to get various fields from the logs and message counts. Associate counts with the processes that logged them.
Describe how curl works. What happens when you call the command? Describe the process of loading libraries, parsing arguments, DNS resolution, etc.
Scale a ride-hailing application so that it handles ~10,000 requests/minute. This was a 1.5-hour-long discussion with follow-ups, including Consistent Hashing. They also challenged multiple of my design claims which I had to think about on the spot.
Second round was scheduled only for Linux Memory management. Entire Memory management questions were asked. How it works, why is it required, Virtual memory, swap memory, swappiness and all.
System design was okay. They gave situations and asked how to design system in that scenario. We were allowed to ask questions to check if we were in tbe right track.
The last one was Troubleshooting There was an Apache server and we had tk debug jt. It had 500 and 400 errors. I wasn't able to solve any in this round.
Related with Linux commands, Apache server troubleshooting, finding bugs of given code and system design for you tube.
Its repeated multiple times in this forum.
Viewing 2981 - 2990 interview questions