Thurston Software Solutions, Inc

Pros: I can work remote from Austin, TX, which is a major plus. As a Software Engineer, I get some flexibility for personal appointments, like doctors, if I plan ahead.
Cons: The core hours are pretty rigid, so true work flexibility is limited. It's a corporate software company, so it's not like a startup where you can easily adjust your entire day.
Advice to Management: Consider relaxing the strict core hours for employees in the tech industry, especially for remote teams. More trust and autonomy would go a long way.

Pros: I like the option for WFH days, which is helpful as a Software Engineer balancing personal stuff. The company does allow for some flexible hours for software development, which is a plus. We use a hybrid model, so it's not all onsite in the Seattle office.
Cons: The WFH days can be inconsistent. Sometimes management pushes for more onsite presence without much warning, which makes planning tough. For technical roles, I feel like full remote options should be more common, not just hybrid.
Advice to Management: Managers should clearly communicate WFH policies and stick to them. Consider offering more remote options for experienced software development roles.

Pros: You usually get solid 40-hour weeks as a Software Engineer here. The hybrid work model in the Austin, TX office helps a lot with personal appointments and errands. It's a pretty good environment for regular software development work.
Cons: Sometimes the agile sprints get really intense, especially during crunch time for new features. It can be tough to completely log off on those weeks, impacting your work-life balance. This isn't great for mental health in a corporate environment.
Advice to Management: Try to smooth out the project timelines more consistently to avoid those intense crunch periods. It'd really help with developer burnout and retention.

Pros: Some senior managers genuinely care about their engineering teams. They try to provide resources for software development projects. The hybrid model works pretty well for me.
Cons: Upper leadership often makes decisions without enough input. Communication from the top isn't always clear. It's tough for junior Software Engineers to advance quickly in this corporate structure.
Advice to Management: Work on more transparent communication from the top. Give project leads more autonomy and really listen to feedback from engineering teams on strategic decisions.