Benefits: Good compensation and (when you're not on-call) work-life balance.
Stability: Unless you're in mid-upper management, there is comfort in working for a monopoly which is slow to truly modernize and that has ever-increasing human resource needs as clients are added. The job will go on.
Coworkers: Some of the best and brightest group of people to work with.
Micro-management: It's normal to see directors and VPs getting involved in troubleshooting client issues, often multiple times a week. This is definitely leading by example, but it also perpetuates a hero culture that is steeped in favoritism towards holders of proprietary knowledge.
Status quo: Despite the overly-vast and brittle legacy codebase, nobody is willing to insist to upper-management that a rewrite is necessary and urgent. It's telling that a memory dump is often the default troubleshooting technique: In one week I've seen more of them than in all my career elsewhere. The irony is that this is vastly more expensive than the apparent cost of modernization.
Castle-building: The head of product is unapproachable to criticism and suggestions, and focuses on features rather than simplicity. The result is that the product is overly-complex to use and excruciatingly slow to run, and causes unnecessary stress on engineering just to maintain an already-excessive time-to-market.
Lack of diversity: One can predict with great accuracy the ancestral origin of the staff based solely on the team and management level. It also seems self-perpetuated.
Simplify. Get rid of unnecessary baggage and legacy decisions. Favor modern approaches that scale well and more efficiently, and that enable faster iteration and development. Be critically introspective.
Interview was scheduled for and 90 mins first 30 mins introduction was given by HR regarding position and that are the expectation. Similarly asked about current role and responsibility in my org. Same thing was repeated by next 30 mins by interviewe
The interview process was pretty routine, with three rounds in total, including HR. They didn't ask too many technical questions, but mainly focused on my resume. The last two rounds were 30-45 minutes.
Phone interview followed by on-site interview. The whole process took about 1.5-2 weeks. The interviewer asked many technical questions related to database developing skills, DB maintaining skills and Unix as well. Some soft-skill questions was ask
Interview was scheduled for and 90 mins first 30 mins introduction was given by HR regarding position and that are the expectation. Similarly asked about current role and responsibility in my org. Same thing was repeated by next 30 mins by interviewe
The interview process was pretty routine, with three rounds in total, including HR. They didn't ask too many technical questions, but mainly focused on my resume. The last two rounds were 30-45 minutes.
Phone interview followed by on-site interview. The whole process took about 1.5-2 weeks. The interviewer asked many technical questions related to database developing skills, DB maintaining skills and Unix as well. Some soft-skill questions was ask