A Day In The Life of a Quality Analyst at Springworks

Anusha QA engineer

If you’re anything like me, you’ll understand when I say: I love hearing about career stories — not out of nosiness (OK, maybe a little!), but curiosity and interest. 

This ‘A Day in the life of’ series gives you an insight into what a typical day looks like for our employees at Springworks and how they started their careers. 

Today’s story is about Anusha Bhat, who’s a QA Engineer. Hopefully, you’ll take something inspirational away from it.

Anusha Bhat

My alarm clock goes off…

At 7 AM. And then I do some household work and make my breakfast.

My commute to work… 

Usually, I leave for the office at 11:30 AM with my colleague and we choose to carpool to combat the traffic congestion. 

Why I became QA…  

I tried many roles in development, recruitment, and content management in bits. And QA`s shoes fit me the most. I guess the ability of questioning makes me fit better here. I think a QA analyst position is a very good place to start when you’re not exactly sure which path to take in web development.

I’m responsible for… 

Daily checking the crash reports and bringing to the notice of dev and biz teams of any chokers. Sticking to the release cycle and boosting the confidence of the release by testing covering maximum use cases are a couple of things always expected.

When a product feature is released, I spend time running tests, talking to the team and the client about additional information that always comes up in this stage, reporting test results, and feeding back any suggestions for improvement.

The most challenging part of my job… 

Figure the loophole of the system before it reaches the customers. If the product is successful, then developers are to be credited,  but when it’s flawed, QA to be blamed. So it’s not easy to be a QA engineer.

Unfortunately, in many companies, the Development team and QA team are not in so-called “friendly” relationships that they should be. It is very important to share knowledge with each other. 

Luckily it’s not the case in Springworks. Here, the QA team is aware of the development process of a product and the Development team helps to increase the quality of the product and to care about it in terms of testing.

The best part of my job… 

I am allowed to take the steps which can benefit the product. My opinions on product development are respected. The most successful projects on which I have worked at Springworks have succeeded because we had people with different skills in the team.

My typical day… 

Being in the coolest team, always had fun at work from the time I come to the office. Sticking to the plan of the release cycle and keeping an eye on crash reports. Then daily stand up and looking for new tools that can ease QA`s life.

Meet with developers to discuss test strategies for new features. List down tests to do (like functional, usability, performance) and new automated tests to cover. Think if we have all the tools and knowledge that are needed.

I also share knowledge with other team members if she or he needs my immediate feedback. E.g., a developer asking how a feature should work in some edge case or product manager needing to understand how other parts of the product work.

At the end of the day, I write down all the things I wasn’t able to do this day and review priorities for the next day.

My favorite thing about life at Springworks… 

Springworks is like my second home. I never had Monday blues after being part of Springworks. Benefits like owning the work planned and working with a good pace, no pressure, time flexibility, etc. make Springworks one of the best workplaces I could be in.

We don’t have slackers in the company who just want their salaries and go home. Everyone wants to grow and develop and help build the company. This is very inspiring.

My best advice for someone looking to become a QA analyst… 

Think where your product or project can break and have the checklist for every release cycle. 

Learn to understand the context of each fix or release, in order to determine what tests are required to be run and also determine which ones can be left out without incurring any significant risk.

Leave a Reply

Your email address will not be published.

Previous Story

6 Must-Have Qualities of Successful Recruiters In 2020 [Infographic]

hiring for startup
Next Story

How to Successfully Hire Right Talent for a Startup: The Complete Guide

Latest from Life at Springworks