Clarion Technologies Reviews

(.Net Team) - Lack of technical developers, no architect - TL and SDM are zero about new technologies and management (all are 8 to 12 year exp in clarion). - I don't recommend the developer who are from MNC company, it is better to find another one. - Work hours maintained by one Sapience tool and you need to spend 8 hours for a day, for that every developer moving mouse so they will fill work hours in sapience which is most worst thing to do. - They are policy oriented if you don't follow there policy, you will not get good hike or appraisal (no matter how long you work in office or sound in technologies) - You will get appraisal depend or rating out of 5 by following there policy or rules 1. Fill daily status in some internal tool 2. add idea monthly 3. send daily status to LT 4. every week code review by QA which is worst part for me. because it is no one following. - They are client oriented not employee (so you need to work any how day night to complete client task) - If your performance is low they will fire at any movement so no security, It happens with my 2 friends.

Well there is a lot of Cons to talk about. I cant discuss it all but still I try to cover most of it. 1. For Developer there are hell of things to do every day. Every day they have to provide their 8 hour work to client along with they have to write timesheet and blog for every day of how they invested their 8 hours. On top of that every week they have to fill a PR Form. A PR Form is a 40 hours work done by developer in a week, which they need to explain it to a Tester, who is not a dedicated tester of your project. So basically there would be two testers one tester who got a good idea of project and the other who have no idea of project and would test your work for every week. 2. TESTER : QA Process is bad and weakly implemented with no importance at all. Very less billable project to work on. Mostly work on PR Form. PR Form which is a 40 hour work done by any developer and QA have to test it in 2 hours. SO basically there not much to learn on this process and provide very fever experience to grow as there is no dedicated project to work on. 3. Only targets small projects which only lasts for 1 or 2 months. Mostly maintenance projects. So developer just get to brush up their already learned concepts to work on and for testers it easy just to find bugs. For testers ad-hoc testing is primary focus as no test case no procedure is followed. 4. Could remove you from your position at any time if you're bench. They have very fewer projects they first ask developers on different technologies to join and then they try to look out projects if projects are not found then developer remains on bench and then after few months they are asked to leave the organization. In front of 6-7 cases occurred. Employer were asked to leave. Also in QA they eliminate them at any time. 5. For on bench people small internal projects are given to work on. Which is of no use and sooner you'll frustrated and spend your time on playing TT or carrom. 6. Lack of devices : As there are projects which require devices like ipad, iphone and android. But the company has only one phone of each. And there arises many dispute among developer and testers of different projects to work on device. The company has got 1 android device and that of lava. Atleast they should get an android phone of good company.