V2STech Solutions Reviews

No clear product vision, scalability planning, or market research; work is limited to repetitive CRUD-based projects. Innovation and new ideas are not encouraged or supported. Excessive micromanagement with strict focus on logged hours rather than outcomes. Internal appreciation and recognition are minimal, even when clients acknowledge good work. Continuous employee activity monitoring, including screenshots, creates a culture of distrust and invades privacy. No standard project management tools; manual Excel tracking is mandatory, with escalation emails for minor misses. Employees are expected to work on multiple projects simultaneously, but systems and hardware provided are inadequate. Feedback is collected formally but rarely acknowledged or acted upon. Policies are selectively enforced—very strict for leaves and WFH, but inconsistent elsewhere. Bonus rules change unpredictably, sometimes affecting high performers due to overall team performance. Poor work-life balance; long hours and weekend work are common, with compensatory off rarely honored. High attrition due to continuous hiring and firing. Lead roles come with responsibility but no authority; team changes are made without consultation. No structured development lifecycle; frontend and backend work is often done in reverse order, affecting quality. Performance reviews are one-sided, with ratings appearing pre-decided. Strong emphasis on NDA and data security, yet third-party monitoring tools capture sensitive information. Deployment practices are unstructured and risky. No dedicated seating; seat changes are sometimes used as a control mechanism rather than for collaboration. Lack of respect for experience and seniority; inputs from seniors are frequently dismissed without discussion. Interview process is extremely weak, with no proper screening or basic technical evaluation. Salary increments are consistently delayed, often without transparency or clear timelines.

Weak interview and hiring process: Candidates with experience are hired without proper role-fit evaluation, leading to mismatched expectations and productivity issues. Freshers are expected to deliver from day one without structured onboarding or training. Lack of engineering practices: There is no focus on system design, software architecture, UI/UX, software quality, documentation (FRD/BRD), or proper planning. Most projects are treated as “simple CRUD” work, regardless of actual complexity. The primary focus is on delivery, while long-term quality, scalability, and maintainability receive little importance. Disregard for experience and expertise: Estimates provided by experienced team members are frequently reduced without technical reasoning. When challenges are raised, they are often perceived as incapability rather than genuine technical risks. Unrealistic workloads: Employees are frequently stretched across multiple projects, leading to long working hours (often more than 12 hours a day) and weekend work, with little to no recognition. Micromanagement and lack of trust: Daily timesheets, activity trackers, and screenshot monitoring create a stressful environment. Even technical failures in tracking tools require justification. Stand-up meetings often extend far beyond reasonable duration. Poor infrastructure: Outdated and underpowered systems negatively impact productivity and employee well-being. Feedback not acted upon: Instead of addressing repeated employee feedback, new employees are encouraged to post positive reviews, raising concerns around transparency and improvement culture.