It is important to Pascal to develop not only professionally but also personally in his new role. He has to, because contrary to his expectation of a lively technical exchange and corresponding questions from his colleagues, the focus is primarily on a human level. Many questions and requests for support relate to interpersonal situations, which gives him the valuable opportunity to grow on a personal level and improve and refine his communication skills.
Pascal's working day is varied and dynamic and while some days he jumps from one appointment to the next or deals with a multitude of messages and emails, other days he can devote himself entirely to his developer tasks. This variety keeps him on his toes and brings new challenges and opportunities every day.

One of the biggest challenges for Pascal is the sheer endless variety of backend areas. In contrast to the frontend, where a harmonious and uniform concept prevails, the backend presents itself as a multifaceted mosaic. Pascal, who comes from the Order&Inspect world and is very familiar with the backend system there, is motivated by the task of maintaining an overview of the different areas while the usual day-to-day work of a developer continues.
Here he sets himself the goal of familiarizing himself even better with the different backend systems in order to gain the overview that his colleagues expect and need from him.

In addition to strategic issues, his main focus is on the further development of his team. Regular development meetings and open discussions are an integral part of his work. He specifies a time corridor, but the frequency is the responsibility of the employees.
His unusual questions, which he likes to include in conversations to encourage a change of perspective, are particularly exciting:
- "If you had to spend a day in my role, what would be the first thing you would do?"
- "What decision would you make if you were sure you wouldn't fail?"
These questions not only help him to generate new ideas, but also to recognize current challenges and moods within the team at an early stage.

He has set himself goals to actively shape his role and use his position to initiate change within the company. For example, the development of guidelines is on his agenda, which should offer developers a creative framework in which they can develop. empiriecom is very proud of the fact that the developers can act very freely, and yet it is important to regularly question how sensible some procedures are. For example, when experimenting with particularly unusual programming languages that only a few people have mastered. These guidelines are intended to ensure that all developers work within sensible framework conditions and can develop their creativity.

Another key point for Pascal is the centralization of various processes. Due to the highly valued freedom of the teams, it often happens that tasks are processed twice or three times.
In his discussions with the backend developers, Pascal not only wants to find out what expectations they have of him, but also to ensure that projects and code that are needed but neglected are no longer neglected. There should be no areas that no longer receive any maintenance and that no one dares to tackle.

A standardized back office for the store is a goal that is already being driven forward by others, and Pascal wants to support the processes as best he can.