Codal

Pros: As a software engineer here, I did get some work-from-home days after my first year. It's nice for certain projects, especially in the digital agency space. The remote option helps a lot.
Cons: Initial months were strictly onsite in the Chicago office. It felt a bit rigid for junior roles. I couldn't always shift my hours easily, even for simple things.
Advice to Management: Consider more consistent WFH policies across all teams. It would help retain talent, especially in competitive software development.

Pros: I've found the work-life balance to be pretty decent most of the time as a Software Engineer. We have some flexibility with our hours and can do a hybrid model with some WFH days. It's nice not being in the Chicago office five days a week.
Cons: Project deadlines for custom software development can get pretty intense. Sometimes you're pushing past 5 PM to hit a client launch, which definitely impacts work-life balance. The late nights happen more than I'd like.
Advice to Management: Focus on better project scoping and realistic deadlines for clients. It would really help reduce the crunch periods and improve employee well-being.

Pros: I liked the chance to work on cool digital transformation projects. Being a remote Software Engineer meant I had a good WFH setup and solid flexibility with my schedule.
Cons: Job security isn't always the strongest due to the client services model. As an IT consultant, you're only as secure as the next project, so there's always a slight worry about bench time between software development gigs.
Advice to Management: Try to ensure a more consistent project pipeline for IT consulting staff. Clearer communication on long-term role stability would help alleviate concerns for employees.