My immediate team members are really what make this job enjoyable most of the time. The benefits and pay are also a great plus. As well, there's a lot of work to be done on various systems, and with all of that work, there's a lot of space to learn and grow.
Where to even start here? A lot of people have been jumping ship as of late.
The main problem is that as Verizon Connect has merged into Verizon, Verizon has tried more and more to exert control over systems that it doesn't understand. Instead of listening to the experts who designed these systems about what developers need and what can be done, they only care about obvious numbers.
There's a huge difference between the people who came over from the old company and the Verizon people. Verizon people want something to show off, whereas people from Connect know what can be done and what will work, but Verizon people have the final say.
This mentality comes from the top down and over time has caused many people who made these systems and know how to manage them to quit. Verizon doesn't seem to be learning any lessons from this and instead is doubling down on everything they do. As systems become more and more broken, fewer and fewer people are available that know how to maintain them.
I can see that after the systems stop working because no one who understands them is left, they will probably blame the people who left for "making a bad system." The company culture of Verizon is not good at all and feels very fake, plastic, and inauthentic.
Take more modern approaches to how you interact with employees instead of trying to control and manage every aspect of how they work. People can tell when a culture is forced and inauthentic; don't think they can't.
Until you start listening to employees who have the expertise, system implementations will continue to be subpar.
One Technical interview + One HR round. Basic DSA questions and projects were asked in the Technical round. 1. Write a code for palindrome. 2. SQL. 3. Tech stack of your project and motivation behind it.
The interview process was smooth and professional. The questions were relevant, insightful, and focused on core competencies. The interviewer offered clear next steps and maintained a positive, engaging atmosphere. However, we need to be very strong
The interview process went well. There was a technical round followed by an HR round. The questions were regarding the projects on the resume and general CS topics.
One Technical interview + One HR round. Basic DSA questions and projects were asked in the Technical round. 1. Write a code for palindrome. 2. SQL. 3. Tech stack of your project and motivation behind it.
The interview process was smooth and professional. The questions were relevant, insightful, and focused on core competencies. The interviewer offered clear next steps and maintained a positive, engaging atmosphere. However, we need to be very strong
The interview process went well. There was a technical round followed by an HR round. The questions were regarding the projects on the resume and general CS topics.