
Media.net Site Reliability Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 15 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Media.net.
Site Reliability Engineer
So the process was pretty standard. First round was a mix of aptitude, OS/CN/DBMS questions, and 3 easy coding questions. Second round was a machine coding round focusing on socket programming. Round 3 was a face-to-face interview covering OS, CN, and DBMS concepts. Round 4 was a face-to-face system design interview. Finally, Round 5 was with HR.
- Tell me about CA fundamentals.
- Could you design an IaaS platform for internal use?
Site Reliability Engineer
The interview process had 5 rounds. Round 1 was an online assessment on InterviewBit, lasting 45 minutes, with 3 sections: General Aptitude, CS fundamentals (OS, DBMS, Networking, Linux Commands), and 2 easy DSA coding questions plus 1 shell/bash script question. Round 2 was a 3-hour offline Machine Coding round with 2 questions and 5 subquestions related to socket programming, heartbeats, server commands, and threading. Round 3 was a Face To Face interview focusing on my Resume and Projects, covering topics like Key Exchange Algorithms, HTTP verbs, HTTP vs HTTPS, Multithreading vs Multiprogramming, and SQL vs NoSQL use cases, with deep dives into each. Round 4 was a System Design round, and Round 5 was a Managerial Round. I didn't get selected after Round 3.
- Can you write a Python code for both server and client to create a 2-terminal echo server using UDP protocol?
- How would you implement sending a heartbeat from the client, and have the server send manually entered and queued commands to the client, utilizing the concept of threading?
- How can you execute commands on the client side, ensuring the process stops when the client encounters an exit code of 0?
Site Reliability Engineer
SRE Interview process : Round 1 – Work experience details, Systems (Unix/Linux) fundamentals, OS & Networking basics, DevOps fundamentals/DevOps tools, Troubleshooting & Monitoring, Automation Scripting (Python/bash), Generic Programming (any language)/Problem-solving. Round 2 – In the depth of all the above aspects plus Web Architecture, File Systems, DNS, Caching, AutoScaling, Load Balancing etc. Round 3 (Machine Round] and we would like to judge how you would perform in a real-world scenario. Round 4 (System Design) Round 5 (Final) - Discussion with the DevOps leadership team
- Can you explain the difference between containerization and virtualization, including when and why to use each?
- Could you share an experience of handling a recent incident or outage?
- How would you troubleshoot an application or service experiencing high latency?
Media.net Site Reliability Engineer Interview Questions
Quoted word for word from Media.net interview reports.
“What is the difference between HTTP and HTTPS?”
Read reports →“What occurs when the command 'ls' is executed?”
Read reports →“What is a system call?”
Read reports →“What is the difference between a forward and a reverse proxy?”
Read reports →“How does a server obtain an IP address?”
Read report →“If files in Linux have been deleted but the disk space still shows full (100%), how would you debug this situation and why does it happen?”
Read report →“What are HTTP Verbs?”
Read report →“Could you explain what inodes are?”
Read report →“What are Key Exchange Algorithms?”
Read report →Formats, difficulty and experience
Across all 15 Media.net interview reports.