Pay is okayish, but there are other better places with much higher pay and better employee wellbeing.
Otherwise, absolutely nothing. Everything in general is toxic.
This place can make you hate development — not because of an immense workload, but due to the complete lack of guidance or mentorship. Compared to previous organizations I’ve been part of, which had great mentors and thorough KT (Knowledge Transfer) sessions, Zeta offers little to no support. For freshers or those with less than two years of experience, mentorship is virtually nonexistent. Even when you reach out for help, you often receive no guidance — yet if you make a mistake, you face excessive criticism and questioning from people who themselves may not know the solution.
There is a poor work-life balance with 5 days work from office — frequent weekend work with no recognition, rewards, or appreciation. The HR department is unprofessional and unhelpful. They often delay responses to raised requests, fail to follow up, and tend to look down on newcomers to the industry. Unlike most organizations that provide sufficient time to upskill and adapt, Zeta expects employees with little to no prior exposure to their products to become 100% proficient after utterly mediocre training.
I applied online. The process took one week. There were two technical interviews: - First interview: DSA with two medium problems. One was a Course Schedule II variation, and the other was DP, specifically DP on graph. - Second interview: DP, specif
The process included intro and problem-solving rounds with a good deal of discussion around each topic. You need to have a good understanding of each topic to begin with, and you must have a deep understanding of microservice architecture.
I applied through a college or university. The process took two days. First, there was an OA, followed by two rounds: one was DSA and one was technical. Medium-level DSA questions were asked in round one, and system design was in round two. The OA w
I applied online. The process took one week. There were two technical interviews: - First interview: DSA with two medium problems. One was a Course Schedule II variation, and the other was DP, specifically DP on graph. - Second interview: DP, specif
The process included intro and problem-solving rounds with a good deal of discussion around each topic. You need to have a good understanding of each topic to begin with, and you must have a deep understanding of microservice architecture.
I applied through a college or university. The process took two days. First, there was an OA, followed by two rounds: one was DSA and one was technical. Medium-level DSA questions were asked in round one, and system design was in round two. The OA w