Pros: For development roles, the hybrid model was pretty decent. We could usually do 2-3 days WFH, which helped a lot. They were also okay with adjusting daily hours if you needed to deal with personal stuff.
Cons: The main issue is project dependency. If your client wanted you fully onsite in the Lisbon office, then remote work was totally off the table. This lack of consistent work flexibility was a pain, especially as a Software Engineer.
Advice to Management: Try to standardize work flexibility policies across all projects, not just leave it up to client demands. This would really help retain talent in IT consulting.
Show more
Pros: As a Software Engineer in Lisbon, the compensation and benefits package is actually pretty solid. I've worked on some genuinely interesting digital transformation projects with good tech stacks. The hybrid work model is a nice perk for flexibility.
Cons: The work-life balance for software engineering roles can be a real challenge. Expect to put in a lot of extra hours, especially when client deadlines hit. It often feels like a corporate consulting firm where burnout is a common topic.
Advice to Management: Leadership needs to focus more on project scoping and protecting team members from excessive overtime. Better resource allocation would improve employee morale significantly.
Show more
Pros: I've worked on some interesting software development projects here. The hybrid work model is a decent step in the right direction, letting us split time between home and the Lisbon office. It's nice to have some choice.
Cons: Still, the flexibility isn't great for all roles. As a Software Engineer, I felt pretty tied to specific hours, even with hybrid. Getting approval for fully remote work or truly flexible hours beyond the hybrid model felt like a big hurdle.
Advice to Management: Consider offering more options for genuinely flexible hours or fully remote work for roles that can support it. The current hybrid setup is a start, but it could be improved to better support employee needs across the tech industry.
Show more
What is the typical team structure like at InnoWave for software engineers, and how does collaboration usually work?
At InnoWave, software engineering teams are generally structured into smaller, cross-functional units. Collaboration is facilitated through agile methodologies, with daily stand-ups and regular sprint reviews to ensure alignment and knowledge sharing among team members.
What is the team collaboration like at InnoWave for software engineers in their Dublin office?
At InnoWave, the culture emphasizes collaborative development among software engineers. Teams typically use agile methodologies, with regular stand-ups and cross-functional communication to ensure projects move forward efficiently in the Dublin tech hub.
What is the typical work-life balance like for software engineers at InnoWave, especially with the company's focus on project delivery?
Work-life balance at InnoWave can vary depending on project timelines, but the company generally supports flexibility for its technical teams. While some periods might require extra effort, there's an emphasis on efficient work practices to maintain a sustainable rhythm for developers in the IT sector.
What is the typical team structure and management style like at InnoWave for software engineers in their Dublin office?
InnoWave generally operates with cross-functional teams, often employing an agile methodology. Management is typically hands-off, focusing on project delivery and individual autonomy for experienced engineers.
