QA Engineer (Toolbox QA)

We are now looking for a QA Engineer to join the Toolbox QA team.

Our team is working to evolve Toolbox into a broader part of the JetBrains ecosystem. This role covers several substantial areas at once: a desktop application, a shared local background service, and server-side and integration-heavy components that support product distribution, connectivity, and ecosystem workflows. Much of this work happens at the intersection of multiple JetBrains products and teams, so we are looking for a senior engineer who can take ownership, work proactively in ambiguous environments, and drive quality across subsystem boundaries.

In this role, you will:

• Own quality for several product areas and drive testing strategy within them.

• Participate in monthly release acceptance and help make release-readiness decisions.

• Perform functional, exploratory, regression, and acceptance testing for new and changed functionality.

• Search for, localize, and reproduce complex issues, report them in our issue tracker, and verify fixes.

• Work closely with developers during implementation, not only after features are considered ready for testing.

• Assess risks, define test scope, and decide what should be covered manually, what should be automated, and what must block a release.

• Contribute to test automation where it creates the highest value, including writing tests for some of our server-side and infrastructure-related areas.

• Collaborate with multiple JetBrains teams to validate end-to-end scenarios and reduce integration risks early.

• Help improve QA processes, release validation, and overall quality culture in the team.

• Contribute your own ideas to improve the product.

• Provide developers with recommendations on how to make the product more user-friendly, including advocating for user interests.

We will be happy to have you on our team if you:

• At least three years of experience in QA for complex software projects.

• Can work independently, take initiative, and manage tasks well.

• Are comfortable owning a broad area of responsibility and making quality decisions at the project level.

• Have experience testing desktop applications, client-server systems, or technically complex integration scenarios.

• Understand how to test systems that include UI, background processes, local services, network communication, and server-side components.

• Are confident investigating difficult problems using logs, metrics, system tools, and hypothesis-driven debugging.

• Have experience testing without complete functional specifications and can quickly build understanding in a new domain.

• Can communicate clearly with developers and other stakeholders, including in cross-team projects.

• Care deeply about product quality and user impact, not just test execution.

Technical requirements:

• Solid understanding of testing methodology, including risk-based testing, regression strategy, exploratory testing, and release validation.

• Experience testing complex applications on macOS, Windows, and Linux, and/or a good understanding of client-server architecture, HTTP, authentication flows, and integration points between components.

• Ability to investigate issues related to networking, process lifecycle, local environment, configuration, and OS-specific behavior.

• Confidence working with logs, thread dumps, command-line tools, proxies, and other debugging instruments.

• Basic programming skills sufficient to read code, understand implementation details, write small utilities, and create meaningful test scenarios.

• Familiarity with Kotlin and/or Java.

• Experience with YouTrack or similar issue trackers, CI systems, and version control workflows.

We’d be especially thrilled if you:

• Can write automated tests in Kotlin or are comfortable contributing to automation when needed.

• Have experience with integration testing, infrastructure-related testing, or validating distributed workflows.

• Have worked with release processes, release acceptance, and quality gates in products with frequent releases.

• Can define a quality approach for a new subsystem from scratch and drive it with limited guidance.

• Enjoy improving processes, not just following them.