As a QA Engineer – Kubernetes Platform Validation, you will be a peer in the engineering pod that builds and operates Kubernetes-based cloud platforms across Azure (Local) and GCP (FedRAMP). You will drive end-to-end solution validation, design chaos tests, and ensure reliability, security, and scalability.

About the Company

BETSOL (BETSOL.com) is a global IT services and AI-powered enterprise engineering company. With over 17 countries of operation, BETSOL accelerates cloud transformation for enterprises by delivering AI-native and cloud-native solutions. The company holds several engineering patents and maintains an industry-leading Net Promoter Score (NPS) that is 2x the industry average. BETSOL also owns the open-source backup and recovery product line, Zmanda, which delivers up to 50% savings in total cost of ownership (TCO) and best-in-class performance. Known for its employee-centric culture, BETSOL has offices in Broomfield, Colorado (USA), Bangalore, and Belagavi (India). Their Global IT Services builds and supports end-to-end enterprise solutions, reducing time-to-market for customers.

Role Overview

As a QA Engineer – Kubernetes Platform Validation (Azure Local & GCP FedRAMP) , you will be a core member of the same engineering pod that designs, builds, and operates Kubernetes-based cloud platforms across Azure (Azure Local, formerly Azure Stack HCI) and Google Cloud Platform (GCP) FedRAMP-authorized deployments. Unlike a traditional downstream QA role, you will work as a peer alongside DevOps/DevSecOps engineers from day one. Your primary focus is end-to-end solution validation of these two platforms in parallel — covering everything from initial deployment through Day-2 operations, upgrades, and decommissioning. You will design and execute tests across the full spectrum of 'ilities' (reliability, availability, scalability, security, observability, performance, recoverability, upgradability), deliberately break systems to prove resilience, and read Terraform/Ansible/Helm and observability data fluently to troubleshoot from the platform down to the code level.

Key Responsibilities

• Platform Validation: Drive end-to-end validation for two Kubernetes-based platforms simultaneously — Azure Local (Microsoft's hybrid on-prem stack) and the FedRAMP-authorized GCP deployment. Validate deployment, Day-2 ops, upgrades, and decommission. Design and document solution-level test cases in Given/When/Then style, ensuring readability by engineering, product management, SRE, and operations.
• Kubernetes & Cloud Platform Testing: Perform hands-on testing across kubectl, Helm, operators, CRDs, PVCs, StatefulSets, ArgoCD/Flux, network policies, and node affinity. Validate AKS and GKE environments including Azure Monitor / GCP Cloud Monitoring, Key Vault / Cloud KMS, and Managed Identities / Workload Identity. Comfort learning a new hybrid on-prem topology (Azure Local) is required.
• Root Cause & Regression Testing: Read Terraform, Ansible, and Helm charts fluently to understand what is deployed and why. Reproduce customer or production incidents in the lab, trace the path from IaC through Kubernetes to cloud resources to root cause alongside engineering, and author regression tests to prevent recurrence.
• Resilience & Chaos Testing: Deliberately break and recover single nodes, pods, network paths, and storage (S2D pool degrade, PVC unbound, VPN tunnel drop) to verify SLOs hold under failure. Use LitmusChaos, Chaos Mesh, or equivalent tooling.
• Observability-First Testing: Verify system behavior by reading metrics, logs, and traces (Prometheus, Grafana, Loki, OpenTelemetry, Alertmanager) rather than solely asserting on HTTP status codes.
• Security & FedRAMP-Aware Testing: Test TLS termination, cert rotation, secret management (Cloud KMS / Secret Manager), RBAC boundaries, and container image scanning (Wiz, Prisma, or equivalent) on the GCP deployment. Verify audit logging into GCP Cloud Logging and generate evidence aligned to FedRAMP Moderate/High control families (AC, AU, SC, SI, IA). Apply the same controls on the Azure Local side wherever they cross-map.
• Collaboration: Pair with engineers on design reviews, feature-freeze planning, and Day-2 playbooks as a peer — catching quality issues before code is written, not after. Communicate clearly and be accountable.

Tech Stack

• Container Orchestration: Kubernetes (kubectl, Helm, operators, CRDs, PVCs, StatefulSets, ArgoCD, Flux, network policies, node affinity)
• Cloud Platforms: Azure (AKS, Azure Local, Azure Stack HCI, Azure Monitor, Key Vault, Managed Identities), GCP (GKE, GCP Cloud Monitoring, Cloud KMS, Workload Identity, Cloud Logging)
• Infrastructure as Code (IaC): Terraform, Ansible, Helm
• Observability: Prometheus, Grafana, Loki, OpenTelemetry, Alertmanager
• Chaos Engineering: LitmusChaos, Chaos Mesh
• Security & Compliance: TLS, cert rotation, Cloud KMS, Secret Manager, RBAC, container image scanning (Wiz, Prisma), FedRAMP control families (AC, AU, SC, SI, IA)
• Test Management: Jira (Test issue type), Zephyr (nice to have)
• Distributed Systems (nice to have): Kafka, Redis, MariaDB/Galera, MinIO (S3-compatible object storage)

5+ years of QA / SDET experience, including at least 2 years hands-on with Kubernetes and 1+ year in a major public cloud (Azure or GCP).

Mandatory Skills:

• Hands-on Kubernetes: kubectl, Helm, operators, CRDs, PVCs, StatefulSets, ArgoCD or Flux, network policies, node affinity.
• Azure and GCP fluency: AKS and GKE, Azure Monitor / GCP Cloud Monitoring, Key Vault / Cloud KMS, Managed Identities / Workload Identity.
• Ability to read Terraform, Ansible, and Helm charts to understand deployed infrastructure and trace issues to root cause.
• Test design across the full 'ilities' spectrum in Given/When/Then style.
• Observability literacy: Prometheus, Grafana, Loki, OpenTelemetry, Alertmanager.
• Security and FedRAMP-aware testing: TLS/cert rotation, secret management, RBAC, container image scanning, audit-log verification, control-family evidence generation (AC, AU, SC, SI, IA).

Good to Have:

• Zephyr or native Jira Test issuetype experience.
• LitmusChaos, Chaos Mesh, or equivalent chaos-engineering experience.
• Prior FedRAMP work or experience in similar regulated environments (SOC 2, HIPAA, PCI DSS, DISA STIG).
• Experience with distributed data services: Kafka, Redis, MariaDB/Galera, MinIO or other S3-compatible object storage.

Comprehensive benefits and opportunities as part of an employee-centric organization. (Mentioned in description)