Viatick Reviews

1. Management and Leadership Issues - The organization suffers from unstructured management practices. - Hiring more developers is not the answer to their problems. - Senior developers are resistant to feedback, take criticism poorly, and lack leadership or mentoring skills, despite claiming otherwise. - When developers raise concerns about the feasibility or complexity of requirements, or explain the root causes of issues, these explanations are often dismissed with a condescending "know-it-all" attitude with claims of having over decades of tech industry experience. - On-site deployments are poorly planned, with no standard operating procedures or protocols in place. The company reacts rather than acts, and when problems occur, the development team is often blamed. - There is a lack of distinction between hardware and software issues, and management often ignores explanations when these distinctions are made. As an IoT company, they should understand that some faults are hardware-related and cannot be resolved by the software team, especially remotely. 2. Work Culture and Employee Treatment - Limited opportunities for career growth for developers, who are often viewed as interchangeable resources that can be replaced with lower-wage employees. - Compensation is below industry standards, especially compared to other companies in the same sector. - Developers are expected to know and handle everything, not for their own growth or learning, but so the company can exploit highly skilled developers under the label of "full-stack," without paying them a fair wage. - The company lacks empathy towards employees, with frequent unexpected late-night calls that exceed contractually agreed-upon working hours. - There is no performance review process, nor any budget for employee learning and development. 3. Software Development and Processes - The company demonstrates an inadequate understanding of the proper software development lifecycle, following a flawed, barely functional version of a waterfall model. - There is no established code review process. - No coding conventions are in place. Upon joining, the codebase had no unit tests in place. - The codebase is disorganized, with no clear documentation regarding microservices, database design, or workflows. - The importance of sprints and clear requirement analysis is misunderstood, leaving developers responsible for figuring out what needs to be built. They often work with vague requirements and are later blamed when deliverables do not meet expectations. - Many features are casually discussed and then forgotten once delivered, leading to the development of unused or unnecessary features, wasting development time and effort. 4. Quality Assurance and Testing - Quality Assurance practices are almost non-existent, yet developers are held accountable when issues arise, despite the lack of a proper QA process to ensure product quality. - Proper QA and testing processes should be in place to anticipate potential issues and allow time to address them, rather than trying to fix problems in production and adding unnecessary pressure to the development team. 5. Communication and Project Management - Communication of business requirements is poor, and developers are frequently tasked with responsibilities beyond development, such as data entry and QA testing. - Timelines for feature development are unrealistic, with expectations for completion within hours without considering feasibility or complexity. - Deployments and production launches occur without prior announcements or a formal code freeze, creating unnecessary disruption. 6. Lack of Structure and Strategy - There is no clear demarcation of hardware or software issues, especially being an IoT company. Faults should be tested in advance, and issues that arise should be properly classified and addressed with buffer time. - Developers should be aware of the hardware specifications their software will run on to prevent issues in advance. - The organization lacks proper planning for on-site deployments, reacting more than acting when problems occur, and placing unnecessary pressure on developers during crises.

High pressure from bosses Low pay No 13th salary No career path