Lowball offers after acquisition, no job security, Un professional HR practice - Senior Software Engineer BOLD Employee Review

1.0
3 Aug 2025
Recommend
CEO approval
Business outlook

Pros

this company has nothing good to share.

Cons

BOLD acquired our company and re-hired some employees , offering a 25% salary cut on Cash component, 0 employee benefits , and no job security — not even a minimum retention period. This was done despite identifying some employees as "critical" to the transition. The HR communication was chaotic and unacceptable. There was no prior intimation, no clarity on timelines, and we were given a short window to sign a legally binding contract — with vague terms and no opportunity for negotiation. They knew employees were vulnerable and used that to their advantage. It felt like a take-it-or-leave-it situation, and they offered the bare minimum required to legally operate. They talk about “internal equity” and “evolving offerings,” but in reality, you’re being slotted into the lowest-cost template, regardless of your experience or contributions. This wasn’t a global experience — it was cost-cutting disguised as standardization. If you care about stability, transparency, or respect — think twice before joining BOLD.

Explore other reviews about BOLD

5.0
4 Mar 2026
Recommend
CEO approval
Business outlook

Pros

Great work life balance Super fun team

Cons

Not many to be honest

2.0
15 Apr 2026
Recommend
CEO approval
Business outlook

Pros

Compensation is competitive and fairly above market, and the work-life balance is real — not just a talking point. Benefits were solid across the board.

Cons

The biggest challenge was the lack of organizational direction. Design teams were largely left to operate without clear strategic guidance, which made it difficult to align work to meaningful outcomes. There were gatekeepers at key decision points that slowed progress without adding clarity. On the product side, many product managers struggled to articulate the problems they were actually trying to solve. This created friction in the design process and made it hard to build experiences grounded in user needs. Without a shared problem definition, teams end up building in circles. My team was laid off about a month ago, which I mention as context — not with bitterness. But it does reflect a broader pattern of reactive decision-making rather than proactive planning

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