Pros
f you’re in the ODP team, you’ll get exposed to many tools and workflows, mainly because you’ll be left to figure everything out yourself. Opportunity to learn a lot by self-initiative due to lack of proper processes and support.
Cons
Chaotic Engineering Process: In the ODP team, as a Build and Release Engineer, you're constantly forced to refresh packages due to ever-changing code and unstable requirements. Releases are rushed and disorganized. Untrained Promoted Managers: Many managers are internally promoted without any formal training, leadership experience, or understanding of people management. This results in unclear direction and poor team dynamics. No Role Clarity: There’s no clear definition of your responsibilities — you’re expected to “just know.” Leadership often lacks visibility into what technical teams, like ODP, are doing. Nepotism Over Merit: Promotions, conversions, and transitions are often influenced by relationships with CxOs or founders. Connections matter more than contributions. Lack of Product Vision: Founders are fixated on sales and acquiring big-logo clients — even small deals — rather than building a strong, long-term product roadmap. Contradictory Culture: Leadership leans on the “we’re a startup” excuse to avoid promotions or resources, but uses “processes” to justify rigid rules when convenient. Timezone Burnout: Senior leaders operate from US/Canada and expect the India team to stretch late into their working hours, often leading to burnout. HR Breaches Confidentiality: Feedback shared with HR isn’t safe and may be used against you — raising serious concerns around trust. Vague & Uneven Policy Enforcement: Leave and WFH rules are ambiguous, and managers enforce them arbitrarily. HR stays silent on inconsistencies.