Anjali Goyal - QA Career Insights: Inspiration, Challenges, and Tech Stack Management
What inspired you to pursue a career in QA?
Being in Quality Assurance means that you perform the last checkpoint for any feature of the product before it gets shipped to the client. It involves problem solving, managing risks and ensuring high quality standards are met throughout the Software Development Life Cycle - it’s a huge and exciting responsibility! It brings me closer to the product and at the end of the day, it’s very satisfying to deliver a high quality product to the client.
What are some of the common challenges you face while working in QA?
Being in Customer Success and following agile methodology means welcoming frequent changing requirements and ad hoc requests from the client. It gets challenging but consistent collaboration within the team and constantly improving the processes help overcome these challenges.
How would you describe the work culture in our company?
The work culture in Backbase is outstanding - Diversity and Inclusion at its best. Despite a diverse culture, Backbasers come across as very collaborative and depict together and entrepreneurial behavior. I believe this comes from the fact that we have such strong leadership! Additionally, each Backbaser has their dedicated People Manager - who helps them in shaping their interests, optimize productivity and enables professional growth.
What programming languages and tools do you use in your work as a QA engineer?
As a Senior QA Engineer and having worked within this domain for more than 7 years, I have worked with a wide variety of tech stack. However, in Customer Success we use Espresso Test Framework for Android UI Automation, XCTest for iOS, Playwright for Web, RestAssured and Postman for API testing; Jenkins and GitHub Actions for CI/CD.
Can you share any insights or tips you have learned over the years for effectively managing a complex tech stack?
I have always enjoyed learning something new which is why I also update myself with evolving industry trends. I tend to understand frameworks - their best usage, limitations and compatibility - to effectively utilize them based on varying business needs.
So, choosing a tech stack should rely on current objectives and business needs. If a product roadmap can succeed without utilizing trending technology (programming languages/ databases/ frameworks), then it’s not worth the time, effort and cost to update your existing technology with every new trend in the market. Any addition to or change in a tech stack must be about solving a real business need rather than simply buying into the hype.