DevOps Engineer

As a DevOps Engineer at Qureight, you'll be responsible for deploying and securing ourcloud-based data analytics products, ensuring high standards with infrastructure as code methodologies, and implementing robust logging and monitoring systems to adhere to regulated processes. Your role is critical in driving efficient operations and ensuring that our clients can effectively upload, curate, and analyze their complex healthcare data.

Candidates applying for the DevOps Engineer role at Qureight should have at least 2 years of experience in applied DevOps. Essential skills include proficiency in Linux, experience with cloud providers like AWS, and familiarity with infrastructure as code tools like Terraform. Having expert git skills, CI/CD pipeline maintenance experience, and knowledge of Kubernetes are crucial for succeeding in this role.

At Qureight, we value skills and experience over formal qualifications. While a degree can be advantageous, it is not a requirement for the DevOps Engineer position. We encourage candidates with relevant experience and a strong skill base to apply, as we're focused on finding the right fit for our team.

At Qureight, our team culture is collaborative and dynamic. As a DevOps Engineer, you'll work with multidisciplinary teams that foster innovation and encourage independent project management. We believe in making a real difference in healthcare, and everyone’s input is valued as we strive for shared goals within a friendly and motivated environment.

Working as a DevOps Engineer at Qureight comes with numerous benefits, including flexible working hours, a hybrid work policy, and a competitive salary. Additionally, we offer 25 days of annual leave, a contributory pension, private medical insurance, and opportunities for professional development, making it an attractive place to grow your career.

Discuss your experience with AWS, including any specific services you have used such as EC2, S3, or Lambda. Highlight how you've managed costs and utilized AWS features in previous projects. Give examples of how you've ensured compliance and security in your implementations.

Infrastructure as code (IaC) is a practice that allows you to manage infrastructure using code and automation. Explain its significance in terms of repeatability, consistency, and version control. Provide specific examples of tools you've used, like Terraform or CloudFormation, and how they enhanced efficiency in your projects.

Discuss the CI/CD tools you've used and how you've implemented automation in your pipelines. Mention the stages of integration and delivery you've set, how you've ensured code quality through automated testing, and the impact of CI/CD practices on release cycles.

Talk about your experience with monitoring tools like ELK, Prometheus, or Grafana. Provide examples of how you've configured these tools to track application performance and troubleshoot issues. Emphasize the importance of proactive monitoring in a regulated environment.

Provide a specific example of a technical challenge you faced, your approach to solving it, and the outcome. Highlight the tools and strategies you utilized, along with any collaboration with team members that contributed to the solution.

Discuss your methodologies for security in deployments, including automated security testing, reviewing configurations, and collaborating with security teams. Highlight any experience implementing security best practices and tools in your past roles.

Share your practical experience with Kubernetes, including setting up clusters, managing deployments, and troubleshooting issues. Explain how you've leveraged Kubernetes features to improve scaling, availability, and resource management in your applications.

Talk about your experiences working with cross-functional teams, emphasizing communication, collaboration, and the sharing of knowledge. Describe how you align team goals with individual contributions to foster a supportive and productive work environment.

Provide an example of a project where you had to take the initiative and work independently. Discuss the steps you took to plan, execute, and deliver the project, including any challenges you faced and how you overcame them.

Discuss your coding best practices, including documentation, testing, and peer reviews. Emphasize the importance of readability, maintainability, and performance optimization, detailing how these considerations contribute to high-quality code in production environments.