Position: Junior QA Engineer
Category: QA
English level: intermediate
Years of experience: 1

I was the team leader (group of 10 people) of the Mindmap training project at GoIT during my studies. The mentor's comments:"The mindmap is incredibly detailed, the presentation of processed information is well structured. I would like to say something about the clear sequence and original presentation."
PROJECTS
PETLY: my first project. GoIT provided an opportunity for course graduates to implement their theoretical knowledge in an educational project as close as possible to real life.
The team consisted of two groups: FS Developers and QA Engineers. The task of FS was to create the PETLY site, QA  – to test the site and its components as a whole in order to eliminate defects and improve the product as a whole.
MY ACTIVITIES and my group of QA Engineers activities  on the project:
1. Meetings of the QA group to choose a testing strategy and tools, clarify problematic issues, and resolve current issues.
2. Joint meetings of FS and QA to clarify the functionality of the product, raise problematic issues and the algorithm for solving them, make suggestions for improving the functionality, UI of the site.
3. TRELLO was used to manage the project and tasks.
4. POSTMAN and SWAGGER were used to work in the BACKEND (working with user registration and login endpoints, adding and removing ads and user cards, etc.). POST, GET, PATCH, DELETE methods have been developed.
5. In FRONTEND, the same testing was carried out on registration, login, creating ads, etc., which made it possible to see the differences and interaction of Frontend&Backend.
6. 260 TEST CASES, 78 TEST RUNS were created in TestRail.
7. 47 BUG-REPORTS were created in JIRA.
8. Static testing was carried out (review of technical specifications, site layout); dynamic testing (black-box testing); non-functional testing (UI); testing related to changes (smoke, repeat, regression); according to the scenario (positive and negative). Techniques such as equivalence classes and boundary values were developed using the BLACK-BOX testing method.
Testing was conducted on various devices: Desktop, Tablet, Mobile.
9. After completion of testing, data collection, analysis of the conducted testing and creation of a summary report.
--------------
And also my 11 homework tasks were successfully completed in the GoIT courses. 
The following topics were studied in home tasks: 
QA Documentation, Software Development Lifecycle Models, Testing types: Unit, Integration Testing, System Testing, Acceptance Testing; Test Techniques: Black-box testing, White-box testing, Static Testing, Web technologies: HTTP request, work in Front-end, Back-end, XML, JSON; API (Trello, Postman), Database (SQL).
I prefer web testing and don't want to work for Gamedev.