Pros
First of all, situation in different Teams is completely different, so in each specific case feedback may be really different. Not a long time go company was pretty small and it still benefits to atmosphere. The culture of trust, openness and communication between all colleagues (not only developers and including all offices) is pretty high. Especially inside one location (like Spb office) where everybody literally knows each other not only by name. HR's (SpB department at least) are doing pretty good job by trying to support it organising sporting and charity events, pizza parties, small branded gifts, team building activities etc. Nothing really over the top but pretty good for SpB. In terms of development teams are pretty independent in the way how they are doing things and sometimes even what they are doing. In most cases (not really business critical) there are no strict structure to control technical solutions but there is always possibility to get an advice from architects or other teams. From product side situation is really different from team to team. But at least I do not know cases when there is some pressure from Product or Management except from a cases when critical services are completely broken. So freedom is everywhere. And this leads to the fact that there is pretty ok situation with overtimes. They are counted and paid without any troubles. And as far as I know there are no real crunches. There is no trouble with salaries which are on pretty ok level for SpB and can be rediscussed on half-a-year basis. So basically if you know your job well and just want to do it in good atmosphere and without much pressure Infobip should be awesome place.
Cons
Company is rapidly growing (and plans to continue to do it) but it is not really able to support this growth from all sides to keep work comfortable: - Infrastructure teams are constantly overloaded, internal tools works not really stable, especially GUI. There are some constant bothering activities from Security and Networking. - Looks like that existing product management is used to work with small bunch of very experienced, independent and skilful developers. So less experienced colleagues/teams often receive not enough support to really understand what is needed, so sufficient part of this job should be resolved by a team which is sometimes a trouble - Key technical and architectural positions are taken by people who just works in a company for years which is not always fits with their skills. So sometimes architects are more focused on resolving technical tasks and not providing vision. And managers... just do not know how to work with people in efficient way. I wouldn't say that it is trouble for all company, but if you are unlucky enough, you and your team maybe on your own. - There are already some troubles with explaining top mgmt ideas, its reasons and ways of implementation to "simple developers". Currently it is hard to say will it be major issue or not. Another thing that may be not suitable for everybody is troubleshooting. Because teams are 100% for their services they also providing support (at least to other employees), controlling metrics and state of env etc. So especially in highly used services troubleshooting weeks are pretty exhausting time for troubleshooters. So if you are not really want to take responsibility on yourself, investigate in problems on your own or you need to have always someone who will monitor you and support without a mention, then work in Infobip may be challenging for you. But in fact it is worth a challenge.
