Experience to work there for some weeks - Software Development Engineer In Test (SDET) bei BOLD: Mitarbeiterbewertung

1.0
24. Apr. 2023
Empfehlen
CEO-Befürwortung
Geschäftsprognose

Pros

Facilities. Thats it, they will provide you some good facilities to work there. Cab,good assets, Gym vouchers, Food, good pay. Some Team members helping you a lot.

Kontras

If you ok to just go to any organization that provide you good facility you can join there. But other then that nothing else I can promise you. What i feel in very short spell that its totally depends upon team you join. Pls pls check before joining in which team you going to work. They will not disclose before you join bt pls ask before joining otherwise it will be hell for you. I think most of the teams are good dont ever think to join the backend team(API) or there core payment team. Equally nightmare for Tester and developers. Manager is checking small small things. If you join for 15-20 mins late they will tell like "make sure you join on time otherwise your performance bonus will be effected". Long and repetitive KT and Reverse KT session.(Trust me this is another headache). Politics is on peak.(MANAGER,DIRECTOR,SENIOR everyone involved here) I saw people left the company with in a year and returning lakhs of bonus amount(if you left before year you have to return around 20% of total CTC). Pressure is too much (specific for API backend and core payment team). going to 5 days work from office. Avg office infra. I left in weeks so you can imagine the real life there.

Mehr Bewertungen zu BOLD entdecken

5.0
4. März 2026
Empfehlen
CEO-Befürwortung
Geschäftsprognose

Pros

Great work life balance Super fun team

Kontras

Not many to be honest

2.0
15. Apr. 2026
Empfehlen
CEO-Befürwortung
Geschäftsprognose

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.

Kontras

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
Bewertungen anzeigen nach: Hilfreich|Sterne|Datum|Alle