Position: QA Automation Engineer
Category: QA Automation
English level: fluent
Years of experience: 1.5


Currently Middle Test Automation Engineer at UpTrader Inc. a major white-label CRM solution for brokers worldwide.

Our CRM is used by hundreds of thousands of users in Asia Pacific, Europe, and the Middle East. It’s a complex piece of software with multiple integrations and rich functionality including support for money transfers, trading on the stock and currency markets, management of thousands of accounts, to name just a few. The app is rapidly growing and has multiple releases each sprint.

The QA of the app is carried out by a test automation system based on Selenium Grid & Pytest. Steps Model and POM are implemented to make code scalable and easy to maintain. The rapid growth of the platform is achieved by the implementation of GitLab CI and automated bug reporting, which caches bugs way before they can make it to the prod. This way I can add multiple new tests to the system each week, as well as regularly revise old ones to make sure everything stays up to date.

* Project Stack: React, Django, PostgreSQL, Docker & Kubernetes, Git, Sentry, Jira, Figma, C++ and C# for third-party software integration.
* Test Stack: Selenium WebDriver, Selenium Grid, PyTest, Requests, GitLab Ci.

Team: me, 1 QA Engineer, 3 Back-end Engineers, 2 Front-end Engineers, an Analyst, a Designer, and a Product owner. We work on scrum methodology with daily meetings and a review & planning session each sprint. Workloads are estimated in story points.

My achievements. 
Fixed broken test system. The system was out of use for several months before I came. I have rebuilt the architecture to implement POM and made code more scalable, as well as improved automated reporting: implemented logging and replaced screenshot capture with video capture, so all our tests could be watched like a movie to figure out what went wrong really quickly. Also, I have updated the software including Selenium Grid and Python. I have rewritten old tests, so they could work with the updated architecture.