Move beyond AI notetaking: Be the first to see the new features in Fellow 4.5

X

3 Meetings For Your First Week as a Quality Assurance Analyst

Starting your role as a QA Analyst? Check out these tips to get to know your manager, the product's test environments, and the customers' point of view.

By Moni Ahmadi  •   November 27, 2020  •   2 min read

If you are a Quality Assurance Analyst and started your job recently, this is a list of three meetings you should schedule immediately!

1 One-on-one meeting with your manager

First, get to know your manager and set up a one-on-one meeting with them. There are lots of items you need to talk about but I’ll point out some important ones here:

Ask about their expectation for the QA role, the current QA process and the authorities you’ll have in your role.

Ask about the tools you should work with, test environments, and remember to request access.

It’s important to learn about the development structure, regular deadlines, dev team meetings and any other rules/best practices.

Talk about what you want to build for the first 6 months, your abilities to tackle the existing problems, and what you need to do to reach your teams’ expectations.

Finally, if you’re not working remotely, don’t forget to ask them to give you a tour of the office, the kitchen, and make sure you learn how to make your next morning coffee. ☕️

Pro Tip

Fellow’s library of 200+ suggested one-on-one meeting questions will help you spark an engaging conversation.

Try it for free

2 Meeting with a Data Analyst

If you’re starting a new role as a QA Analyst, you need to learn about the analytical tools. This will help you understand usage in different parts of the product! Having a one-on-one meeting with a data analyst in your company will be very beneficial.

Ask them about the company tools and ask how they work. Then, export whatever you need to write the test strategy and test plan.

Here is an example of how usage data can help:

In our case (at Fellow.app) it’s useful to know if most users are using browsers or mobile applications. Which browser is used more, which components are most important, and the average number of concurrent users per day.

These are all items to consider when you start writing your test strategy!

3 Meeting with the Customer Success team

As a Quality Assurance Analyst, it’s very important for you to get to know the Customer Success team at your company. The Customer Success team knows everything about the product and users’ requirements – the parts they love and the parts they don’t!

Ask them to give you an onboarding tour as a user. This will help you understand the product so much faster and more efficiently!

Get to know the users’ point of view; what they think about the product, which feature is their favorite, which bugs usually make them angry and so on…

Make a list of the most important parts and mention them in your test plan. This will help you display your ability to track and catch the product’s issues.

We hope that these tips help you in your new role as a Quality Assurance Analyst!

Be sure to check the Fellow Blog soon for more content on management, leadership, or productivity 👋

  • shopfiy
  • uber
  • stanford university
  • survey monkey
  • arkose labs
  • getaround
  • motorola
  • university of michigan
  • webflow
  • gong
  • time doctor
  • top hat
  • global fashion group
  • 2U
  • lemonade
  • solace
  • motive
  • fanatics
  • gamesight
  • Vidyard Logo