However, if you aim to mostly focus on coding only, this is may be not a good fit. They also have some other general problems. For devs: - mind that this is a software house so expect some bench time between the projects. I personally don't mind but not everybody like it - there's a lot of writing blog posts instead of coding and some people don't really like it - as a developer, you're expected to lead projects. Leading can mean being a dev + project owner and/or technical supervisor. They don't mention it being a requirement during recruitment process at all. So if you want to learn handling projects, then it's great, if not then this may not be a place for you - this is minor but can be irritating: developers are often treated as resources and not like people. Expect being informed about your projects as the last person. Often your peers know where you'll be assigned before you - the pay is not that great. Of course, it depends on where you live. Still, if you're a lead it doesn't affect your salary and you're usually required to do it. This may be important for some people In general: - higher management tends to micromanage (not all of them thankfully). To be fair, they improved it significantly already, but this still sometimes happen. Not going to influence regular developers, but can be important if you're considering other departments or being a manager - they say a lot about DEI (Diversity, Equity, Inclusion) being important, but not much real work is done to improve the culture. If it's important for you or if you're from underrepresented groups, think twice before joining. It's not the worst it could be but also not really great and it seems there's very little interest in HR to improve things outside of creating slides and employer branding