Anca Petrea

As a QA Engineer in a newly formed team is challenging and rewarding, and my responsibilities are: - Integrating the QA process during the development life cycle inside the team, but aligned with the company QA process; - Reviewing the Acceptance Criteria defined for different implementations; - Documenting the use cases found for the different implementations; - Run: manual testing after the development is done; integration testing; data integrity and regression testing; - Web Services testing.

As a QA professional coming from an outsourcing background, I got the opportunity to be involved in the entire Software Development Life Cycle from defining the product requirements to making sure those same requirements are delivered in the product shipped to the customers. I applied all my previous knowledge in Software Testing and helped the company increase the quality of the product. I soon became responsible for managing the releases from a QA perspective and giving the green light for the launch.

As an assistant manager, a very important part of the job was making sure that the collaboration between the testing and development teams ran smoothly. Along with responsibilities like training new team members, the job implied creating test plans, writing technical documentation, providing estimates for QA tasks, prioritizing tasks and much more. In this role I learned a lot about the importance of collaboration, I improved my QA technical skills and I obtained the ISTQB Foundation certification.

My main responsibility was to accurately test the customer's product and report bugs or features that were not according to specifications. I and the other members of the QA team would make sure that the software met the quality standards imposed and that all environments were working as expected. - CRM project. - Manual testing - Regression, smoke and integration testing - Bug reporting and tracking (Jira) - Documenting the test scenarios. - Team with up to 15 QA testers and 2 team leaders.