My everyday goals are:1. Maintaining the relevance of technical questions2. Maintaining the order in the section (clear rules, problem solving)My achievements, which I am especially proud of:1. Detailed feedback for each candidate who was interviewedI believe every specialist learns day by day and should be able to work with weaknesses. So our feedback is compiled with care by experienced interviewers using a library of useful topics and links. This way, the candidate gets not only a list of topics, but also sources that we trust2. Detailed interviewer reportsA lot of work has been done with quality of the reports after the interview. We needed to provide hiring managers reports that reveal the candidate from different sides: practical experience (analytical skills, testing tools, situational behavior), theoretical knowledge (fundamentals of mobile testing). A flexible template has been developed for interviewers, that includes auxiliary blocks for an assessment of the candidate3. Preparing materials for candidatesI renew our lending with useful themes and links to help candidates to prepare for coming interview at mobile section. There are the main topics that we will discuss, attached only free and educational materialsIf we talk about my other responsibility, I regularly do interviews, communicate with recruitment and help interviewers with any kind of problems

My technical responsibilities are:1. Websocket, localise and universal links testing2. UITesting in Swift3. Write simple scripts in Proxyman to simplify test dataMy other responsibilities are:1. Juniors and interns onboarding2. Work with test documentation at different levels (write / review)3. Participating in a 3Amigo and take all related work4. Сonducting a retrospectives, make points and monitor the progress6. Weekly duty aimed at working with requests from our users

1. Onboarding of new employees. Create tasks for a trial period in accordance with the project technical matrix, employee's wishes and abilities. I identify improvement areas and suggest ways to work with it2. Organization interns and juniors work. Creating a development path to an independent QA and support all along the way 3. Always here for any of new ideas. With my QA team we have developed a critical path scenario (CPS). CPS are written based on analytics. The idea is to draw a portrait of our average user and his/her behavior in the app. The task of CPS is to inform the team about general state4. Reduction of the regression testing. Team "Payments&Transfers" is large, so the regression could last more than two weeks. What I did: 4.1 rely on our analytics data, I have identified a list of critical screens by the criteria: the number of users and money loss4.2 our application is divided into modules, so it allowed us to collect only the screens, that was affected in the development processAt the moment regression testing consists only affected screens + critical ones. It helped us to free the time and pay attention to other activities5. Familiar with new testing tools. Step by step, I arranged moving the entire development and testing team to a new tool for UITesting and test cases (about 400 people). I provided colleagues: a storage space for test cases with easy navigation, clear instructions and webinar6. Work organization. For an easy start in the team, I wrote a page with all the frequently asked questions of newcomers and explanations of the work of various specific tools in the project7. Independence. I appreciate desire to be independent and take responsibility for new areas. Therefore, each QA had its own responsible area in the team. My only task is to help and explain everythingThe complex of my actions allowed the team to be independent and calmly without a team leader during the vacation