employer cover photo
employer logo
employer logo

West Bend Insurance Company

Is this your company?

Incompetent IT Leadership - Anonymous employee West Bend Insurance Company Employee Review

2.0
28 Sept 2017
Anonymous employee
Recommend
CEO approval
Business outlook

Pros

IT Management is so bad you can do nothing for months on end. If they catch on, throw out an acronym or buzzword. Your non-management coworkers are exceptionally skilled and have been keeping the company afloat. Don't worry, they're here to help ( Unless they're running behind on something, you'll get thrown under the bus then. )

Cons

Where to start? The incompetence runs so deep. IT Leaders here truly are the bottom of the barrel, in terms of both IT acumen and overall reasoning. Lately there's been a push to bring younger talent in. It's a transparent effort to get fresh grads used to stretching further than their experienced counterparts for less money. If a "leader" has been with the company for a while, they'll even make up positions just to keep them happy, regardless of little they actually contribute. This is the kind of place where leadership actually thinks blanket statements make good policy.

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