Position: Senior QA
Company: bvblogic
Experience required: 5y
Category: QA
English level: upper
Published: 2022-09-01T00:00:00+03:00

**Overview:**

 We've been solving scheduling problems since 2008, with our first app, the we launched *Client Name under NDA* in 2011 and is self-funded, profitable, and privately owned.
We pride ourselves on being product-led and customer focused. Our product is optimized for teams, and we love working with them — large and small. We're good at what we do, some of the biggest names in our industry use and validate our tool, and our customers love us. And we've done all this while being deliberately small, nimble, and fully remote — we're a tiny company that does big things. Connect with your calendar and only share the times you want with your customers - they book straight into your calendar. Customers get their own notifications, reminders, calendar invites and more.


Frontend: React, Cypress
Backend: Java
Data: DynamoDB, Redis
Infrastructure: AWS
Architecture & Design: Invision
Process: Beanstalk, CloudWatch Code Management: Git, GitHub

**Must haves:**

- Willingness to work with CYPRESS;
- We don't want you to just write tests, but it's more that we want you to have ownership over the QA process so he can help us identify what tests should be added and so on, apart from writing tests.

We are looking for a "good QA engineer who gets involved", not someone just following instructions from us about what tests to add. We started a relationship with a QA supplier around a couple of years ago. We didn't have automation tests before then, so what was done in that area was to create a test suite (mainly in Cypress, but also has some Playwright and Supertest tests). All the work was done in "catch-up" mode, as the tool was already built before. This means the Engineering and Product team were telling the QA automation tester what tests to build. Now that we have a good test suite, we want to include QA automation as part of our development process. For that, we need someone who will own this process. We expect this person to be able to talk with the Product and Engineering team, anticipate what's coming, agree on the QA strategy and decide together with engineering what should be tested at what level, and then implement the automated tests in Cypress.

**An example of upcoming work:**

We are re-writing part of our tool from scratch for which we will need to review the existing
Cypress tests, and agree with Product and Engineering on what would be the best approach to follow to test it. Should those tests be re-used for the new application? Does it make sense to reduce the number of Cypress tests and ask developers to add unit tests instead? What can we do to reduce manual testing for this new application?... All these are questions that will need to be answered and we would like the new QA person to be involved in those decisions, as none of us are QA experts.

**Who are we looking for?**

A QA specialist who drives the QA strategy, and is in charge of the QA automation test suite.
This person will work closely with the rest of the QA team, Product and Engineering teams in     order to implement the QA strategy in the most efficient way.
What you will do in a typical day:
● Work closely with the Product and Engineering team to understand what changes will be
implemented and driving the test strategy on how better test those changes;
● Work closely with the QA manual testers to identify scenarios what are worth automating in
order to reduce manual testing;
● Contribute to problem-solving in the QA area;
● Daily monitoring and maintenance of our QA build for automation tests;
● Add and maintain tests as needed;
● Continuously improve the QA culture as you go along, refactoring and proposing solutions.