#final?
bold lynx
after OA technical
I had been rigorously preparing with LeetCode for the past two weeks, expecting a technical deep dive in my interview. However, the experience turned out to be quite different. I was asked about TCP/IP troubleshooting, and I explained how ping, tracert, and Wireshark are used for network diagnostics. Strangely, the interviewer dismissed Wireshark, which left me wondering what alternative tool they had in mind.
Next, they presented a file creation issue on disk, and I pointed out that storage could be full as a possible reason. Instead of discussing further, they pivoted to stress testing—to which I explained the role of chmod in permissions. Yet again, I was met with an uncertain response, followed by a sudden shift to swap space, thread vs. process differences, and other topics.
Finally, when we got to the coding question, it wasn’t something directly from LeetCode but rather a pizza store problem involving toppings and scalability considerations. I implemented a clean OOP-based approach, but they quickly jumped to asking about scalability—without much clarity on what aspect they wanted to focus on.
Overall, the interview felt scattered, with abrupt topic changes and vague questioning. It was an interesting experience, but I was left feeling that it didn’t truly assess my skills in a structured manner.#I used a hell of slangs If you want entertainment read the Hindi version
Sorry for slangs, I am helpeless and hopeless at this time
mental bloom
what role?
faint escarp
Doesnt sound like typical swe interview