Unity

Pros: The best part is definitely my teammates. Working as a Software Engineer, I've met some really smart people dedicated to game development. There's good WFH flexibility, even remote from Austin, which is a big plus.
Cons: The overall company culture feels a bit disconnected sometimes, especially since we went full remote. Communication from top leadership can be a bit vague, which is typical for a big tech company. It feels like they're struggling to maintain that early startup vibe after scaling so much.
Advice to Management: Try to reconnect with the remote workforce more effectively. Clearer communication from leadership would really help bridge the gap and strengthen the company culture.

Pros: I really liked the hybrid model they had for software engineers. It made commuting to the San Francisco office much easier a few days a week. The WFH options were also solid, giving me a decent work-life balance.
Cons: The biggest downside is coordinating with global teams. Sometimes you're stuck with early morning or late evening meetings, which can eat into personal time. It's tough to truly disconnect when you're expected to be highly responsive.
Advice to Management: Try to establish clearer core collaboration hours that respect different time zones. It would help improve work-life balance for everyone, especially for game development roles.

Pros: I really appreciate the hybrid model for Software Engineer roles; it allows for some WFH days each week. Being able to skip the daily commute to the San Francisco office a few times is a huge plus. The general expectation is pretty clear, making it easier to plan personal life.
Cons: Sometimes the required in-office days feel a bit rigid, and it's tough when teams aren't all aligned on the same hybrid schedule. More flexibility on which days you need to be onsite would be better. It can sometimes impact collaboration for game engine projects if key people aren't in.
Advice to Management: Try to make the hybrid policy more adaptable to individual team needs and project phases. Giving teams more autonomy on their in-office schedule could really help improve morale and productivity.

Pros: It's exciting to work on a product used by so many game developers globally. I learned a ton about the game engine industry and real-time 3D tech. The team members are generally smart and collaborative, especially within our software engineering roles.
Cons: Upper leadership can feel out of touch with technical realities at times. Decisions often change quickly, making planning tough for individual contributors and remote teams. There's not enough transparency from senior management on strategic shifts, which impacts morale a lot.
Advice to Management: Focus on clear communication and consistent strategy from the top. Involve engineering leads more in product roadmap decisions. Listen to feedback from individual contributors to avoid burnout.

Pros: The base salary for a software engineer is pretty competitive, which is nice. For big tech in the game development industry, it's definitely solid. RSUs are part of the package too, though their value fluctuates.
Cons: Healthcare plans aren't the best compared to past companies I've worked for. Dental coverage felt really basic. Annual salary increases were barely noticeable.
Advice to Management: Review the healthcare and dental benefit plans to make them more competitive. Also, ensure annual raises actually keep up with inflation.

Pros: I was remote from Austin, TX, which was great for WFH. The flexibility for a Software Engineer was decent on most days. I could usually manage my 40-hour weeks outside of major deadlines.
Cons: Crunch times for big game development milestones were intense, though. You'd definitely feel the pressure in this big tech environment. Sometimes I was working 60+ hours a week on tight deadlines for core 3D engines.
Advice to Management: Try to forecast project timelines better to avoid last-minute crunch periods. It really wears down the engineering teams, especially those working on core 3D engines.

Pros: As a Software Engineer, the hybrid work model is pretty flexible. I mostly worked remote from home, which was great for my schedule. They're decent about letting you arrange your hours for personal stuff.
Cons: Sometimes the team in the San Francisco office has meetings that are tough for remote folks. There's an expectation to be available, even with flexible hours, which can extend your day.
Advice to Management: Really try to accommodate remote teams better for meeting times. It makes a big difference for people not in the main office.

Pros: Working on the Unity engine gives you great experience for game development. Projects are often challenging and you get to learn from really smart people in the San Francisco office. It's cool being at the forefront of real-time 3D innovation.
Cons: Career progression for senior software engineer roles can be super slow. There aren't many clear paths to move up unless you actively switch teams. You really have to push hard for promotions, even with solid performance. It often feels like you're stuck in the same spot.
Advice to Management: Please make career ladders clearer for engineers and invest more in formal mentorship. The promotion process needs to be more transparent and consistent across different development teams.

Pros: The immediate teams are usually solid. I've learned a lot technically as a Software Engineer here. The hybrid work setup in the San Francisco office is pretty good too.
Cons: Upper management changes direction a lot. It's hard to trust leadership decisions for the long term. This instability definitely affects morale across the big tech company.
Advice to Management: Try to be more transparent and consistent with long-term strategy. Frequent pivots really wear people down and make it tough to plan our work effectively.

Pros: They do offer a hybrid model which is a plus for many. Being able to work from home a couple of days a week is solid for work-life balance, especially for those in game development roles. There's good tech and resources available for remote work too.
Cons: It's tough because some teams demand more in-office days than others. True WFH options aren't always consistent across the San Francisco office, which can be frustrating. You can feel a bit stuck if your manager isn't keen on flexibility.
Advice to Management: Management should standardize hybrid policies more across all engineering teams. It'd really help with consistency and stop some of the team-specific disparities.