Renesas Electronics

Pros: For embedded systems development roles in the San Jose, CA office, there's decent work-from-home potential, especially after big project milestones. I liked the hybrid model that some teams allowed, letting me avoid rush hour a few days a week.
Cons: Work flexibility isn't company-wide. It really depends on your immediate manager's style, which can be tough if you get a traditional manager expecting 5 days onsite. There's not a lot of official policy guiding remote or hybrid work for engineers.
Advice to Management: Standardize WFH and hybrid policies across all engineering departments. It would really help with morale and recruiting for critical embedded systems roles.

Pros: As an Embedded Software Engineer, I did get some hybrid work. It's good to come in for team meetings and then WFH when I need deep focus on microcontroller projects. The San Jose office has solid equipment for development.
Cons: But honestly, the flexibility isn't great compared to other semiconductor industry companies. Many hardware engineer roles are still expected to be 5 days onsite. It feels a bit old school for a big tech company in Silicon Valley.
Advice to Management: Please re-evaluate remote work options. Trust your employees more with where they do their best work. It'd really help attract and keep top engineering talent.

Pros: When I started as a Hardware Design Engineer, the WFH policy was pretty good for a big tech company. We had solid hybrid work options, especially being remote from San Jose, CA some days. It definitely helped with commute times in the semiconductor industry.
Cons: Lately, though, it feels like they're pulling back on work flexibility. It's tough when some managers insist on more onsite days even with an existing hybrid policy. This push for more in-office time kinda impacts work-life balance.
Advice to Management: Listen to employees on what actually works for hybrid models. Mandatory in-office days don't always boost productivity for technical roles; trust your teams more with their schedules.

Pros: The hybrid model helps, letting me work from home a couple of days a week as a Software Engineer. It really cuts down on the Silicon Valley commute. There's generally some flexibility if you need to schedule appointments, which is good for personal stuff.
Cons: Don't expect full remote options; for most firmware development roles, it's a mandatory 3 days in the San Jose office. This limits true work flexibility. Sometimes, global team meetings happen super early or late, which impacts personal time more often than it should.
Advice to Management: Consider more flexibility for experienced software engineers, perhaps 2 days onsite instead of 3. Standardize expectations for remote vs. hybrid work across different departments and global teams.

Pros: The hybrid work model is a good start for work flexibility. As a Senior Embedded Software Engineer, not being in the San Jose office every day really helps with personal appointments. We see a push for more remote options in specific engineering roles, like in automotive electronics.
Cons: Real work flexibility totally depends on your manager. Some teams are super rigid about specific office days. It doesn't feel like a choice then, more like a strict rule. Being hybrid isn't fully remote, which can be tough if your commute is long.
Advice to Management: Push managers to truly get the hybrid concept. Don't just make it a mandatory office schedule. More flexible options for all engineering roles, especially within the automotive electronics division, would be huge for staff retention. Make the policy consistent across the board.