Unfair Treatment, Favoritism, and Sudden Layoffs in Onboarding Team - Client Onboarding Specialist Tenant Inc. Employee Review

2.0
5 Sept 2025
Recommend
CEO approval
Business outlook

Pros

Worked for more than 3 years on the Tenant project with good exposure to onboarding and client support. Opportunities to learn during product launches like StoragePro. Colleagues from the Indian team showed strong teamwork and dedication.

Cons

Sudden terminations without clear notice—even for employees with strong performance records. Office politics and favoritism seem to influence decisions more than actual performance. Employees from the Indian team, particularly those who joined from Alokin, often feel undervalued. Company policies around leave and WFH are not applied consistently—different rules seem to exist for different groups. In the Bangalore office, WFH approvals appear easier for local employees, while others face stricter scrutiny. Leadership in the onboarding team tends to depend heavily on the Indian team for handling technical issues and escalations, yet recognition for these efforts is often missing. This has created a perception gap between contribution and credit. Internal transfer requests and skill-based growth opportunities are frequently overlooked. Recognition for achievements is very short-lived. After the StoragePro success (largely supported by the Indian team), contributions were quickly forgotten. Since early 2025, layoffs have disproportionately affected the Indian team. This has led to the perception that “if you join onboarding, you will leave Tenant soon.”

Explore other reviews about Tenant Inc.

5.0
30 Sept 2025
Recommend
CEO approval
Business outlook

Pros

Great ppl, passionate of tech

Cons

Can be stressful and challenging

1.0
25 Aug 2025
Recommend
CEO approval
Business outlook

Pros

Talented peers in Tech Support. There are quality employees across the customer-facing teams, just severely lacking the backing to succeed.

Cons

Decision-making prioritized preference over evidence, and the people closest to customers were routinely sidelined. Cross-team communication broke down, and leadership often defaulted to interdepartmental blame instead of owning outcomes. Leadership and decision-making Senior leadership operated in silos. Feedback from frontline teams was dismissed or reframed as a “lack of effort,” masking real staffing and prioritization gaps. Strategy was presented as certainty even when data and on-the-ground signals said otherwise. Execution and product quality Releases repeatedly went out with systemic QA gaps that produced major regressions. These were predictable results of weak release gates, unclear ownership, and shipping to a calendar rather than to readiness. When failures reached production, Tech Support absorbed the fallout while still managing a heavy backlog of unresolved defects. Support and escalation Ticket escalations frequently aged without meaningful updates within the technology organization. Operations did not consistently back Tech Support when cross-team help was required, leaving support accountable for issues it had no authority to prevent. Culture and accountability Stated values around collaboration and customer focus were largely aspirational. Raising risks early was treated as negativity. The environment rewarded keeping heads down over surfacing problems, so the same fires returned sprint after sprint. Impact Customers experienced avoidable breakage, morale declined, and turnover increased. Those doing the heaviest lifting had the least influence on the inputs that drive outcomes.

7
See reviews by: Helpful|Rating|Date|All