Applied for a Senior Python Developer role at Omnissa Bangalore.

Round 1 - Technical Discussion - 60 mins

The first round was a 60-minute technical discussion around my resume, projects, architecture decisions, and different engineering scenarios. This round was actually good. The interviewer was knowledgeable, respectful, and gave useful insights during the discussion.

I cleared it and the recruiter told me the next round would be System Design.

So naturally, I prepared for System Design.

Round 2 - System design ?? - 60 mins

The second round started with around 15 minutes of database/design questions like why database indexes are faster and why B-Trees are used.

Then suddenly: “Now we’ll do problem solving.”

No prior mention of DSA. No indication that most of the “System Design” round would actually be coding problems.

First question: Given an array and k, find the maximum pair sum less than k.

I gave a brute-force solution. The interviewer wanted the optimal solution and kept pushing for it before moving to the next question. Eventually, I requested to attempt the second problem because time was running out.

Second question: Given two strings, check whether one can be converted to the other with atmost one insertion or deletion, or replacement.

I solved it in O(n) time with O(n) extra space. Again, the expectation was an O(1) space solution.

And that was it.

After the interview?

An automated rejection email:

“We have decided to move forward with other candidates.”

No recruiter call. No feedback. No explanation.

I completely understand getting rejected because I couldn’t arrive at the optimal solutions. That’s part of interviewing.

But if a round is going to primarily evaluate DSA/problem solving, why call it a System Design round?

Candidates spend hours preparing based on the information recruiters provide. The least companies can do is accurately communicate the interview format.

And after multiple rounds, an automated rejection with zero feedback makes the whole process feel unnecessarily transactional.

Anyway, posting this so the next person interviewing for Omnissa doesn’t walk into a “System Design” round expecting System Design.