Jobs selenium

Turnitin is looking for an experienced Senior Software Quality Engineer to join our Integrations team. This role is ideal for a highly skilled quality professional who is passionate about building reliable, scalable, and maintainable test solutions while also bringing strong exploratory and risk-based testing skills to complex product integrations.

In this hands-on senior role, you will help ensure the quality, reliability, and stability of Turnitin’s integrations across learning platforms, third-party platforms, APIs, and customer-facing workflows. You will collaborate closely with engineers, tech leads, product managers, and other stakeholders to define test strategies, improve automated coverage, strengthen automated testing and reporting within CI/CD pipelines, and support confident software releases.

Responsibilities

• Collaborate closely with engineers, tech leads, product managers, and other stakeholders to deliver high-quality products and services.
• Develop and execute comprehensive test strategies, test plans, and test cases for integration features, APIs, UI workflows, and customer-facing journeys.
• Design, develop, and maintain robust automated end-to-end tests within the existing Java/Selenium automation stack, while evaluating and introducing modern automation tools and approaches where appropriate.
• Apply strong programming skills, including object-oriented programming concepts and design patterns, to create maintainable automated test code and contribute to code reviews for automated tests and quality-related changes.
• Perform manual, exploratory, regression, smoke, and risk-based testing across complex product and platform workflows.
• Conduct API and web service testing and integrate automated tests effectively into CI/CD pipelines.
• Investigate automated test failures, flaky tests, production issues, and integration defects, providing clear root-cause analysis and actionable recommendations.
• Generate, maintain, and improve test reports, dashboards, and quality metrics to support engineering and release decision-making.
• Participate in the assessment and adoption of emerging automation tools, including modern browser automation frameworks and AI-assisted engineering tools.
• Review requirements, acceptance criteria, technical designs, and user stories to identify risks and quality gaps early in the development process.
• Mentor and support other quality engineers, sharing knowledge and helping improve automation, testing practices, and overall quality capability within the team.

• Communicate effectively across teams and stakeholders, with strong attention to detail in documentation, investigation notes, and reporting.

   

Requirements

• Strong professional experience in software quality engineering, including automation, manual, exploratory, regression, and risk-based testing.
• Strong programming experience with Java.
• Strong understanding of object-oriented programming concepts, clean code principles, and design patterns as applied to test automation.
• Extensive hands-on experience with UI end-to-end automation, including Selenium WebDriver.
• Strong experience with API and web service testing using tools or libraries such as REST Assured, Postman, curl, or similar.
• Experience designing, developing, maintaining, or significantly contributing to scalable test automation frameworks.
• Experience using AI coding agents or AI-assisted development tools such as Claude Code, GitHub Copilot, Cursor, or similar.
• Experience integrating automated tests into CI/CD pipelines using tools such as GitHub Actions, Jenkins, TeamCity, or similar.
• Experience developing test strategies, test plans, and test cases for complex software systems.
• Strong analytical and troubleshooting skills, with experience analysing automated test results, investigating failures, identifying flaky tests, and improving test reliability.
• Experience testing SaaS products, distributed systems, microservices, integrations, or complex web applications.
• Experience working with logs, monitoring tools, test reports, dashboards, and other diagnostic sources to support investigation and decision-making.
• Experience with test management and reporting tools such as Xray, Allure, TestRail, Jira, or similar.
• Experience with Git-based development workflows, including pull requests, code reviews, branching, and collaboration with engineers.
• Strong written and verbal English communication skills, with the ability to explain quality risks, testing outcomes, and technical findings clearly.
• Ability to work effectively in distributed, cross-functional teams across multiple locations and time zones.

Nice to Have

• Experience with Playwright or other modern browser automation frameworks.
• Experience with native mobile testing, including mobile test automation using Appium.
• Experience testing integrations with Learning Management Systems or other third-party platforms.
• Experience with LTI standards, SSO, REST APIs, event-driven systems, or data synchronization workflows.
• Knowledge of cloud computing platforms such as AWS.

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.

Java · Selenide · AWS / Azure / GCP · Kubernetes · Terraform · Runtime Threat Detection
 

About the role

Upwind is a runtime-powered cloud security platform. We protect customers' cloud environments across AWS, Azure, and GCP — from the moment an account is onboarded, through vulnerability and image scanning, CSPM and compliance, identity and inventory correctness, all the way to runtime threat detection.
 

You will own quality for a set of product areas end to end: writing and running the manual test plans, building and maintaining the UI automation that keeps them from regressing, and being the person who finds the problem before a customer does. You sit inside a feature squad next to the backend and frontend owners, not downstream of them.
 

This is a hands-on role with a real learning curve on the cloud-security domain. We expect you to grow into it, and we will support that.
 

What you'll actually do

Manual testing & test design

• Build test plans for new features — onboarding flows, dashboards, scanners, integrations — and turn them into structured, prioritized test cases (P0/P1/P2) with clear preconditions, steps, and exit criteria.
• Run feature-level manual QA cycles: validate acceptance criteria against the PRD, verify each functional requirement, sign off before go-live.
• Run regression and retest sweeps ahead of releases, and verify fixes on dev before they move forward.
   

