Good team with room for improvements
Gut am Arbeitgeber finde ich
I really like the regular exchange between the developers and the current tech stack.
Schlecht am Arbeitgeber finde ich
It often feels like developers end up being the cleanup crew for product work that wasn’t properly prepared. The same pattern repeats: a new “great idea” has to be implemented immediately, even though the problem isn’t fully understood, requirements stay vague, key details get postponed with a “we’ll figure it out later,” and the real impact only becomes visible once we’re already deep into implementation, as if that’s just normal. People call it “agile,” but in reality, it’s more like chaos with Scrum terms on top: priorities change mid-sprint, alignment happens after decisions were already made. Instead of building the product steadily, it ends up feeling like we’re jumping from fix to fix, just hoping nothing major blows up.
Verbesserungsvorschläge
Developers need more appreciation as real partners, not just ticket implementers. That’s not only about money, but also about how work is prepared, how much context and ownership they get, and whether they’re equipped with the right tools to do the job properly.
Arbeitsatmosphäre
The working atmosphere is low at the moment. Of course, there are the missing salary adjustments, but also the ongoing confusion in product development, with repeatedly unclear, not well-defined ideas. This is very stressful for the development teams, which have to modernise the platform simultaneously.
Work-Life-Balance
Work-life balance depends heavily on the team you’re in. Some teams operate under noticeably higher pressure and a constant delivery mode. On top of that, when individual performance in the team is weak, the workload often gets redistributed to the people who are already delivering — meaning you end up picking up extra tasks to keep things moving. In reality, work-life balance is good for some but not consistently across the company.
Karriere/Weiterbildung
Career opportunities are very limited, as there are currently no changes or growth. Additional training opportunities are available within the budget, but unfortunately, there is a lack of coordination with future technological challenges, and restrictions are in place to ensure that not too many people attend the same conference. In addition, it is expected that new knowledge will also be easily acquired during work alongside normal tasks. Therfore more attention should be paid to ensuring that developers are well prepared for future challenges.
Gehalt/Benefits
The salary is average. However, I think it's unfair that too much attention is given to salary bands rather than individual performance. Especially when you see that the workload is unevenly distributed. This reduces daily motivation.
Kollegenzusammenhalt
Team spirit is generally good. You can ask questions anytime, and you’ll usually get a helpful answer. Lately, though, it feels like more people are optimizing for visibility and promotion, doing “their own thing” to stand out instead of pulling in the same direction. That kind of ego-driven work is creeping up, and it means important shared tasks get dropped or delayed. When you’re trying to deliver a bigger feature that needs real teamwork, it becomes seriously frustrating.
Vorgesetztenverhalten
Managers are there, but it feels like they're just supposed to manage us all somehow and concentrate on the problem cases. Agreed yearly goals are often not met or made possible due to daily project work. Sometimes I also miss opportunities for honesty about my personal development. The real feedback usually only comes when you apply for other jobs but don't get them.
Arbeitsbedingungen
The working environment is good thanks to 100% remote working. However, the technical setup, with poor VPN access, constantly having to request permissions, and not being able to use certain standard tools because the company would rather save on licensing costs than enable developers, makes everyday life uncomfortable for developers.
Interessante Aufgaben
You simply work based on what others have decided. Topics are defined, and the tech stack is clear. As a developer, you just do your tickets: a new endpoint or a new Vue component. The most interesting thing usually happens when something doesn't work as expected because the topics weren't well prepared. But then it's more stressful than interesting work.
Image
Umwelt-/Sozialbewusstsein
Umgang mit älteren Kollegen
Kommunikation
Gleichberechtigung
Arbeitgeber-Kommentar
Dear colleague,
thank you very much for your detailed and thoughtful feedback. We truly appreciate the time and effort you invested in sharing your perspective. It means a lot that you highlight the regular exchange among developers and the tech stack as something positive; strong engineering dialogue is very important to us.
At the same time, we take your criticism around unclear requirements and shifting priorities very seriously. Agile should not feel like chaos, and developers should be true partners in shaping solutions, not just implementing tickets.
For a deeper and more detailed conversation on the other topics you raised, please feel free to approach your People Partner or any member of the People Team. We’re always open to an exchange.
Also, did you take advantage of any of the various open and anonymous Q&A sessions we regularly offer? We’d like to encourage you to make use of these regular formats and share your feedback there.
Thank you again for sharing your view.
Your Eurowings Digital People Team