QA Engineer (Junior-Friendly) — Cloud Security Platform - Upwind

QA Engineer (Junior-Friendly) — Cloud Security Platform
Java · Selenide · AWS / Azure / GCP · Kubernetes · Terraform
Start here, and go deep
Upwind is a cloud security platform. Companies connect their AWS, Azure and GCP environments to us, and we tell them what's dangerous — vulnerable container images, misconfigured permissions, exposed identities, live attacks in progress.
It's a big product, and nobody arrives knowing it. You'll learn it with us — the cloud, the Kubernetes, the security domain, the automation. That's the deal: you bring the curiosity and the fundamentals, we teach you the rest.
What you'll be working on
Testing features by hand
Learn a feature area properly, then write test plans for it — onboarding flows, dashboards, scanners, integrations
Turn plans into clear, prioritized test cases with real steps and expected results
Check new features against what product actually asked for, and verify fixes before they ship
Run regression rounds before releases
Writing automation
Write WebUI tests in Java + Selenide, in a framework that already exists — you'll be adding to it and learning the patterns, not building from zero
Gradually automate the areas you've been testing manually, so your time moves to more interesting work
Investigate failing tests: is it a real bug, or is the test unstable? Learn to tell the difference fast
Getting hands-on with cloud
Set up your own test environments: connect AWS accounts using Terraform and CloudFormation, onboard Azure and GCP projects
Deploy our sensors onto Kubernetes clusters and Linux servers
Generate QA workloads and check the platform reacts the way it should
Compare what the UI shows against the real underlying data — this is where the most interesting bugs hide
Reporting what you find
Write bug reports engineers can pick up immediately: steps, expected vs actual, impact, environment, and evidence
Learn to spot when five bugs are really one bug with one cause
What we need from you
Some commercial QA experience — internship, junior role, or a year or two of manual testing
Basic Java — you've written and debugged code, and you can read someone else's without panic. You don't need to be a developer.
Some exposure to test automation. If you've written Selenium or Selenide tests in a course or a small project, that counts.
Test design fundamentals: equivalence classes, boundary values, negative cases — the ISTQB material, understood rather than memorized
Curiosity about how things work under the hood: you've opened browser devtools and looked at what requests a page makes
Basic Linux comfort: you can SSH into a machine and read a log file
Git and Jira
English good enough to work in a distributed team every day
Genuinely optional
Cloud experience of any kind · Kubernetes · Terraform · a security course or CTF you did for fun · SQL · CI/CD
If you have none of these, that's fine. If you have one, tell us about it.
What we care about more than your CV
You want to know why. "It's broken" is where you start, not where you stop.
You'll set things up yourself rather than waiting for someone to hand you an environment.
You write clearly. A vague bug report costs the team a day; a good one saves it.
You want to learn cloud security properly. Not eventually. Now.
What you'll walk away with
Java automation experience in a real production suite. Hands-on AWS, Azure, GCP, Kubernetes and Terraform. A working understanding of how cloud attacks and defenses actually operate.
That combination takes most people years to assemble. You'll build it here, with people who'll teach you.
Bring the curiosity. Apply.