xIQ Reviews

1. Worst work-life balance - You buy SOME hours of the employee, not all of them. You can't just schedule a meeting or invite someone to a meeting whenever you feel like it. The upper management (CEO specifically) might be competent, but you're nothing if you don't have empathy. Stop micro-managing and hire people who you can actually trust. Make the hiring process of better quality. 2. Learn to respect your employees - They are your employees whose hours you pay for, not their dignity. They are not your slaves. Just because you pay them (which btw every company does) doesn't mean you can mock/threaten them over their pay scales and bonuses. Learn to respect them and stop being rude. Otherwise, no matter how many people you hire, your retention rate is still gonna go down the hill. 3. Stop putting pushed fake reviews on Glassdoor through your current employees. 4. Stop using i2c's name for your own welfare. I've seen a lot of people being told about i2c all along and landing at xiQ in the end. 5. Foster a culture of empathy, love and kindness. The CEO needs to focus on that primarily. Plus, improve your onboarding.

(Most of cons here are for those that know how industry should work. If you are fresher, I dont recommend you working here. Because you'll come out with no skill at your disposal.) Short Story: No refreshment, events, no LinkedIn page that appreciates & highlights employees, Developement process are worse, no industry standards to follow in codebase. No guidance & mentorship given to freshers. There is n't xiQ's own HR. They rely on i2c which makes it tedious to communicate. No way to let your concerns be heard. -- Only way to let your conerns be heard is talk it through to your CTO. But all you will ever get is "I am busy, will discuss later." And that later will Never come. There are no defined processes for code reviews, bug fixing, feature addition, etc. They don't follow industry's best practices. Recently they refactored the code in the name of just introducing comments, doc-string and DRY principle. Which only made the codebase EVEN WORSE. Now there are legendary and viscious bugs in those enchanted modules and I'm sure you wouldn't want to wake them up. Thing is you'll be scared to fix something. There is not a single process (apart from an outdated document) to understand the domain. Its guerilla style boyses & girls, you're working on prod DB DIRECT. Majority about 95% data belongs to testing and belongs to us - the developers. There's no career growth planned out for you.