DISH Network Technologies Software Engineer Interview Questions
& Process

The interview process had 3 rounds: an online coding and aptitude round, a technical interview round, and then an HR round. The first round was an online coding/aptitude test, which I don't remember much about since it was from college placements. Then there was a technical round where they asked about OOPS concepts, and I had to solve problems on linked lists and arrays, but no tree or graph questions. They also asked about my projects and which technical subjects I found interesting. Finally, an HR round where they asked about handling stress and staying organized.

So the whole interview was like, two parts, both technical. The first part was all about Data Structures and Algorithms (DSA), checking how well I could solve problems and knew the basics. They threw a bunch of coding challenges at me, like array stuff, strings, linked lists, trees, graphs, DP, and greedy algos. I had to actually write the code and make sure it was efficient, like time and space wise. They really wanted to see if I could optimize and talk through my solutions, even considering edge cases. The second part was System Design. This was more about building big systems. They gave me a scenario, like designing a web service or a chat app, and I had to break it down. We talked about the different parts, like front-end, back-end, databases, and how they'd all work together. Scalability was a big thing – how to handle lots of users and traffic. We also covered things like load balancing, data consistency, and fault tolerance. They really grilled me on the trade-offs, like CAP theorem, and how to keep things running smoothly and reliably. Communication was key throughout, explaining all my design choices.

I interviewed with Sling media a couple of years back. The recruiter set up a phone interview for me with their manager. I waited for him to call at the scheduled time for 30 minutes, but he never did! He emailed me hours later saying something came up, which was pretty unprofessional. I agreed to reschedule. The manager didn't call the second time either! By then, I should have just told them off, but I went ahead and accepted their third invitation. This time, it was with an architect, not that manager. The architect had a really strong Indian accent, but since I'm also from India, I could understand him fine. He asked about my projects. I talked about a project where I used MongoDB, explaining why we chose it and how it fixed issues we had with our old MySQL setup. I mentioned we were really happy with the switch to Mongo. Then, this architect started grilling me about why we didn't use Cassandra instead. I explained that Mongo was easier to transition to from a relational background because it had secondary indexes, and some team members were already familiar with it. I wasn't against Cassandra, but he insisted we should have gone with it. I figured if Mongo solved the problem and was working great, then it was a good choice. I would have even stuck with MySQL if it could have effectively handled the problem. It's a big advantage that RDBMS have with ad-hoc query flexibility, as long as your data volume isn't massive. I notice a lot of engineers think using the newest NoSQL database is the coolest thing, without fully grasping what relational databases offer. I suspect this guy was one of them. I'm open to using any tech, whether it's Microsoft, Apple, Google, or anything else, as long as it gets the job done. Being biased towards or overly devoted to one technology shows a lack of open-mindedness. You just don't know what other products can do. I'm glad I didn't waste more time by going for an in-person interview.