Position: QA Lead (4-days work week)
Company: Hellotickets
Experience required: 5y
Category: QA Automation
English level: upper
Published: 2023-09-01T00:00:00+03:00

Hellotickets is looking for a Quality Assurance Lead. 
**If you can not only manage, but also show by your own example how to work qualitatively, know how to teach, know how to build a process from scratch, and defend the right decisions - we are waiting for your resume!**

**Main requirements:**
- Experience in similar position in last **2 years**
- Good English
- Excellent management skills, extreme attention to detail, ability to multitask
- Self-starter who can develop solutions to solve challenges
- Effective work with technical documentation
- Experience in backend functional testing using postman/swagger
- Extensive experience in integration testing
- Good knowledge of testing theory, test design, SDLC/STLC and Agile-based frameworks


**Responsibilities:**
- Create, control, and promote QA standards and best practices
- Provide technical guidance to teammates through coaching and mentorship
- Provide high-level coordination and guidance to team members
- Ability to work in a fast-paced environment that supports production and maintenance level changes
- Collaborate with other teams and departments, company management to ensure projects are completed to established technical standards


**We offer:**
— Full-time, remote job
— 4 days working week (Monday - Thursday, Friday day off)
— Paid vacation (20 days) and sick leaves
— Flexible working schedule
— Friendly professional staff and warm atmosphere

**Application Requirement:**
As part of your application, we would like you to respond to a scenario that simulates a real-world situation you might encounter in this role. Please provide your approach to the following scenario:
Web project. You are a QA Lead on a project team alongside another Middle QA Engineer. There are three tasks, each with its own severity level: Major, Critical, and Blocker. Unfortunately, there isn't enough time to thoroughly test all three tasks before the release, and each task requires the dedicated attention of one person. 
The number of environments and regression testing is not taken into account. There is no additional information.
Your Response:
Please outline your strategy for handling this situation, including how you would prioritize and allocate resources among the tasks, and mitigate potential risks.