Neueda Reviews

- Projects: Overall, the projects are either non existent, meaning you will come to "work" everyday and there won't be anything to do for a couple of months - yes, months - or when you finally get a project, you will either work on a completely different set of technologies that you were hired for or the project will be something that the client didn't want to work on, so they just hired a third party company to work on the "boring stuff". - No career progression - You join as a developer and leave as a developer, the whole structure is flat, apart from the "Junior Developers", who are just underpaid people from third world countries. - The "line managers" aren't line managers, they are just a bridge between the two managers who go out looking for projects, and the developers who are going to work on these projects. They are not technical, even though they are the ones responsible for choosing who is going to work on what. You have one meeting every two weeks with your line manager to discuss how the project is going, and by that I mean they just want to know if there's any internal conflict or if the deadlines can be met, it usually takes 2 or 3 minutes. - The first developers hired by the company were all based in Riga, Latvia, and they patronised the entire company, they mistreat everybody else who weren't hired by their direct recommendation, creating a lot of internal conflict. This is due to the lack of hierarchy, so whoever "shouts louder" wins. - Don't allow remote work at all. - The projects doesn't have scope - which means that you will work blindly, where the client will ask the line managers for something do be done, the line managers will then pass that on to the developers but as the line managers aren't technical themselves they don't know at all what the requirement is all about, and you as a developer isn't allowed to contact the client directly. - They say they "use" agile but there's nothing of that. The only thing they have is a Jira board and daily meetings. Forget about story points, sprint plannings, PO, etc. - Childish behavior during code reviews, lots of internal conflicts in this regard that usually "escalate" to the line managers, as the team architecture is flat. But as the line managers aren't technical they try so solve the conflict on a behavioural level. There's even one case of a guy who was fired because two other people got together and complained about him not being technical enough, even though nobody else in the rest of the team shared the same view. - Annual leave is low, only 21 days. - During the interview they will judge you by your age in order to give you a salary, older people get offered 45k and up and younger people get offered 30k or even less. Your experience/knowledge doesn't matter. People who where recommended by one of the developers based In Riga, who were there at the beginning of the company, usually are the best paid, going from from 65k and up.

Management: - Your line manager has no authority to do anything (in project, with customer, with teams). Line manager can only listen to you, report upwards, wait for response and then give response to you. - Passive-aggressive tactics are used a lot. For example - you are presented with one option and asked whether you like it or not. If you say "no", then "let's try to make it work" phase begins and you end up going with this option anyway. It is done so it was not management who forced you into a choice, but rather you who made a decision to agree. - It seems that no one in management really understands technology and how it works. - Some problems were solved by management telling "you think that is is a problem, but actually it's not" and that's the end of story. Projects: - Business is build around "we need to keep as much people as possible on this project, for as long as possible", ignoring everything else. - You don't really have possibility to influence where you will land - Sometimes you might be thrown into a project like a baby into a pool, and just expect to swim from get-go. - It seems that teams for projects are formed at random Personal growth: - No one really cares about your what are your skills. You are DevOps? Do frontend here. You are frontend guy? Do DevOps on this project for a 2 months. You are team of java developers? Nice. Let's transform you into a team of DevOps guys. And so on. Customers: - I have never seen Neueda said "no, that's a really dumb idea, we are not going to do that" to a customer. It is always - "of course, we will make it work, how about hiring a few more people?". Hardware: - Whatever customer gives you is what you will be working with. - There is high chance that you will be forced to use VDI (remote desktop)