YuJa Reviews

1. Nasty CBO who doesn’t mind embarrassing employees in front of everyone. Hypocritical CEO who plays nice in normal times, but you will know what he is really like when you are not in his best interests. 2. All managerial personnel as a whole are sly and devious. They plot and retaliate against employees, like those who dare to not like the company and give them resignation notice. They would give you a "surprise attack" by asking you to leave immediately, like in 10 minutes, some day after you gave the notice, and you won't even have time to say goodbye to your coworkers before your account is deleted. The conspiracy can be quite sophisticated, something they may have done several times. Everyone in the management level knows about it but no one would tell you until the very last 10 minutes. They would act like, “OK we will discuss your last day and let you know”, and then give you the surprise. The previous day, they would fool you to come to the office the next day (if you are WFH during COVID) using some lies, so you will be able to return the front door key on site before leaving. Otherwise, the off-boarding process would take another day and the surprise attack wouldn’t work. 3. There is an “exit interview” in the off-boarding process, where they ask for reasons for your resignation. Don’t expect them to take your answers sincerely. Instead, they see them as valid reasons to retaliate against you as mentioned above. Be cautious, they also put obstacles in your just requests, like asking for employment documents, after you quit by ignoring your calls and emails. 4. Outdated tech stack: JSP, Servlet, jQuery and Ajax. 5. They don’t even use Slack, Jira or IntelliJ. Instead, they use Google Chat, Pivotal Tracker and Eclipse. I guess that is because they are cheaper, but at the expense of lame UX, which makes developers’ lives harder. 6. Bottom-end second-hand working computers. Most monitors are not 1080P. I even saw some developers use 18-inch screens. 7. Probation period as long as 6 months. No extended health insurance until the 5th month working there. And the coverage is just bottom-end. 8. Developers are treated like tools and aren’t appreciated. Work is repetitive and boring, most of which is fixing tech debts and you cannot learn much. They don’t care at all. You won’t get any feedback about your performance, neither positive or negative, even after you completed a big ticket or came up with a better solution that is not your responsibility at all. 9. Developers are under constant pressure, which is this company’s way to keep these “tools” productive, instead of by lifting their morale. There wouldn’t be anyone saying “you must code faster” to you directly, but they can definitely make you feel it. For example, by assigning you multiple tickets at once, by setting an unrealistic deadline, and by making you report what you accomplished in the past few days in front of everyone twice per week. 10. They don’t invest money or time in employees, who again are just tools in their POV. There are no training programs. When hiring, they don’t consider if your skill set fits the job, but when working if you tell them that you need to spend a few days learning before starting a ticket, you would be in trouble. Tech leads don’t mentor sincerely. They answer no more than you ask and get impatient easily. 11. Don’t expect any family-like or friend-like relationship in this company. The culture in this company is rude and cold. When going through the recruitment process, they act as nice as possible, but that isn’t the reality after you join the company. Most people’s communication styles are blunt, and people rarely use “please” or “could you” or any softeners. This is partly because of the managerial personnel’s characters, partly because, as said above, everyone is under constant pressure, so they don’t have time or patience to type more words. This culture affects people. Those co-op QAs, I believe they are polite students in university, but in this company, they communicate just like anyone else. There are zero team activities for coworkers to know each other, which is imaginable due to that workload. Barely any communication between developers. No discussion about code structure or implementation. In the team’s Google Chat channel, on average there are only 1 – 2 messages about work posted per day (on one dare to post non-work related messages). Even after a few months’ working, there could still be team members who you haven’t ever talked to at all. 12. Due to the lack of discussion, you can imagine how bad the code quality is. Tech leaders are incompetent with making structural decisions. Maybe they don’t have time due to tight deadlines, or simply don’t care. The consequence is plenty of bad designs and tech debts in the codebase. The lack of thorough code review just makes it worse. Only team captains review code, and they have tickets to work on, so the review process is rough. Pull requests are just poured into the staging environment, which, as a result, always contains bugs. Just take a look at their mobile app, you would know which level this company is at. If you work there long enough to get used to it, you would become a worse developer, not a better one.