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.

ResponsibilitiesBe part of the central DevOps team, reporting to its leadHelp the team to give guidelines and blueprint on DevOps lifecycleProactively 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. RequirementsAt least 2 years of working experience in the roleUnderstand how a distributed application works, constraints and limitationsExperience with Linux servers and at least one public cloudExperience with containerization technologies like Docker and KubernetesExperience with GitCoding and scripting experience (python, shell/bash)Experience in creating/refactoring deployment pipelines (we use Jenkins and GitHub Actions)Experience in creating/refactoring Ansible scriptsFluent in EnglishDesired Skill setsExperience with automation tooling, both infrastructure and configuration based: terraform/ansible/packer etc. Experience with web servers and load balancing solutions: apache, haproxy, nginxDatabases and stores: mysql/postgres/redis etc. Distributed services like brokers and queues (kafka, rabbitmq)Understanding Java code bases and basic knowledge of MavenKnowledge of WildFly Application ServerKnowledge of application life-cycle maintenanceThings we care aboutWe value attitude and your thinking process over the list of skills and tools in your beltAutomation everywhere it is reasonableInfrastructure as code: configuration files, infrastructure deployments should be version controlled and driving automated deploymentsSecurity: is part of the process, it's a journey and it's definitely an engineering problemWell written documentation: if it's not documented it doesn't exist

#J-18808-Ljbffr