Senior DevOps Engineer - English Required

As a Senior DevOps Engineer at DaCodes, you will design, implement, and maintain infrastructure as code, streamline coding to deployment processes, and collaborate with development teams to enhance application performance. Additionally, you'll be involved in monitoring system performance, troubleshooting issues, ensuring security compliance, and maintaining CI/CD pipelines, all while supporting both cloud and on-premises environments.

To qualify for the Senior DevOps Engineer position at DaCodes, you should have a Bachelor's degree in Computer Science, Engineering, or a related field. Proficiency in Linux administration, GCP, AWS, Docker, Terraform, and scripting languages is essential. Previous experience with CI/CD practices and monitoring tools like NewRelic will greatly benefit candidates.

DaCodes is committed to the growth of its employees. As a Senior DevOps Engineer, you will have access to courses and certifications, participate in meetups with industry experts, and engage in virtual networking events. This focus on continuous learning ensures you stay ahead in the rapidly changing tech landscape.

At DaCodes, you'll enjoy a supportive and inclusive work environment. You will have the flexibility of remote work options and a Monday to Friday schedule. We prioritize legal benefits applicable to Mexico, and our company culture is recognized as a Great Place to Work, ensuring that every team member feels valued and engaged.

As a Senior DevOps Engineer at DaCodes, you will engage with a variety of cutting-edge technologies. Key tools include Git, Github, Jenkins, Docker, Terraform, and cloud services like AWS and GCP. You will also work with databases like MariaDB and ElasticSearch, enhancing your expertise in both development and operational environments.

When asked about infrastructure as code, highlight your proficiency in tools like Terraform or CloudFormation and discuss specific projects where you designed or managed infrastructure using code, emphasizing automation and consistency in environment setups.

Discuss your familiarity with security best practices, compliance standards, and tools you’ve used for vulnerability scanning and monitoring. Share examples of how you integrated security into CI/CD pipelines and your approach to risk management.

Be specific about the CI/CD tools you've worked with, such as Jenkins or GitLab CI. Explain how these tools have helped automate deployment processes, improved collaboration among teams, and led to faster, more reliable releases.

Share your experiences managing on-call responsibilities, including how you prioritize tasks during incidents and the steps you take to resolve issues. Highlight your communication skills and ability to stay calm under pressure.

Provide a detailed account of a specific situation where you identified performance bottlenecks. Discuss the approach you took to analyze metrics, implement changes, and the measurable outcomes of those optimizations.

Talk about your step-by-step process for deploying applications, covering aspects like testing, rollback procedures, monitoring post-deployment, and how you ensure minimal downtime or impact on users during the deployment process.

Provide an example of a specific task you automated, detailing the tools used and the resulting time or resource savings. Discuss the challenges faced and how automation improved efficiency and reliability in your workflow.

Express your commitment to continuous learning through channels such as online courses, webinars, tech blogs, and engaging with community forums. Mention specific technologies or frameworks you’re currently exploring to enhance your skills.

Discuss the containerization tools you've used, such as Docker, and your experience with orchestration platforms like Kubernetes. Provide examples where you've implemented these technologies to improve application deployment and scalability.

Highlight the importance of communication and teamwork in the DevOps process. Share strategies you use to foster collaboration, such as regular check-ins, shared documentation, and encouraging feedback loops to bridge the gap between development and operations.