Great projects, scope for learning and growth, good leave policy, and exposure to large-scale projects.
Terrible work-life balance. People work up to 16 hours during important projects.
The point I mentioned about scope of learning is offset by the fact that most senior folks aren't very cooperative and willing to share information due to being swamped by work and poor resource allocation. There's also this "knowledge hoarding" culture prevalent in Verizon which is debilitating to juniors and hinders growth.
Management and resource allocation is terrible. You'll find people working hours on end and eventually getting nothing done due to poor planning. There's also a huge number of ad-hoc code releases where you're supposed to make changes overnight and push it to production just on the whim of onshore management. Developers have no say; managers don't care.
Prioritize the well-being of developers. Bring in adequate resources (full-time employees) rather than temporary vendors who don't have much depth of information. Project allocation should be done only after discussing employee availability first.
A 2-hour interview process with two technical rounds: firstly screening and then technical. There were several panels, and each of them was assigned candidates randomly. After the interview, I asked about the project and its kind, but it was more of
My interview was on campus. Three rounds in total. First round was aptitude and coding. Round 2 was the technical interview, followed by the technical HR. The interview went well, actually. I was tested on how well I approach problems, and a few b
It was quite easy. After the online assessment, the next round was a GD. My topic was about online delivery. After that, the next round was technical. They asked an string question, which was easy. After that, we discussed my projects. Another round
A 2-hour interview process with two technical rounds: firstly screening and then technical. There were several panels, and each of them was assigned candidates randomly. After the interview, I asked about the project and its kind, but it was more of
My interview was on campus. Three rounds in total. First round was aptitude and coding. Round 2 was the technical interview, followed by the technical HR. The interview went well, actually. I was tested on how well I approach problems, and a few b
It was quite easy. After the online assessment, the next round was a GD. My topic was about online delivery. After that, the next round was technical. They asked an string question, which was easy. After that, we discussed my projects. Another round