Hatch

Pros: The executive leadership really understands the tech industry and has a clear vision for the product. They're good at communicating the big picture, especially in a fast-paced startup environment. I learned a lot about scaling software development.
Cons: Middle management can be inconsistent, which impacts daily tasks for Software Developers. There's not always clear communication between teams. Sometimes project timelines feel unrealistic.
Advice to Management: Focus on empowering middle management more. Improve cross-team communication to ensure everyone's on the same page. Really listen to feedback from the individual contributors, especially in our hybrid work model.

Pros: The teams here are full of smart, dedicated people. I really appreciate the hybrid model with WFH days; it helps a lot with work-life balance, especially for a Software Engineer in San Francisco. There's a decent focus on innovation within our immediate teams.
Cons: Upper management struggles with clear, consistent direction for software development projects. Our sprints often felt all over the place, which was tough. It's hard to see a clear path for career growth here, especially for senior engineering roles. Leadership changes strategy too often without solid follow-through.
Advice to Management: Try to communicate strategy more clearly and stick to it longer. Give team leads more autonomy to execute without constant shifts. Invest more in career development programs for all employees, especially for engineering roles.

Pros: The team is pretty collaborative, which is good for a remote setup. You can learn a lot from senior engineers, especially in software development. There's a decent sense of camaraderie among the individual contributors.
Cons: The company culture can feel a bit cliquey at times. It's tough to really connect when you're fully remote from Austin, TX, even for a tech startup. Sometimes, managers don't really push for team-building outside of work, leading to isolated feelings.
Advice to Management: Try to build more inclusive social events, even for remote employees. Foster better cross-team communication and break down internal silos. Acknowledge that a remote-first culture still needs dedicated social investment.

Pros: The engineering team here is solid, and I've learned a ton from my peers. We're working on some pretty interesting AI product development, which keeps things engaging for us software engineers. It's cool to see the innovation when it actually comes together.
Cons: Leadership is a big problem. There's just not enough clear direction or a consistent vision from upper management. This makes it really hard to plan projects and sometimes you feel like you're spinning your wheels in the San Francisco office.
Advice to Management: You've got smart people here, but you need to give them a clear roadmap. Consistent communication and a unified vision from the leadership team would make a huge difference for daily operations and employee morale.

Pros: For a Software Engineer, the base salary is decent, especially in the San Francisco office. They offer standard health insurance, which is pretty solid. My compensation as a Software Engineer felt competitive enough to keep me.
Cons: The 401k match isn't great, definitely below what big tech companies offer. Stock options are minimal, not really a significant part of total compensation. Don't expect many unique perks or premium benefits here.
Advice to Management: Rethink the 401k matching and introduce more meaningful stock option packages to be truly competitive.

Pros: The work flexibility here is great, especially being able to work remote from Vancouver. I appreciate not having to commute, which really helps with work-life balance. For software engineering roles, it's generally a 40-hour week.
Cons: Sometimes project deadlines in product development can be really intense. It feels like a typical tech startup push when we're close to a launch, and those weeks aren't great for personal time. There's no real official 'disconnect' reminder from leadership.
Advice to Management: Try to set clearer expectations around project timelines to avoid last-minute crunch periods. Encourage teams to truly disconnect.

Pros: The hybrid work model is a solid perk. I really appreciated the flexibility to work from home a couple of days a week, especially being in the Toronto office. It helps a lot with personal errands. For most junior software engineer roles, the day-to-day isn't too demanding.
Cons: The biggest issue is how client deadlines dictate everything. Sometimes, on major engineering projects, you're working really long hours to meet a delivery. It's not always a true 40-hour week, and WFH days can be tricky to coordinate when crunch hits.
Advice to Management: Try to manage client expectations better so engineering teams aren't constantly scrambling. A clearer policy around WFH during peak periods would also help.

Pros: I liked the flexibility with the hybrid model. You can often work remotely a couple of days a week, which helps avoid the commute. For a global engineering firm, they do try to respect personal time.
Cons: Project deadlines can be intense. As a Junior Project Coordinator, I sometimes worked 50-hour weeks, especially during crucial phases. It's not always consistent, which makes planning tough.
Advice to Management: Try to better manage project loads to avoid burnout, especially for junior roles. More consistent workloads would really improve morale and work-life balance across the board.

Pros: I've learned a ton working here. The teams for software development are super collaborative. The hybrid model really helps with work-life balance.
Cons: Leadership often shifts priorities with no warning. It's tough for Product Manager roles to keep up. There's not enough clear communication from the top, especially in this growing startup environment.
Advice to Management: Please try to provide more consistent strategic direction. Communicate changes better to the whole company, especially to those of us in the Toronto office. Support your managers in executing these strategies.

Pros: The hybrid model is a big win. We get 2-3 days remote from the Toronto office which is solid for personal errands and avoiding the commute. For a large EPC industry player, it's pretty good flexibility, especially as a Project Engineer.
Cons: It's not truly flexible though; you can't just pick your WFH days whenever. Client meetings and project milestones often require onsite presence. Sometimes it feels like there's an unspoken expectation to be in more.
Advice to Management: Keep supporting the hybrid model, but maybe clarify expectations for 'flexible hours.' It would be good to ensure consistency across different project teams within the engineering department.