The project implements customer data collection and storage in a way that is in accordance with the GDPR rules of the European Union. In this project I am working on several frontends implemented using ReactJS, and backends implemented using Spring 4.

• modularizing the frontend components
• implementing backend endpoints for the frontends
• setting up CI/CD pipeline and infrastructure for the frontend libraries

The task in this project was to develop a proof-of-concept for a data analytics solution. The solution contains several backends, modelling different approaches for the data analysis, as well as a frontend for comparing the results of the different algorithms and to showcase the user experience of the system.

• setting up the first iteration back-to-front: test data generation, analysis backend, frontend
• developing the ReactJS frontend
• development of the backend
• setting up CI/CD pipeline and infrastructure in AWS

In this project the company has developed an internal tool for Audi. The tool consists of a frontend part, and several backends. I have been hired as a full stack developer
working on both the ReactJS frontend and the Spring Boot backend. As time progressed I have taken over the lead developer, and later the architect roles. The goal of the project was to have a flexible frontend with widgets. Each of the widgets is provided by separate teams and loaded dynamically as per user configuration. The backend services should accommodate the frontend widgets, and provide big data like analytics.

• bootstrapping the front-end and the build pipeline
• developing the ReactJS frontend
• cleaning up old code in the backend, change architecture to accommodate further improvements
• designing the architecture: backend services, database tables
• prototyping widget loading mechanism

As Head of IT my main tasks were for one part technical, on the other hand team leading and coordination. The technical aspects included: laying down the technical direction of the company, implement components, migrate old code to accommodate new structures, maintaining and monitoring of the backend system. On the management side I acted as a bridge between the tech teams and the business teams. I have created
specifications, reviewed the code from the external and internal software developers, and managed the internal software developers.

• reviewing the existing code base, and decide on future direction
• plan the transition of the old code base to new technologies and structures
• migrate old components step by step by carefully balancing re-factoring budget with
  new features
• implement new components along with new features
• design of new features and software components
• coordination between technology and business
• specifications for the external software developers
• code review for the external and internal software developers
• maintenance and monitoring

As Head of IT my main tasks were for one part technical, on the other hand team leading and coordination. The technical aspects included: laying down the technical direction of the company, implement components, migrate old code to accommodate new structures, maintaining and monitoring of the backend system. On the management side I acted as a bridge between the tech teams and the business teams. I have created
specifications, reviewed the code from the external and internal software developers, and managed the internal software developers.

• reviewing the existing code base, and decide on future direction
• plan the transition of the old code base to new technologies and structures
• migrate old components step by step by carefully balancing re-factoring budget with
  new features
• implement new components along with new features
• design of new features and software components
• coordination between technology and business
• specifications for the external software developers
• code review for the external and internal software developers
• maintenance and monitoring

The main project was split in multiple teams, which worked collectively on an Industry 4.0 topic. I was part of the so called Cloud Integration team, which had the task to deploy the created software automatically (CI) on AWS servers. My main focus was getting the software automation in place to make this happen. I also worked on setting up and maintaining a monitoring infrastructure.

• setting up monitoring using Prometheus, to monitor the deployed software
• provision Kubernetes clusters in AWS
• automatically deploy the current software to the cluster
• scripts for managing the Kubernetes cluster
• making changes on the software so that it is monitorable, and deployable

The company has re-structured its technology department to be more flexible, by creating autonomously acting developer teams, which are guided by so called delivery leads. Delivery leads coach their teams, and help them to design their systems. In this capacity I am lead of four teams: Article management, Stock services, Risk management, Payment analytics.

• Coaching the teams, so that they are able improve their designs
• Validating the technological decisions of the teams
• Job interviews
• Deciding on team composition
• People leadership

In 2015 I took over the technical leadership of the Risk management team. This team is concerned with assessing risk our customer put at the company. We employ sophisticated machine learning algorithms and a highly scalable architecture to cope with the high amount of data.

• Architectural decisions for our components
• Technical and architectural vision for the re-factoring of our core components
• Job interviews
• Deciding on team composition
• People leadership

As the company grew bigger I was promoted to a team leader. The size of my team has varied between 6-10 people. My main responsibilities are managing my team and laying down the architectural concepts of our components. Besides that I am taking part in the platform decisions for the whole technology group (which libraries to use, how to solve technical problems, library design). As the other team leads I regularly deploy our live stack, and conduct job interviews for the company.

• Architectural decisions for our components
• Monitoring / operating live servers
• Fixing live issues in the databases and servers
• Resource allocation
• Platform decisions
• Job interviews
• Deciding on team composition
• People leadership

• I joined the company as a back-end Java developer helping in the re-writing of the whole Zalando software ecosystem.
• The shop and its back-end services were written in PHP (based on Magento).
• My main projects were: creating the address normalization / check component, communication interfaces with external systems (payment provider, dunning, gift voucher print system, logistics system).
• In these projects I have developed common libraries, which are still used in our components.

• I was a Java / J2EE developer working in the back-end team of the company.
• Mymain task is to implement test services (Web services) for various payment providers.
• I also create new payment providers and bindings for these.

• I had two main roles in the company.
• I was part of the release management team, and I was a developer in multiple languages.
• As developer I worked on requirements gathering, software design, and implementation of back-end systems.

• As a lecturer I had to teach C programming in the practical classes.
• Additionally I created programming tasks, helped the students in preparing for exams, and the year end programming home work.

• Our group worked on integrating the mobile phone with web technologies.
• In this role I worked mainly on the web application part of the system, but occasionally I had to create phone applications as well.
• Apart from developing applications in my role I had to come
  up with new ideas, which could be researched further and could be patented by the company.

• My tasks was creating utility applications, which enhanced the productivity of other colleagues in the company.
• These applications were mainly Microsoft Office add-ins,
  and other utility scripts.