Site Reliability Engineer

What we are ideally looking for in the next member of the team:

• Humble and curious attitude: you are keen to understand how things work and improve them by continuous iteration.
• Clear communicator, confident, self-sufficient, focused and determined, even so, You value, listen and weigh your teammates' opinion.
• Strong problem solving, troubleshooting and system analysis mindset and resolution.
• Know when to escalate or ask for help vs having to own and resolve the issue in isolation.
• Knowledge of technology architecture for large-scale distributed systems is a plus.

• Linux (debian/ubuntu): workstations and server are using linux.
• Cloud: AWS (preferred), OCI, GCP or Azure are a plus.
• Container management: docker, kubernetes but also PaaS-driven: ECS, EKS, GKE, AKS.
• Monitoring and logging tools like New Relic, Datadog, Prometheus, ELK Elasticsearch stack.
• Advanced working experience with git source repository
• Programming languages: at least one out of shell/bash, python, groovy.
• Automation tooling, both infrastructure and configuration based, like terraform/ansible/packer etc.
• Continuous integration and delivery ecosystem and tools: Jenkins (preferred) or Gitlab/CircleCI, ArgoCD/Flux, etc.

• We value attitude and your thinking process over the list of skills and tools in your belt.
• We are in a path of standardization, therefore we are looking into individuals that are keen to simplify and dig into complex applications.
• Done is better than perfect: we understand the value of getting things done in agreed timelines and iterate over their improvements.
• Simple is better than magical: you will contribute to create easy to use solutions that are more likely to be adopted by stakeholders that can understand their purpose and collaborate to improve them.
• Visibility is key: we value data-driven decisions and business-driven metrics. You will be key to implementing observability tooling used across the engineering function.
• Automation everywhere it is reasonable: it's ok to have manual and documented tasks if there is a VERY good reason.
• Everything should be reproducible and repeatable: we like boring solutions because they always work.
• 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.

English fluency is required (both written and spoken), Italian fluency is a plus.

We offer flexible working with an average of 3 days at the office and 2 days working from home.