employer cover photo
employer logo
employer logo

West Bend Insurance Company

Engaged Employer

Company grew fast and new management people don't 'get it' - Anonymous employee West Bend Insurance Company Employee Review

2.0
Jan 27, 2011
Anonymous employee
Recommend
CEO approval
Business Outlook

Pros

Facilities are great. There are many opportunities for associates to interact with each other.

Cons

The company grew fast over the last ten years. As such, additional layers of management and meny new management positions were created. The old school management was appreciative of their people and very personable to everyone. Many people clammoring for their own advancement (who would stab you in the back in the process) are now in many of the management positions. The unfortunate result is that management as a whole is disconnected from the lower level staff and make decisions based more on covering thier own tails than what is good for the company, customers and associates. Basically, 'ethics be damned and don't rattle any cages. Or, 'how can the next decision make me look better" regardless of whether or not the decision makes sense for the company. Really a shame because the company was great 10 years ago.

Explore other reviews about West Bend Insurance Company

5.0
Jun 17, 2026
Recommend
CEO approval
Business Outlook

Pros

Great office with good cafeteria

Cons

Work is a little slow

3.0
May 15, 2026
Recommend
CEO approval
Business Outlook

Pros

Modern technology stack with opportunities to work on cloud systems, APIs, distributed architecture, and enterprise modernization efforts. There are smart engineers throughout the organization, and some teams genuinely care about delivering quality solutions. The technical challenges themselves can help accelerate growth in areas like Azure, React, system integration, and large-scale enterprise workflows.

Cons

The environment often felt highly results-driven without enough emphasis on communication clarity, collaboration, or healthy engineering alignment. Requirements and priorities shifted frequently while delivery pressure remained high. Many interactions across leadership and architecture boundaries felt transactional instead of collaborative, which could make engineers feel isolated rather than supported. Success often depended as much on navigating ambiguity and organizational dynamics as technical ability itself.

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