Position: Site Reliability Engineer
Company: GeeksForLess
Experience required: 2y
English level: intermediate

Requirements:
- Experience with  and  Swarm.
- Understanding of the GitOps concept
- Experience with  as we have started the process to migrate applications from our on-premise data centres to the cloud()
- Experience with (setup and configuration with  agents, backup and restore, setup CI/CD pipelines using file)
- Experience with Github Actions
- Experience with at least one of the following programming languages: , , .
- Since most of the company's applications are developed in , experience with packaging applications using Gradle or  is required.
- English: Intermediate

Oning projects:

- Consolidation of our CI/CD infrastructure:
Currently, our CI/CD infrastructure consists of at least 3 swarm clusters( using  swarm to spin agents).
We want to consolidate it and improve the infrastructure in terms of documentation, backup and restore procedures, disaster recovery, etc

- Migration of legacy  apps to (swarm)
there's a queue of more than 100 apps that require to be migrated to the latest CI/CD practices, our plan is to ized those applications and implement CI/CD pipelines for build, test and deployment using a combination of Github actions(for the test, build and push images to the registry) and  to trigger deployment jobs using the GitOps approach

- Implementation of a Secret management service
We're currently relying on  swarm secrets to store applications sensitive data and SSL certificates, however, even useful is not a global solution that developers and the SRE team can use and the process of rotating secrets involves risk due to manual intervention.
We would like to implement a solution such as Vault(https://www.vaultproject.io/) or Knox(https://github.com/pinterest/knox)