Sr. Customer Service Executive - Customer Interaction Suite Milano

Sr. Customer Service Executive - Customer Interaction Suite
Milano
Lombardia, Milano

Job Description The role is responsible for writing and maintaining automation scripts and related CI/CD tools. This is an operational role that may seek appropriate level of guidance and advice to ensure delivery of quality outcomes. Responsibilities Be part of the central DevOps team, reporting to its lead Help the team to give guidelines and blueprint on DevOps lifecycle Proactively identify and solve issues in platforms together with the rest of the infrastructure and engineering teams. In consultation with Information Security, implement best practices and compliance. Requirements At least 2 years of working experience in the role Understand how a distributed application works, constraints and limitations Experience with Linux servers and at least one public cloud Experience with containerization technologies like Docker and Kubernetes Experience with Git Coding and scripting experience (python, shell/bash) Experience in creating/refactoring deployment pipelines (we use Jenkins and GitHub Actions) Experience in creating/refactoring Ansible scripts Fluent in English Desired Skill sets Experience with automation tooling, both infrastructure and configuration based: terraform/ansible/packer etc. Experience with web servers and load balancing solutions: apache, haproxy, nginx Databases and stores: mysql/postgres/redis etc. Distributed services like brokers and queues (kafka, rabbitmq) Understanding Java code bases and basic knowledge of Maven Knowledge of WildFly Application Server Knowledge of application life-cycle maintenance Things we care about We value attitude and your thinking process over the list of skills and tools in your belt Automation everywhere it is reasonable Infrastructure as code: configuration files, infrastructure deployments should be version controlled and driving automated deployments Security: is part of the process, it's a journey and it's definitely an engineering problem Well written documentation: if it's not documented it doesn't exist J-18808-Ljbffr