Pluspunten
From my experience at EPAM, there are several aspects that stand out positively. One of the biggest advantages is the autonomy and flexibility I've been given. I appreciate that there's no micromanagement; I can choose to work from the office or home, and my hours can vary as long as the work gets done. This level of trust is invaluable. EPAM also excels in providing learning and development opportunities. The internal communities for various specializations are a fantastic resource for knowledge sharing and professional growth, whether it's listening to experienced colleagues or even presenting my own insights. The access to internal learning platforms, as well as resources like LinkedIn Learning through an EPAM email, are great for continuous skill enhancement and certification. For someone looking for their first job, EPAM can be an excellent entry point. In today's market, finding that initial position is incredibly challenging, and EPAM offers a solid starting salary for juniors ($600 after taxes for FOP Group 3). The medical insurance and the Lviv IT Cluster card are also significant benefits, contributing to overall employee well-being. Finally, the EPAM University programs, particularly the Android course I took, are highly beneficial. Despite some outdated content due to the war, the structured learning environment and the depth of material provided a much faster and more comprehensive learning experience than self-study.
Minpunten
However, my time at EPAM hasn't been without its drawbacks. A major concern is the compensation policy. It feels like EPAM is very tight with money, especially when it comes to raises. As a junior, I've had to actively fight for a higher salary, and even then, the increases are often minimal ($100-200), which isn't a normal raise for someone at this stage. While the starting pay for a first job is decent, the progression seems slow and difficult. Another significant issue, particularly on large projects, is the slow pace and inefficiency. A considerable amount of time is often spent just trying to understand requirements and navigating complex codebases, often leading to writing only a few lines of code after extensive effort. This can be frustrating and can hinder a sense of rapid personal development, especially when compared to roles where I was the sole developer and constantly learning new things. The level of bureaucracy is also noticeable. There seems to be a service and a ticket for everything, even for minor requests like getting a mouse for a laptop. While not a huge problem individually, these small procedural hurdles can add up and affect overall efficiency and experience.
