A day in the life of Manual QA Engineer
Welcome to our “A day in the life” blog series, where we offer a behind-the-scenes look at how specialists across Pwrteams work, collaborate and navigate everyday challenges. Each edition focuses on a different role, giving insight into daily routines, responsibilities and what it’s really like to be part of our teams.
For this chapter, we spoke with Lesia Smyrnova, Manual QA Engineer at Pwrteams Ukraine. With an academic background in System Analysis, Lesia found her place in tech by focusing on analytical thinking, communication and a deep understanding of software processes. Her workdays revolve around testing complex business logic, managing time pressure and collaborating closely with her team in a fast-changing Agile environment.In this interview, Lesia shares details about her career path into QA, what a typical workday looks like, the challenges she faces and what she enjoys most about being part of her team at Pwrteams.
How did you come into this position? What was your previous background?
I started working as a Manual QA about 5 years ago. My educational background is somehow related to what I do now - I studied System Analysis at the Faculty of Applied Mathematics and Informatics at Ivan Franko Lviv National University. I got my bachelor's and master's degrees there, which gave me a deeper understanding of how software is developed. Although we studied multiple programming languages and had several related courses, coding never came easily to me. Even with a good understanding of language syntax and strong knowledge of algorithms, creating a program from scratch was challenging. And interestingly, once I finally solved an issue and the program worked, it often felt obvious in hindsight.
When it was time to start my career, I decided to focus on my strengths and, well, how to put it.... coding wasn’t one of them. I can still read and understand existing code, identify weak spots in software thanks to my background, and I have strong communication skills, which are one of my biggest professional assets. Putting all of that together, QA felt like a natural choice. I started learning independently, took courses and deepened my knowledge in areas I knew I’d need - networks and protocols, SQL and creating and maintaining documentation. After several interviews, I received my first offer, and well, here I am.
What does your typical workday look like?
I start my day by logging in and reviewing all the emails and product channel mentions that came in overnight. After this slow introduction, I sketch out my workday: what tasks are top priority, what I need to investigate, and how everything aligns with deadlines. I usually work using the Pomodoro technique. I set a timer for 45 minutes and stay fully focused during that time, trying not to get distracted. When my attention drifts, it becomes much harder to complete tasks efficiently. After each focus session, I take a 5–7 minute break, making coffee in silence, having a snack or simply staring out the window to give my brain a rest. This rhythm carries me through most of the day. My meetings usually happen later in the evening, between 5:00 and 6:30 p.m. At that point, work becomes more intense and distractions increase, so I make one last push before logging out around 7:00 p.m.
What’s your favourite part of the job?
I really enjoy working with complex business logic and figuring out how to fit the most important tests into the limited time we usually have left (yes, we’re almost always short on time). It’s the most challenging part of my job, but also the most fun. It may seem difficult, but it’s creative in its own way.
And the most challenging?
Time pressure - always. A fast-changing environment is unavoidable in today’s reality, but having little time or no opportunity to stick to an initial plan can make things hectic and intense. I’m comfortable working in an Agile environment, but planning your work becomes especially challenging when priorities change on an hourly basis.
What new skills have you picked up in this position?
In my current role, I combine QA and BA responsibilities. It can be overwhelming at times, but this is the first project I’ve been part of where every team member needs a deep understanding of even the smallest details - processes, flows and business logic. There are so many nuances and specifications that everyone on the team has become a strong analyst.
What makes it so great to be part of your team?
The feeling that “we’re all in the same boat” makes people more collaborative and creative when it comes to achieving project goals. I truly appreciate my colleagues for that; most of them are excellent collaborators. They manage to be top performers despite limited time and resources, which is incredibly inspiring to witness and be part of. I’ve also made a few great friends within the company.
What do you like the most about being part of the Pwrteams family?
The people here are great both professionally and personally. The company puts a lot of effort into organising monthly activities - workshops, Ice Cream Days, and events where colleagues are welcome to bring their families. It creates a warm and comforting atmosphere that really helps us unite. One more thing, it’s no secret that my favourite colour is purple, and it just happens to be our company’s brand colour. As a total purple-colour enthusiast, I simply couldn’t work anywhere else without being surrounded by purple all the time (just kidding, haha).
Want to team up with awesome people like Lesia? Take a look at our open positions and don’t forget to apply!
Write your own
success story
with Pwrteams!
Share your details in the form, tell us about your needs, and we'll get back with the next steps.
- Build a stable team with a 95.7% retention rate.
- Boost project agility and scalability with quality intact.
- Forget lock-ins, exit fees, or volume commitments.