Why this role is worth your next few years
Most QA jobs teach you one product and one process. You learn the checklist, and two years later the checklist is still all you know.
This one is different. You'll work across cloud security on AWS, Azure and GCP — deploying Kubernetes clusters, running infrastructure-as-code, testing threat detection, and writing the Java automation that holds it together. That isn't one skill. It's the stack the entire market is hiring for, learned properly, alongside people who will actually teach you.
You'll start with support and a defined feature area. Within a few months you'll be running that area yourself.
What you'll be doing
Testing and test design
Own test plans for your feature areas — onboarding flows, dashboards, scanners, integrations — and turn them into prioritized test cases with real exit criteria
Run feature QA cycles: validate acceptance criteria against the PRD, verify each requirement, sign off before release
Run regression sweeps and verify fixes before they move forward
Automation
Write and maintain WebUI tests in Java + Selenide, extending a framework that's already there — you're not starting from a blank file, but you will be shaping it
Automate the areas you test by hand, so your manual time goes to exploratory and new-feature work
Keep the suite healthy: investigate failures, separate real defects from flakiness, and fix the flaky ones properly
Start contributing to how we test, not just what we test — stable selectors, reusable helpers, better test data
Hands-on cloud work
Set up your own environments: onboard AWS accounts via Terraform and CloudFormation, Azure tenants, GCP projects, and verify off-boarding actually cleans up
Deploy our sensors on EKS with Helm and on EC2 hosts
Generate QA workloads and confirm the platform detects and displays them correctly
Cross-check the UI against the underlying data — where the most interesting bugs live
Working with people
Daily contact with backend and frontend engineers, PMs and designers inside your feature squad
Keep test plans, cases and results documented in Jira and Confluence so anyone can pick up where you left off
What you need to bring
Commercial QA experience covering both manual and automated testing
Java — enough to read, extend and debug an existing test codebase confidently
Hands-on UI automation you've done on a real project (Selenide, Selenium, or similar — transferable experience is fine)
Test design fundamentals, and the judgment to know what not to test
REST APIs and browser devtools: enough to tell whether a bug is frontend, backend, or data
Working knowledge of at least one major cloud provider — console, IAM basics, onboarding flows
Basic Linux and CLI: SSH, systemctl, reading logs
Git and Jira
English for daily work with a distributed team
Nice to have — not required
Kubernetes basics · Terraform or CloudFormation · interest in cybersecurity (CVEs, CSPM, IAM) · SQL or OpenSearch · CI/CD · regulated environments like FedRAMP or SOC 2
What actually matters to us
Curiosity about why something broke. The best bugs on our board come with a diagnosis attached.
Ownership. You set up your own environments, chase the answer, and follow the fix through to verification.
Precision in writing. A vague bug report costs the team a day; a good one saves it.
Willingness to learn fast. You don't need to arrive a cloud security expert. You need to want to become one.
What you get out of it
Real mentorship from engineers who know this domain cold. Depth in cloud security across all three major providers, hands-on Kubernetes and infrastructure-as-code, and a mature Java automation stack.
You'll absorb in months what most people spend years collecting — and come out the other side as an engineer nobody wants to lose.
Curious? Apply.
