Pros
To be absolutely honest, very few people hated Josh Software when they first walked through its doors. Historically, this company possessed a very unique DNA that distinguished it from rigid service-based sweatshops. For freshers and interns, it was an undeniable goldmine of learning exposure. You weren’t hidden behind layers of bureaucratic project managers; you were handed early responsibilities, thrown into client-facing environments, and forced to build real technical confidence rapidly. The single greatest asset of this company remains its ground-level workforce. The developers, the mentors, the technical leads, and the everyday engineering peers are incredibly cooperative, brilliant, and willing to share knowledge. The flexibility in working hours—historically speaking—offered a glimpse of autonomy that kept people fighting through chaotic deployments. Employees rarely said, "This company taught me nothing." Instead, they said, "This company taught me everything I know." The deeply frustrating tragedy is that this incredible technical culture did not survive the company’s structural growth. The original engineering essence didn't disappear because the talent failed; it suffocated because the core management transformed the workplace from an employee-centric engineering hub into an aggressively cold, profit-squeezing corporate entity
Cons
The company’s recent office relocation is a literal and metaphorical downsizing of its commitments to employees. Moving into a significantly smaller facility with severely restricted seating capacity and non-existent parking spaces has turned day-to-day operations into an logistical nightmare. Employees frequently report arriving at the premises only to find there aren't even enough physical workstations available to sit and perform their duties. This workspace crunch matches a desperate commercial strategy; the firm has taken to selling entire internal product engineering units—such as the Moxiworks delivery team—directly over to clients just to balance the books. When internal projects end, the "pool" isn't a safety net; it's a departure lounge. There is a growing, short-sighted executive belief that advanced LLMs can entirely bypass deep engineering logic. This perspective is captured by the internal joke that coding skills are irrelevant because management expects everything to be solved via Claude. By treating AI as a replacement for human engineering craftsmanship rather than a tool to amplify it, leadership forces highly compressed, unrealistic delivery timelines that cause immense developer burnout and compromise code scalability All good seniors who were working here, someone about 15 years, someone about 10, someone about 7-8 yrs are leaving or already left. This definitely signals something. While they are leaving, not all of them received a good gesture of their loyal and long-dedicated, hard-earned gratitude from the founders. For someone, on Wed there was an all-hands and his movement was announced, but the same gesture didn't happen for the most impressive senior who left all of a sudden. Management has increasingly begun using geographical relocation mandates as an aggressive, disguised tool for forced attrition. The strategic lack of empathy is perfectly illustrated by an incident where a highly successful QA Lead—who had literally just been awarded a performance-based promotion the previous month—was suddenly slapped with a mandatory transfer to Hyderabad. Instead of providing standard corporate relocation assistance, management demanded a literal salary cut. To guarantee an exit, they placed this newly promoted leader on a brutal, manufactured performance rubric: bi-weekly evaluations where any single negative piece of feedback over a 90-day window would result in immediate, direct termination. This wasn't an escalated or underperforming resource; this was a high-caliber asset successfully steering major accounts like HDFC Bank and Nipro. It proves that at Josh, your past execution, leadership, and promotions mean absolutely nothing the moment immediate project billing shifts. For the QA teams, operational planning from management is completely untrustworthy. Personnel are routinely ordered to pack up and move to cities like Bangalore under the guise of "short-term, temporary project support." When professionals ask for an exact timeline, management shifts the goalposts in real-time: first stating 2 months, then extending it to 3, then 4, and suddenly stretching it to 6 months. The moment an employee tries to establish boundaries—such as sending a formal email requesting a firm cap at 6 months—they are met with swift retaliation and immediately removed from the account.The operational reality for teams that were transitioned out to Bangalore, like me reveals a systematic trap. I was initially moved out under temporary premises found themselves stranded in an extended relocation loop lasting nearly two full years. The most alarming aspect of this rotation strategy occurs upon return: the absolute moment these long-term QA teams finally managed to return to their base location in April 2025, they were immediately and systematically terminated from the firm. It didn't matter that they were core pillars of the critical HDFC QA delivery team; they were discarded the moment they outlived their immediate, localized utility. A highly damaging cultural pattern emerging from internal feedback is the perception of deep-seated favoritism and insular groupism. Career advancement and protection during down-cycles are increasingly viewed as being dependent on non-technical parameters. There is persistent frustration surrounding the influence of late-evening sports cliques (Football, Cricket, Badminton) starting around 7:00 PM. Employees note that joining these informal, after-hours social circles heavily impacts an individual's visibility and internal backing. Furthermore, a superficial focus on external branding—such as expecting staff to regularly post curated alternate-day compliments of the office premises on social media—has created a workplace where performative visibility routinely outweighs actual technical contribution. Those outside these preferred social circles are systematically marginalized, regardless of their delivery output. The company structure maintains a rigid hierarchy that visibly undervalues non-developer engineering tracks, particularly Quality Assurance and testing teams. Managers routinely discount the analytical time required to write and execute robust test suites, often viewing testing as an idle function. This structural bias results in severe career stagnation: highly competent QA engineers remain fixed in title and compensation for years, while junior developers within favored internal networks are fast-tracked to senior designations in under a year. If you join here as QA you are mostly doomed, I remember there was QA senior to me who was hired as QA, was being asked to work as Support enginer was been given Software engineer role (since they didnt had that role in there system when he joined) it was only last year when i came back in appraisal cycle he was shifted to a QA role, NOTE: he had already worked in the company for more than 6 years till that time and he was give QA engineer role not the Sr QA role, so you know how doomed you will be