My Software Tester Career Journey Across Different Industries
My software tester career journey began when I joined Testvox as an intern. I did not start with years of software development experience or an extensive technical background. I started with curiosity and a desire to understand how software works and how QA engineers ensure applications function correctly before reaching real users.
At Testvox, I learned through hands-on work on live projects. I developed practical skills in understanding requirements, designing and executing test cases, reporting bugs, verifying fixes, and testing applications from the user’s perspective.
My software tester career journey grew from an internship into a full-time QA career, with experience across web applications, mobile apps, APIs, and projects in different industries.
Can you share your journey to becoming a software tester?
My journey began when I joined Testvox as an intern. I did not have a background in coding or years of tech experience. Instead, I arrived with a simple curiosity: I wanted to understand how software is built and how to make sure an application works properly before it reaches real users.
Rather than just studying theory, I learned by working on live products. Step by step, I learned how to review requirements, write test cases, run tests, report bugs clearly, and verify fixes. Over time, that internship grew into a full-time QA career where I took ownership of testing across web platforms, mobile apps, and APIs.
What did you learn after joining Testvox as an intern?
I quickly realised that software testing is much more than just finding bugs. A good QA engineer looks at the whole user experience, understands business goals, tests unexpected edge cases, and communicates clearly.
During my time here, I built practical experience in:
- Manual, functional, and regression testing
- Designing and executing test cases
- Web, mobile, and API testing (using Postman and JSON validation)
- Bug tracking and management with Jira
- Database fundamentals with SQL / MySQL
- Basic test automation with Playwright
I also learned how essential teamwork is. Testers must work closely with developers, project
managers, and designers to help build a reliable product.
What made your Testvox journey different?
The variety of projects made a huge difference. Instead of testing the same product repeatedly, I
moved across different industries. Each project brought new business rules, user expectations,
and technical challenges.
This taught me that while every product is unique, the core mission of QA never changes:
understand the requirements, think like the end user, spot defects early, and deliver quality.
Can you tell us about some of the projects you worked on?
I had the chance to work across several different domains:
- Composio: An API integration and automation platform where I focused on testing endpoints, authentication, and full business workflows.
- DR-M & Magrabi: E-commerce platforms in Saudi Arabia, focusing on shopping journeys and checkout flows.
- Famplanr: A family organizer app centered on task and user management.
- Archstore: An e-commerce app requiring thorough testing of customer journeys and catalogue behaviour.
- Sensodoko: A mobile game where performance, responsiveness, and device stability were top priorities.
- Aifer: An educational app focused on student learning workflows.
- Castle: An OTT streaming platform where I tested media playback, navigation, and streaming stability.
- Zywa: A fintech application where data security, accurate calculations, and reliability were critical.
- Kallarackal Maharani Jewellers: A retail platform spanning an admin panel, Android, and iOS apps, with a focus on schemes, payments, and admin controls.
- Klinik-Plus: A healthcare platform connecting doctors, patients, and hospital workflows.
- Evide: A local service booking platform involving multiple user roles and real-world interactions.
What is the biggest lesson you learned from working across different industries?
Every application has its own story and unique risks. You cannot test a banking app the same way you test a mobile game or a hospital management system.
Before running a single test, I learned to pause and understand the product and its users. I now routinely ask:
- What is the main purpose of this feature, and who uses it?
- What happens if someone types in invalid data?
- How does the app respond if the network drops or an API fails?
- What happens if many users complete an action at the exact same moment?
- What happens if a user clicks through screens in an unusual order?
What is a moment you are particularly proud of?
I am proud of my growth from day one—moving from learning the basics to managing complete testing cycles on live projects. Even when faced with unfamiliar domains, complex bugs, or issues that were difficult to reproduce, each challenge taught me something valuable. Seeing an application move smoothly from development to a stable launch is always rewarding.
What do you enjoy most about software testing?
I love the problem-solving side of QA. Developers build features to follow a plan, but testers explore what happens when users go off-script.
The most critical bugs often appear when someone enters unexpected data, switches devices mid-task, or loses their connection. I enjoy investigating those edge cases, asking “What happens if…?”, and preventing problems before users ever encounter them.
What has been the biggest challenge in your QA journey?
Adapting quickly to new industries. Every new project comes with unfamiliar terms, workflows, and user expectations. Instead of finding that overwhelming, I treat each domain as a chance to learn faster. I also learned that writing clear, detailed bug reports is essential so developers can easily reproduce and fix issues.
How would you describe your experience at Testvox?
Testvox shaped my professional career. It went far beyond a normal internship because I was trusted with real responsibilities from the start. It taught me testing tools and techniques, but more importantly, it taught me how to think like a tester. I am grateful for the guidance and trust that helped me grow into a QA professional.
Why would you encourage someone to consider a career in software testing?
Software testing is an excellent career for anyone who is curious, enjoys solving puzzles, and likes looking at products from different angles.
You do not need to know everything when you start. I came in without a software development background, but curiosity, hands-on practice, and asking the right questions helped me build a career. In the end, QA is about understanding the user, protecting their experience, and helping the team build better software.
Conclusin
As I developed my automation skills, I began exploring Playwright testing documentation to understand browser automation and reliable end-to-end testing.