QA Engineer (Ultimate team)

• Strong communication skills and the ability to explain technical problems clearly.
• Independence, self-discipline, and a habit of learning new technologies on your own.
• A collaborative approach to working with distributed engineering teams.
• Proven experience testing commercial software applications.
• Proficiency in Java or Kotlin sufficient to write test applications and read source code.
• Fluency in spoken and written English.
• Practical familiarity with build tools (like Maven, Gradle, or Bazel), databases, and Docker containers.
• Experience testing software across different operating systems alongside basic system administration skills.

Are you a QA Engineer who cares about code craft and system stability? Do you want to focus on quality over quick fixes and own your decisions from day one?

IntelliJ IDEA changed how Java development worked by introducing automated refactoring, and it remains a core tool for thousands of developers worldwide. Within the IntelliJ IDEA Ultimate team, we focus specifically on improving how the IDE supports key JVM frameworks like Spring, Jakarta EE, and Hibernate.

We need an independent QA Engineer to help us ensure these enterprise development tools remain reliable and efficient. You will take ownership of the testing process for new and existing functionality, balancing manual exploratory testing with automated test development. You will work closely with developers to spot flaws early and collaborate directly with product managers to decide which issues impact our users most.

Day to day, you will:

• Perform exploratory testing of new and existing features to uncover edge cases.
• Run regression tests to ensure platform stability before releases.
• Maintain, write, and scale our automated test suites.
• Reproduce user-reported issues and provide technical support to resolve them.
• Collaborate with developers to share product knowledge and diagnose system bugs.
• Work with product managers to estimate the priority and business impact of issues.

Success in this role means earning the trust of your team through sound testing decisions and leaving our codebase cleaner and more stable than you found it. You will move past simple task lists to take real ownership of product quality, helping the team ship reliable updates without compromising speed. Ultimately, success is defined by preventing regressions and ensuring enterprise developers have a seamless experience using our tools.