Quality Trail

My name is Armin Rajaee and I’m an experienced Software Development Engineer focused in Quality Assurance and Test Automation with 9 plus years of recent experience working in the banking, high tech, and several well-known Canadian and international organizations. Over the past 9 years, I have developed a strong background in software development and testing methodologies, enabling me to assess and improve the quality standards of any given software project.

My main areas of expertise include software quality assurance planning, test automation, test execution and result analysis, and quality management. I have experience working with a wide range of technologies, in different levels and stages of testing, and more. I’m also familiar with Agile and Waterfall methodologies and have performed in both successfully in past projects.

In this blog I will mostly write about the rolea and responsibilities of a QA engineer (SDET) in a software team. As an SDET it is your role to be the ambassador of quality for the organization. You are responsible for ensuring the highest level of quality from the initial stages of development all the way to the final code and product release. Your responsibilities include analyzing the requirements, creating and executing test cases, tracking the progress of the tests, and reporting any defects that may be encountered. You must also ensure that the software meets customer expectations and that customer feedback is incorporated into product releases.

The QA engineer is also responsible for communication between business stakeholders, engineers and quality assurance personnel. Your job is to mediate between different parties to ensure that everyone is on the same page and that they understand the consequences of their decisions, you are there to foresee what may go wrong as the result of a technical decision long before you catch it as a bug in the final product. You must also strive to ensure that the deadline is met and the product is released on time and no unexpected scenario is going to show up on the last days to delay the project.

This is not an easy role and requires you to understand the project from inside out and from outside in at the same time. You should speak end users’ non technical language to communicate to CX teams and be able to translate it into technical language of the engineers and follow, analyze, and debug the code to find the issue at the same time.

In this blog I am going to share my experiences with anyone who is interested in Software QA. I would be also super happy to hear from you. Please do not hesitate to contact me, write comments or message me here or on Twitter.