For the first 7 months I was working as one of the two back-end developers for the billing team. This team is responsible for managing the transaction system and enabling the features customers payed for. I was developing and improving the related web services (java and spring) to collect payments using Adyen as payment service provider for the web and mobile-web and Google and Apple for the apps. Due to this I got to know them and their flows pretty well; especially limitations and not-documented weird behaviors. After this months I was the only responsible for the back-end in this team because the other developer was moved to another project.Few months later the structure changed and I became one of the two back-end developers in charge of maintaining and developing the entire system while the new one was built. Because of that I got to dig deeper in older technologies and also to get to know a bit of Angular 4 in order to provide possible support also on front-end side if/when needed.Now I work with another back-end developer and a DB developer on a temporary side project that is the one with the highest priority, getting to improve my knowledge about technologies like AWS, Spinnaker, RabbitMQ and some others cloud related.In almost all of the systems I've been working on we used 3 levels of automatic testing in order to provide stability and consistency to the system: junit tests, integration tests and cucumber tests.

I was working as a back-end developer on the Zurich project. I developed in Java SE/EE and Gosu to implement on Guidewire (software made to support insurance operations) all the functionality needed by Zurich. During this months I was working with Weblogic and Websphere technology as well, getting trained to manage our services and developing and testing environments. After working with web services and JMS, I was then working on the back-end part focused on the migration of DBs from the old system to the new one.We worked using the Agile approach in a field where every other company we worked with used the waterfall approach. Even if that maked it harder to have a good scheduling of the user stories, it was really useful to learn to adapt and to overcome difficulties given from the two approach coming to work together.