Bug reporting

• File bugs that engineers can act on immediately: summary, exact reproduction steps, expected vs actual, impact, environment, and evidence (HTTP requests/responses, Terraform or Helm output, console links, screenshots).
• Triage bug clusters by root cause and link related issues, rather than filing ten tickets for one underlying defect.
• Escalate customer-impacting findings clearly — especially anything that blocks onboarding or produces silent data inconsistency.
   

Automation

• Write and maintain WebUI automated tests in Java + Selenide, extending an existing framework: new test cases, page objects, helpers, test data.
• Grow automation coverage for the areas you test manually, so that manual effort shifts toward exploratory and new-feature work.
• Keep the suite healthy — investigate failures, distinguish real defects from flakiness, and fix the flaky ones.
• Push testability into the product: drive stable data-testid selectors and other conventions instead of depending on CSS classes, DOM structure, or text.
   

Cloud & hands-on environment work

• Set up and tear down test environments yourself: onboard AWS accounts and organizations via CloudFormation and Terraform, onboard Azure tenants and GCP projects, and verify off-boarding actually cleans up.
• Deploy and validate our sensors — the Upwind Operator on EKS via Helm, and host agents on EC2 instances.
• Generate realistic QA workloads and verify the platform detects and displays them correctly.
• Cross-check what the UI shows against the underlying data — backing stores, exports, and reports — to catch cases where the UI and reality disagree.
   

Collaboration

• Work daily with backend and frontend engineers, product managers, and designers inside feature working groups (Slack channels, Figma, Confluence).
• Keep test plans, test cases, and results documented in Jira and Confluence so anyone can pick up the state of a feature.
   

What we're looking for

Must have

• Commercial experience in software QA covering both manual and automated testing.
• Java — confident enough to read, extend, and debug an existing test codebase.
• Hands-on experience with UI test automation (Selenide, Selenium, or a similar WebUI framework). Selenide specifically is a plus, but transferable experience is fine.
• Solid test design fundamentals: equivalence classes, boundary values, negative testing, prioritization, and knowing what not to test.
• Comfort with REST APIs and browser devtools — reading requests, responses, status codes, and payloads to pinpoint whether a bug is frontend, backend, or data.
• Working knowledge of at least one major cloud provider (AWS, Azure, or GCP) — you can navigate a console, understand IAM basics, and follow an onboarding flow.
• Basic Linux and CLI comfort: SSH, systemctl, log reading, running install scripts.
• Git, and experience working in a Jira-based workflow.
• English sufficient for daily written and spoken work with a distributed team.
   

Nice to have

• Kubernetes fundamentals — enough to run kubectl, install a Helm chart, and read pod logs.
• Terraform or CloudFormation exposure.
• Background or genuine interest in cybersecurity: vulnerabilities and CVEs, CSPM, IAM, threat detection.
• SQL or experience querying a data store (e.g. OpenSearch) to verify data independently of the UI.
• CI/CD experience — running suites in a pipeline, reading build failures.
• Experience testing in regulated or compliance-driven environments (FedRAMP, SOC 2, or similar).
   

What matters most to us

• Curiosity about why something broke, not just that it broke. The best bugs on our board come with a diagnosis attached.
• Ownership. You set up your own environments, you chase the answer, you 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 cloud security fast. You don't need to arrive an expert — you do need to want to become one.
  
   

What you'll learn here

Real depth in cloud security across all three major providers, hands-on Kubernetes and infrastructure-as-code, a mature Java automation stack, and what it takes to ship a security platform trusted with production cloud environments.

Зараз шукаємо Python Developer (Automation) у команду Trident Apps — спеціаліста, який буде реалізовувати автоматизоване тестування за готовими сценаріями від QA-команди.

Основний фокус ролі — написання парсерів, автоматизацій та автотестів для внутрішніх продуктів компанії.
 

Очікуємо від тебе:

• Досвід роботи з Python;
• Досвід написання парсерів або автоматизацій;
• Досвід роботи з одним або кількома інструментами: Selenium, Puppeteer, Appium;
• Досвід роботи з PyTest або UnitTest;
• Вміння працювати з API;
• Досвід роботи з Docker.
   

Твої майбутні задачі:

• Реалізовувати сценарії автоматичного тестування на основі готових кейсів від QA-команди;
• Писати та підтримувати автоматизації;
• Пропонувати ідеї щодо оптимізації виконання автотестів;
• Взаємодіяти з командами розробки та тестування.
   

Буде плюсом:

• Досвід роботи з CI/CD;
• Знання Linux.
   

Що ми пропонуємо:

• Повністю remote — працюй з будь-якої точки світу, де тобі зручно;
• Гнучкий графік без мікроменеджменту;
• 30 робочих днів оплачуваної відпустки на рік та 10 днів лікарняних;
• Івенти та корпоративні тімбілдинги — онлайн та офлайн;
• Подарунки та мерч до свят і важливих життєвих подій;

• Корпоративна англійська;