Job Description
At Cloudera, we empower people to transform complex data into clear and actionable insights. With as much data under management as the hyperscalers, we’re the preferred data partner for the top companies in almost every industry. Powered by the relentless innovation of the open source community, Cloudera advances digital transformation for the world’s largest enterprises.
Team Overview
Ready to take cloud innovation to the next level? Join Cloudera’s Anywhere Cloud team and help deliver a true “build your own pipeline, bring your own engine” experience. enabling data and AI workloads to run anywhere, without friction or vendor lock-in.
We take the best of the public cloud- cost efficiency, scalability, elasticity, and agility and extend it to wherever data lives: public clouds, private data centers, and even the edge. Powered by Kubernetes, our hybrid architecture separates compute and storage, giving customers maximum flexibility and optimized infrastructure usage.
The Role
As a Software Engineer in Test – DevOps & Tool development, you will play a critical role in automating the validation of our deployment pipelines and Kubernetes infrastructure. You will bridge the gap between software development and IT operations, working closely with developers and release engineers to ensure every code merge is thoroughly tested before it reaches production. The role also requires test automation of AWC features as an included responsibility
Key Responsibilities
- CI/CD Pipeline Test Automation: Develop and maintain automated test suites integrated directly into Harness CI/CD pipelines to validate pull requests (PRs) and protect the main branch in our trunk-based development model.
- Kubernetes Deployment Validation: Write system and integration tests to verify the successful installation, configuration, and health of AWC foundational services deployed via Helm charts to Taikun Kubernetes Service (TKS) clusters.
- Ephemeral & Upgrade Testing: Automate the provisioning and teardown of ephemeral test environments for PR-level testing. Execute automated upgrade and rollback tests on persistent long-running development clusters to ensure backward compatibility.
- GitOps & Continuous Delivery Verification: Validate the end-to-end continuous delivery flow, ensuring that components managed by FluxCD properly reconcile with the Git repository state and that Helm charts are correctly published to internal OCI registries.
- Quality Monitoring: Track and report on test cycle stability. Assist in automating Jira ticket status updates based on CI/CD pipeline progress to improve release visibility.
Requirements
- Experience: 2–4 years of professional experience as a Software Engineer in Test (SDET), DevOps Engineer, or Quality Engineer focusing on deployment automation and infrastructure testing.
- Kubernetes Fundamentals: Solid, hands-on understanding of Kubernetes core concepts (Pods, Deployments, Services, ConfigMaps, Secrets, Namespaces) and command-line operations (kubectl).
- DevOps & CI/CD Tooling: Experience with modern continuous integration and delivery tools (e.g., Harness, Jenkins, GitLab CI). Familiarity with GitOps principles and tools like FluxCD or ArgoCD is highly preferred.
- Helm & Containerization: Practical experience creating, modifying, and testing Kubernetes deployments using Helm charts, and working with Docker containers and OCI registries.
- Programming Languages: Strong coding proficiency in Python, Go (Golang), or Java for building automated test scripts and interacting with REST APIs.
- Modern Workflows: Proficiency with Git, pull request workflows, and collaborative code reviews.
- Platform Mindset: A collaborative mindset with an eagerness to learn about cloud-native infrastructure, distributed systems, and declarative configuration management.
You may also have:
- Kubernetes Operators: Experience building operators or controllers using controller-runtime/kubebuilder. Understanding of reconciliation loops and CRD design.
- Helm: Experience authoring and maintaining Helm charts for complex multi-service deployments.
- Auth/Security: Familiarity with OIDC, SAML, mTLS, or credential-brokering patterns (SigV4, token exchange).
- Cloud Provider APIs: Hands-on experience with AWS or GCP APIs (IAM, S3, networking).
- Build Systems: Comfort with Bazel, Make, or similar build tooling in a monorepo or multi-repo setup.
- Observability: Experience instrumenting services with structured logging (slog), metrics, or distributed tracing.
