Interview

Good afternoon, my name is Pavel, glad to meet you. I have been working as a tester for more than three years and mostly on English and Germany projects. During this time there were four projects. I can say about myself that I love working in large teams and interesting projects, because you always grow up as a person and learn a lot of new things, thereby improving your skills.

The last project I worked on is called KordaMentha, the essence of which was to create a system that would help process lawsuits and check them, and then sell this system to various companies that want to manage their lawsuits. On this project, we used the development methodology of scrum, because we believe that it best choice for our requirements and team, because there were all the meetings we needed like daily, grooming, planing, retrospective and so on, also it was sprints, and much more, we used the JIRA bug tracking system in which we have all our tasks and bugs. We had a large team, which included 7 developers, a business analyst, 2 testers, project manager and a UI/UX designer.

My responsibilities included quite a lot of things, I constantly had to work on a couple with a business analyst to understand the business logic of the project as well as possible, so we always started with checking requirements and documentation, in which we found logical bugs and it was good that we found it on the documentation leve, for example, I remember we had a problem with the registration of users, because the documentation did not describe what to do if the user interrupted his registration. There were also problems with the fact that the user could restore a blocked account simply through the password recovery function, which is also a rather serious mistake.

There were, of course, ridiculous cases in my work, for example, when a developer confused pop-up windows, and the user after logging into his account was shown a notice that his account was blocked, instead of a greeting.

Often there were also situations when developers say that this is not a bug and that they are not going to fix it, in this case you have to call them, show and analyze everything with documentation and design, and most often the conflict is settled and I am right, but sometimes Of course, it comes to the business analyst, which reinforces my words.