employer cover photo
employer logo
employer logo

West Bend Insurance Company

Is this your company?

Was good before it became a sweat shop for IT - IT Grunt West Bend Insurance Company Employee Review

1.0
4 Jun 2014
Recommend
CEO approval
Business outlook

Pros

Salary and benefits are very good, campus is exceptional, subsidized lunch - avg. cost to employee is about $5 depending on what you order, large dining area, gym, nature trails out back, company picnics, bonus checks yearly.

Cons

They used to boast about being a premier place to work and they were a premier employer under all of the senior leadership throughout the company's history up through CEO and President Tony Warren. The current CEO/President rose through the ranks of the sales silo of the company and now it's all about the bottom line. The rich culture they had from inception is gone and that's the saddest part. Gone is the work / life balance. Gone is recognition for extra work and long hours. Gone is the retention of long time dedicated employees. Now the turnover in IT has been ridiculous in the last few years. I would have given this company 5 stars back in the day, now I give it zero but I'm forced by this site to give it at least one. Consider it a charity star.

Explore other reviews about West Bend Insurance Company

5.0
17 Jun 2026
Recommend
CEO approval
Business outlook

Pros

Great office with good cafeteria

Cons

Work is a little slow

3.0
15 May 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