QA Automation/Devops Engineer for MKE4K

Key Responsibilities

Testing Strategy & Leadership

• Contribute to driving the overall QA strategy for Kubernetes and cloud-native environments, aligning quality goals with business objectives and release deadlines.

• Evaluate and champion best-in-class testing best practices and frameworks for distributed systems.

• Lead risk analysis and test planning for large-scale, multi-cloud infrastructure and container orchestration.
  

Architecting Test Systems

• Architect test frameworks and infrastructure for validating microservices and infrastructure components in multi-cluster and hybrid-cloud environments.

• Oversee the design of complex test scenarios simulating production-like workloads, resource scaling, failure injection, and recovery across distributed clusters.

Automation & Scalability

• Spearhead the development of scalable and maintainable test automation integrated with CI/CD (Jenkins, GitHub Actions, etc.).

• Leverage Kubernetes APIs, Helm, and service mesh tools to build comprehensive automation coverage, including system health, failover behavior, and network resilience.

• Promote test infrastructure-as-code and drive IaC forward on the team making sure the infrastructure code is repeatable, extensible and reliable.
  

Mentorship & Technical Influence

• Mentor QA engineers and developers in advanced testing techniques such as: risk-based testing, chaos engineering, performance and load testing etc.

• Serve as the QA authority in design reviews, production readiness assessments, and incident retrospectives(escaped defects).

• Collaborate with and devops engineers to refine monitoring, alerting, and debugging strategies for testing automation being run in CI/CD.

Quality Advocacy & Continuous Improvement

• Establish quality gates, release readiness metrics, and data driven feedback loops to ensure released software is production quality.

• Drive initiatives to integrate performance, security, and chaos testing into the development lifecycle.

• Advocate for a culture of quality across teams and influence architecture decisions with testing in mind.