Candidates describe a Media.Net software engineer interview built around DSA, CS fundamentals such as networking, OS and OOP, and project discussion. Reports typically describe three or more rounds, with some design-focused and some algorithm-heavy.
$59K
Avg. Base Comp
$75K
Avg. Total Comp
3-5 rounds
Typical Rounds
Not reported
Process Length
Candidates describe the Media.Net software engineer interview as a DSA-heavy process with a wide layer of CS fundamentals. Several reports open with an online test or screening round that mixes coding problems with multiple-choice questions on topics like OOP, DBMS, Linux and networking. One candidate also described a separate socket programming round where a working TCP/UDP server had to be built in Python.
Later technical rounds vary by candidate. One person who did not receive an offer faced a hard problem combining binary search with digit DP and, in a later round, a coordinate geometry problem involving DSU, and described both as stumbling points. Others report more approachable problems, such as jump game variants, two-sum variants, linked list questions, and graph questions like lowest common ancestor. At least one candidate says interviewers pushed for better time and space complexity even on simpler problems.
One candidate interviewing at the SDE 2 level reported a different emphasis: a medium DSA round, then a low-level design round on a chess game's class structure, then a hiring manager conversation that moved into high-level design. If your level is above entry, expect that design may matter at least as much as algorithms.
Project depth also comes up. Candidates report detailed questions on technology choices and implementation logic, so be ready to defend your own work. Operating systems, networking and caching were also mentioned in technical rounds, and one candidate cited inodes and system calls.
Outcomes in this set are mixed, with offers, rejections and one withdrawal. Prepare mixed-technique DSA and fundamentals, not just standard LeetCode mediums.
Synthesized from 7 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Media.Net process.
I went through three rounds, all conducted online. The first round focused on CS fundamentals—computer networks and object-oriented programming—followed by a DSA problem that tested the sparse table concept, which was moderate in difficulty. I did okay on that, but then the second round ramped up significantly. They asked more networking and OS questions, then threw a very hard DSA problem at me that combined binary search with digit dynamic programming. I struggled with the implementation and time complexity. The third round was a mix of technical and managerial elements. They quizzed me on OOP again and gave me a mathematical coordinate geometry problem involving disjoint set union (DSU). I couldn't come up with a working solution under pressure, and that pretty much sealed my fate. Throughout the process, I realized I wasn't strong enough on advanced algorithmic techniques—especially when they mixed multiple concepts like binary search and DP. The managerial round felt almost like an afterthought at that point. I did get some questions about my background and projects, but the technical depth they expected was significantly higher than I had prepared for.
Prep tip from this candidate
Focus heavily on advanced DSA techniques that combine multiple concepts—specifically binary search with DP, and coordinate geometry with DSU. The sparse table problem in round one was manageable, but the hard problems in rounds two and three required deeper algorithmic thinking than typical LeetCode mediums.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Media.Net
What do you tell an interviewer when they ask you what your strengths and weaknesses are?
| Question | |
|---|---|
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Merge Sorted Lists | |
| Subscription Overlap | |
| Top Three Salaries | |
| Closest SAT Scores | |
| Employee Salaries | |
| Random SQL Sample | |
| Monthly Customer Report | |
| Comments Histogram | |
| Top 3 Users | |
| String Shift | |
| Flight Records | |
| Find the First Non-Repeating Character in a String | |
| Rolling Bank Transactions | |
| Minimum Change | |
| Customer Orders | |
| Raining in Seattle | |
| Like Tracker | |
| Recurring Character | |
| Find the Missing Number | |
| Scrambled Tickets | |
| Weighted Keys | |
| P-value to a Layman | |
| Find Bigrams | |
| First Touch Attribution | |
| Prime to N | |
| Size of Joins | |
| Job Recommendation |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an opening round that combines coding problems with roughly 20-25 multiple-choice questions on OOP, DBMS, Linux, networking, logic or math. Coding difficulty is described as easy to medium, such as merging sorted linked lists or 2D array manipulation. One campus candidate reported no separate resume screen.
Candidates report one to three online technical rounds of DSA across arrays, linked lists, graphs and DP. Difficulty typically rises between rounds. Interviewers may ask for better time and space complexity after a working answer. One candidate met hard combined problems, such as binary search with digit DP and DSU with coordinate geometry.
Several candidates report questions on networking, operating systems and caching, and one mentioned inodes and system calls. One candidate reported a dedicated socket programming round, where a working TCP/UDP server had to be written in Python. This round may not be part of every candidate's process.
One SDE 2 candidate reported a low-level design round, designing class structure and state for a chess game. It was followed by a hiring manager conversation about current projects that moved into high-level design. This likely matters more for experienced candidates, but only one report here describes it.
Candidates report project deep dives covering technology choices and implementation logic. Some mention a managerial or HR stage at the end, which one described as straightforward.
