Work-life balance. Average people so opportunities to stand out. Stable job.
For people who want to have a laid-back job with work-life balance, it could be a good place to be. But not a job where one could learn lots of new things, unless you learn on your own.
Pass the buck attitude with most of the employees.
Not much learning, as everyday work is mostly maintenance and fixing unreadable/bad old code.
Low pay.
Most of the time will be spent on deciding whose work it is, as people are good at passing the buck around. Being proactive and taking up more responsibilities can backfire with more work with little or no recognition.
There were two coding rounds and one technical round; overall, a pleasant experience. There was a long time between application submission and when the interviewing process began, but the interviewing process was completed in a few weeks.
The experience was really good overall. Although certain questions seemed irrelevant, like file system architecture, it was overall a good mix of OS, DBMS, and computer network fundamentals. Thank you for your time.
Screening phone call, 15-minute introductory conversation. Technical interview consisted of asking basic OOP, 2 LeetCode Easy-Medium questions, and being asked about your project experience. Ghosted and rejected finally after a month.
There were two coding rounds and one technical round; overall, a pleasant experience. There was a long time between application submission and when the interviewing process began, but the interviewing process was completed in a few weeks.
The experience was really good overall. Although certain questions seemed irrelevant, like file system architecture, it was overall a good mix of OS, DBMS, and computer network fundamentals. Thank you for your time.
Screening phone call, 15-minute introductory conversation. Technical interview consisted of asking basic OOP, 2 LeetCode Easy-Medium questions, and being asked about your project experience. Ghosted and rejected finally after a month.