Status: Offered
Education: One of the top 7 IITs (non-circuital 2024 passout)
Years of Experience: ~2 Years
Current Role: Software Engineer at Product based company

I recently interviewed for the MTS-2 position at Omnissa. Interestingly, I applied and interviewed for two entirely different teams concurrently—one focused on the .NET/C# ecosystem and the other on Java.

Both roles had no language-specific restrictions during the DSA rounds; the interviewers were mostly focused on concept clarity, algorithmic problem solving, and production environment experience. Here is a detailed breakdown of my experience for both tracks.

Track 1: MTS-2 (.NET & C#)

Online Assessment (HackerRank):
This was a Low-Level Design (LLD) style question. I was provided with an in-memory repository class and had to complete a Service class by utilizing its objects.

• Requirement: Complete the implementation of all methods to pass the test cases.
• Language restriction: Only C# was allowed for this specific OA
• Result: Passed all test cases.

Round 1: DSA & Problem Solving (Eliminatory):

• Problem 1: Coin Change. I walked the interviewer through the brute force, better, and finally the optimal solution using 1D memoization (Dynamic Programming). They expected working, compilable code in a language of my choice.
• Problem 2: Get the top K elements from a list.
• Follow-up: System Design / Large Scale Data. I was given a file containing a billion records (IP addresses visited on a site, mapped by timestamp) and asked to find the top K most frequent IP addresses.
• My Approach: I proposed a divide-and-conquer strategy (similar to External Merge Sort/Chunking). I explained how I would divide the massive file into smaller, manageable chunks, process the frequencies in-memory for each chunk, and then merge the results to fetch the final top K.

Round 2: DSA & Problem Solving:

• Problem: I was asked two problems that were fundamentally similar to Course Schedule, but framed in a real-world context: "Method chaining in Visual Studio."
• Follow-up: The second question was an extension of the first. I recognized the underlying graph dependencies and used Topological Sort to solve them.

Round 3: Hiring Manager (HM) Round:

• Deep Dive: We discussed my backend development work at my previous organization.
• Architecture: I was asked to draw the High-Level Design (HLD) of my team's architecture and explain the specific microservices and APIs I owned end-to-end.
• Behavioral: Standard cultural fit and behavioral questions.

Track 2: MTS-2 (Java)

Note: There was no HackerRank OA for this track. The recruiter reached out directly to schedule the first round. After clearing Round 1, the recruiter invited me to the Omnissa Bengaluru office for Face-to-Face interviews for the final two rounds.

Round 1: DSA & Problem Solving:
This was an intense, rapid-fire round where I had to solve 3 problems, providing the brute-better-optimal approach and working code for each:

1. Rotate an array to the right by k steps.
2. Course Schedule II.
3. Longest Substring Without Repeating Characters.

Round 2: LLD & Database Design (Face-to-Face):

• Problem: Draw the LLD for an E-commerce Platform.
• Twist: The interviewer explicitly did not want a standard Object-Oriented Design class diagram. Instead, they wanted me to design it entirely using databases.
• Requirements: Define API endpoints, handle complex queries, and implement pagination.
• Deep Dive: The interviewer grilled me on optimization. I was asked how I would handle concurrency (e.g., two users buying the last item in stock). I discussed locking mechanisms (optimistic/pessimistic) and was asked to write out the specific methods for handling these concurrent transactions.

Round 3: Hiring Manager (HM) Round (Face-to-Face):

• Deep Dive: Heavy discussion revolving around my resume and past backend projects.
• Architecture: I was asked to design the HLD of Skyscanner. Honestly, I fumbled this quite a bit as the scope was massive.
• Feedback: Despite strong technical feedback from Rounds 1 and 2, the HM seemed a bit hesitant, possibly due to my non-circuital engineering background. However, the overall process still concluded positively!

Key Takeaways:

• Omnissa heavily values core foundational concepts. Be prepared to transition smoothly from LeetCode-style graph problems to practical DB concurrency issues.
• Always structure your technical answers: Brute Force $\to$ Better $\to$ Optimal.

Good luck to everyone preparing! Let me know if you have any questions in the comments.

Compensation Details: https://leetcode.com/discuss/post/8384004/need-advice-omnissa-mts-2-spring-financi-em8j/