Johnson Controls

Pros: The benefits package is definitely a plus at Johnson Controls, which is great for a big corporate environment. As a Controls Engineer, you get to work on some really interesting building technologies and large-scale projects. There's also clear potential for career growth if you're proactive.
Cons: Sometimes, leadership feels pretty disconnected from what we're doing on the ground. It can be frustrating when decisions are made at the top without a full understanding of the practical impact on our smart building solutions, especially for those of us working onsite in Milwaukee.
Advice to Management: Try to bridge the gap between executive leadership and the engineering teams, especially those working onsite in our building technologies division. More direct engagement and understanding of daily operations would be really helpful.

Pros: The benefits are pretty decent here, with a solid 401k match and good health insurance. As an HVAC Engineer in the Milwaukee office, I got to work on some really big commercial HVAC projects. They also offer a pretty solid hybrid model now, which helps a bit with commute.
Cons: Work-life balance is often a struggle, especially when project deadlines for building automation systems get tight. I consistently found myself working over 50 hours a week, which wasn't great. It felt like leadership sometimes prioritizes aggressive timelines over employee bandwidth.
Advice to Management: Please consider more realistic project timelines and better resource allocation for engineering roles. This would really help improve work-life balance and prevent burnout for your teams.

Pros: The collaborative spirit within our `Milwaukee office` team is genuinely good; everyone helps out. We do have a `hybrid model` with some dedicated `WFH days`, which is a decent start for `software development teams`. It's a very stable `large corporate environment`.
Cons: The `onsite requirements` feel pretty rigid for a `technical role` like mine, even when the work could easily be done `remote`. If you're remote and an urgent issue comes up for `building technologies` projects, you're expected to drop everything and come in, which kills any `work flexibility`. `Work-life balance` suffers sometimes because of unexpected `onsite` requests.
Advice to Management: Please re-evaluate the actual need for `onsite` presence for `software development roles`. More trust in `remote work` would significantly improve `work-life balance` and `work flexibility` for your `technical teams` without hurting productivity.