Worst year in HotelRunner - Customer Support HotelRunner Employee Review

The frontend projects use relatively modern technologies. Provides employment stability and the opportunity to gain experience.

While the frontend stack is modern, the rest of the technology stack feels outdated and lacks clear architectural patterns. This makes debugging and identifying the root cause of issues difficult. Technical decision-making and analysis processes often feel weak or insufficiently structured. Jira tickets are frequently created with minimal or unclear descriptions. Requests from developers to improve ticket clarity are sometimes discouraged, with the explanation that this is the current working style. Sprint planning is often inconsistent. Sprints may start without clear planning, and a significant amount of work can be added after the sprint has already begun. Communication style in some meetings can become tense, which negatively impacts team morale and motivation. In some cases, product-side roles appear hesitant to take ownership, which can lead to responsibility being shifted to other team members. Team collaboration feels limited. Instead of operating as a cohesive team, individuals often work more independently. Important updates such as annual salary adjustments are sometimes communicated very late, and raising questions about them can feel uncomfortable.

That said, I still gained a lot of valuable experience and learned how to stay focused and productive under less-than-ideal conditions.

One of the main challenges at HotelRunner was the workload. The responsibilities were quite demanding, but the compensation didn’t always reflect that. Another issue was the pace of internal processes. Even small decisions or requests could take a long time, which sometimes made it hard to move quickly or be efficient.