Pros
On the positive side, I was the only one on the team, which meant that I had a lot of autonomy and independence. I was able to work on my own projects and ideas without too much interference from other team members. Additionally, I was able to work on a variety of tasks, from supporting existing functionality to searching for bugs. This kept the job interesting and challenging.
Cons
However, there were also some drawbacks to working at Epam. Firstly, the management was very blurry, abstract and ambiguous. I often found myself unsure about what was expected of me and what I should be working on. This lack of clear direction made it difficult to prioritize my tasks and work efficiently. Secondly, the project structure was terrible. There was no clear organization or hierarchy in place, which made it difficult to find the information I needed and to collaborate effectively with other team members. Finally, the fact that we were using Java 1.6 was a major drawback. This version of Java is quite old and outdated, which meant that I was limited in terms of what I could do with the language. It also meant that I wasn't learning the latest and greatest features of Java, which could have been a major disadvantage in the long run. Overall, my experience working as a Java software developer at Epam Systems had both pros and cons. While I enjoyed the autonomy and variety of tasks, the blurry management, terrible project structure, and outdated technology were major drawbacks.
