Pros: Good salary for beginners. Great learning budget.

Cons: Lots of formalities. You get stuck on asking people permissions to access stuff pretty often.

Pros: Not the hardest work, but interesting tasks.

Cons: No business requirements, no dev processes.

Pros: - Friendly and supportive teammates. - Comfortable office environment. - Modern and well-equipped laptops. - Paid overtime.

Cons: - Chaotic processes with little structure or organization. - Pressure from management (from other locations), who often avoid improving processes and instead blame engineers for missed deadlines (at least it appears so from an engineering perspective). - Micromanagement and excessive control over tasks. - Poor CI/CD pipeline; environments frequently break, and fixing them is time-consuming. - Lack of strong development culture; engineers from other locations often write unstructured, "spaghetti" code and fail to cover changes with unit tests. - Insufficient automated testing; QA performs regression tests manually. This creates a vicious cycle, as time spent on manual testing and fixing environments leaves little time to start automation. - Overestimating titles of engineers. It’s important to note that the quality may vary between projects, but in my case, this project was the worst I’ve encountered. My feedback aligns with that of other former employees from the same project.