Middle QA Engineer (Manual + Automation)

We're expanding and looking for a detail-oriented and responsible Middle QA Engineer who will help us ensure the quality of the products we develop and become a valuable part of a strong team.

Our products are web-based platforms used by marketing and creative teams, so attention to detail and the ability to test complex user flows are essential.

Responsibilities

• Functional and regression testing of web applications;
• Testing complex user scenarios (UI/UX), including cross-browser compatibility;
• Creating and maintaining test cases, checklists, and testing documentation;
• Reporting, tracking, and verifying bugs;
• Participating in release testing and smoke testing before deployments;
• Testing REST APIs using tools like Postman;
• Writing and maintaining basic automated tests for key product flows;

• Collaborating with developers and product managers to clarify requirements and edge cases.

  Requirements

• English proficiency: ability to read technical documentation and write clear bug reports (speaking is not required but would be a plus);
• Commercial experience in testing web applications for 1+ years;
• Strong understanding of manual testing principles (functional, regression, exploratory);
• Experience with bug tracking systems (e.g., Jira, ClickUp);
• Experience testing REST APIs (Postman or similar tools);
• Familiarity with browser DevTools;
• Basic understanding of test automation concepts;
• Responsibility, attention to detail, and clear communication.
  Would be a plus
• Experience writing automated tests (Playwright, Cypress, or similar);
• Experience with API test automation;
• Basic understanding of CI/CD pipelines;
• Familiarity with Git and development workflows;
• Experience testing data-heavy dashboards or complex web systems.

• Familiarity with mobile marketing / user acquisition (UA) or the concept of traffic acquisition for mobile apps.

  Conditions

• Fully remote work;
• Schedule: Mon–Fri, 10:00 to 19:00 (UTC +3);
• Small product-focused team with direct communication between QA, developers, and product managers;
• There may be periods of lower workload between releases — during this time, tasks may include documentation updates, preparing test plans for upcoming features, and improving test coverage (including automation).