About

Microsoft - Senior Service (DevOps) Engineer

Avast - Senior Software (DevOps) Engineer

July 2018 - June 2019
I joined the Avast Secure Browser team to help them:

• Codify their Cloud Infrastructure (hosted on AWS) according to the modern, DevOps best practice using Terraform;
• re-think about their applications and convert them in cloud-native apps using modern technologies such as Docker and Kubernetes for the orchestration;
• implement CI/CD to their flow
• improve their agile using my Scrum Master skills developed in previous roles
• improve the visibility of their stack by building a centralised Monitoring and Logging system using modern opensource technologies such as Grafana, Prometheus, Kibana, Logstash, etc.

During my time at Avast, I also developed a helper tool for AWS Auto Scaling Groups called Sigmund, I also wrote a blog post about it that can be found here.

Crowdcube - Senior DevOps Engineer

September 2016 - June 2018
As a DevOps engineer at Crowdcube, I was responsible for the Web security, platform, and infrastructure hosted on Amazon Web Services (AWS).
During my time at Crowdcube, I:

• Moved the Website assets and content on an S3 bucket, living behind a CDN greatly reducing response time and outages during deployments;
• Moved Applications from using classic ELBs to a single ALB;
• Automated the deployment process, especially registration and deregistration of the servers from the load balancers;
• Designed and provisioned a Management VPC with a Jenkins CI server;
• Added test-kitchen and RSpec tests to the majority of the Ansible roles;
• Helped to deliver a development/test environment, in kubernetes, which creates a dedicated ephemeral environment for developers every time they open a Github Pull Request;
• Got promoted to Senior DevOps Engineer after 9 months;
• Containerised all our production services applying Docker best practices;
• Wrote a tool for developers, in Node.JS, to deploy by typing a command on slack;
• Mentored a DevOps engineer that joined our team teaching him the values and good practices of our job, matching the business needs;
• Started a process of Continuous Integration and Delivery managing to automatically deploy every master build to our staging environment.

Working at Crowdcube was very challenging for many reasons:

• I was the only DevOps engineer for 10+ months;
• As a startup, timelines tend to be very tight, therefore I found myself working at a very high pace;
• I had to learn how to make the best decision without damaging the business values and, of course, costing.

Challenges can be scary, sometimes, but I promptly learned how to deal with them delivering exactly what the company needed and receiving acknowledgement of the good work done.

Comic Relief - WebOps Engineer

February 2015 - August 2016
I started at Comic Relief as a Junior WebOps engineer and I had the chance to manage the web infrastructure which hosts their main company sites such as comicrelief.com, rednoseday.com and sportrelief.com. During my time there, I've learned more about system administration, configuration management and troubleshooting; I also took part of a migration of some of their application to AWS and a re-design of our tool system. All our systems were Linux’s Debian based.
I was part of Red Nose Day campaign 2015 and I helped to deliver a fully scalable and highly available infrastructure for the 2016 Sport Relief campaign.
Right after the SR campaign, I got promoted to WebOps engineer and started to own part of the infrastructure and of the tools used on our stack.
I developed a Docker-based development environment for our developers.
The main tools used were:

• Chef
• Ansible
• Docker
• Terraform
• Jenkins
• Consul
• AWS (EC2, RDS, Elastic Cache, Route 53, S3)
• Vagrant
• Test Kitchen
• Ruby
• Varnish

Workshare - Junior DevOps Engineer (Internship)

October 2014

I was assigned to the DevOps department. As an intern, I learned how to deal with operational problems on a daily basis and how to provide technical assistance.
In this role I:

• Used Ruby for small scripts and Chef Maintenance;
• Worked in a Kanban environment;
• Updated a Git repository using Unix terminal;
• Added some Unit Tests to Chef recipes; and
• Wrote and updated a microservices template for Chef