- email: [email protected]
- phone number: +54 11 6694 5547
- Microservices big fan: Using docker and docker-compose since 2017. Kubernetes and helm lover.
- Coding skills on golang, groovy and python.
- I believe that automatization and git are a must when working in an engineering team: Making manual changes will probably lead the team to break things and don't understand why.
- I trust in metrics, so, I think that monitoring and a good logging will improve response times, avoid downtimes, and prevent future head pains.
- I like automating infrastructure creation, configuration and maintaining with terraform.
- I'm curious about new technologies in general and like to learn new languages and tools in order to make life easier.
- Especially curious about Linux and open source since I was a child.
- I like to establish good relationships with my co-workers, I believe that work is an important part of my life, and I made good friends in my career. I'm a empathic, responsible person.
- I like challenges, and I don't have a problem assuming risks.
Working on improving the company's processes, and its way to deploy to production and to ensure quality and reducing the complexity and the gap for downtimes. I'm taking tasks of mentorship for less experienced colleagues. I'm also planning new initiatives, creating the documents and guidelines needed for convince the management to execute them, plan the needed resources and time for the execution, and execute following the defined guidelines. We manage 2 big products and we maintain a Kubernetes cluster for each product per environment. For some microservices we use lambda functions. I worked on the re-design of the network architecture for incoming requests, using AWS API-Gateway to support both, EKS pods and lambda functions, using only 1 entry point. I also led the IaC adoption for tools like Datadog and LaunchDarkly. I participated as a main engineer in the migration from Harness to Github Actions, we moved all the custom pipelines that we had to an standarized reusable workflows model. Leaving only 3 use cases and standarizing the quality and the reliability of the components across the organization.
In this opportunity, I took a challenge by moving to Amsterdam, Netherlands. In this period I worked on improving the company's infrastructure which is running in AWS ECS, solving incidents, and creating terraform modules to deploy our infrastructure components. Also, I contributed to the SDLC process, using my experience to bring the best practices to the engineering teams when we build software. I worked on moving all the static assets to an S3 implementation, creating the pipeline, and designing the architecture, using Cloudflare as CDN, loading times were 10x faster with this new architecture. I also contributed to implementing IaC for feature flags, using Split.io as a feature-flags provider. This included some PRs to the split.io terraform provider, which is open source.
As the company continued growing, we founded a team called developer productivity, we're in charge of the tooling needed to get the software to build and deploy applications in the cloud. We tackled a lot of compliance and security issues, trying to not frustrate developers across the company, by creating automation and tools for making those expensive changes transparent for development teams. Also, the team has a lot of new co-workers, so at this stage, I'm mentoring them and contributing to their career development in the company.
Managing to build infrastructure. We contribute developers teams to make their pipelines and their development tooling. We use Jenkins, SonarQube, Nexus Repository, NexusIQ, Vault, and a few more technologies to reach our goals. We're constantly researching new technologies to improve teams' productivity. We monitor our infra with New Relic and our log collector is Sumologic. We use Amazon Web Services as our cloud provider. And we deploy our tools to a Kubernetes cluster, using Helm. I am the first engineer in a team of 5 people and it's kept growing.
I started on the SRE team, managing instances of patching and infrastructure management. Then I moved to the Engineering Services team, working in the build process and tooling.
I was managing the company networking, we used Mikrotik as the principal networking brand. I was in charge of the entire network. I managed high-scale projects (around 40000 bare metal servers distributed in the whole country) using SaltStack, and monitoring it with Icinga2. We also had a mid-scale infrastructure running in Azure.
I was doing pen tests and designed their remediations. I did around 10 pen tests and all were successful, and then we remediated those vulnerabilities.
- Spanish (native).
- English (advanced).
- Amateur football and tennis player.
- Amateur skateboarder and snowboarder.
- Really amateur guitar player.
- Learning about photography with drones and mirrorless cameras.