Senior QA Engineer in Petcube

In the midst of the pandemic, we successfully launched the new Petcube Cam. It is now selling so fast that in the past, minor defects have become a major constraint on growth. That's why we are looking for an experienced QA for system quality improvement from apps to backend and firmware. ** About our team ** We have been creating IoT products for pets since 2012, and we strive for the level of quality that Apple has set in electronics for people. With the growth of camera sales and subscriptions, we are expanding our product team, primarily QA and developers, to maintain and improve the quality of our products. ** Why it's great with us ** * We have gone through a startup from 0 to 1 through several crises and with each new product we raise the level of quality. * Our business = Internet of Things + SaaS for tens of thousands of users, and here is everything: hardware, firmware, backend, apps, video streaming, payments, chatbots, ML. * In our team for a year you can get such experience, which in other products accumulates in three, not to mention outsourcing. * You will have all the support of the team and there will be NO bureaucratic barriers to make the products even better and the team interaction even more effective. * Now we work remotely, and we have a cool "Lab" with a farm of cameras, chips and other reasons for socialization * When our technology can understand dogs and cats better than people, we can immodestly remember our participation in this breakthrough ** Who we are looking for ** Quality Assurance engineer with significant experience, zero-tolerance to defects, system thinking, open / open in communication, able to balance specialization and generalization in the team. And it's not just words, we decompose below. If most of the points about you, write right now, let's get acquainted! ** Experience ** * 3+ years in QA. * CV without excessive modesty shows professional glasses and continuous development. ** Quality Assurance ** * Your work habit is to avoid bugs while discussing the product. * Understanding the difference between QA and QC encourages you to improve team processes. * Developers tremble when you come up with clarifying questions, and adore your ability to clarify unobvious cases. * Black / gray / white box, smoke / regression, unit / functional / integration / performance / usability is not a theory for you, but methods of finding the optimal approach to testing product components. * Created / created testing strategies, test cases / suites / runs, release processes. ** Engineer ** * The product stack is not as important as its components and their interaction. * You have your own set of proven tools, you are not afraid to try * new ones and give up inappropriate ones. * You like to hurt the API, you have SQL, you talk about microservices, queues, cloud infrastructures. * I know Charlie, Jason, know how to use SOAP without water and how to take some REST * You know arithmetic without a calculator. * Challenge engineer solutions if required by product quality. ** Zero-tolerance to defects ** * Your escape rate is not zero only due to the combinatorics of non-functional conditions and ultra rare bugs. * Helps the team capture and find any suspicious behavior without turning the backlog into a dump. * Your worst enemies are zombie bugs and regressions. ** System thinking ** * You like to decompose and prioritize. * Helps the team choose the best quality maximization strategy. * The product for you is a multi-component system with probable breakpoints. As, however, and team processes * You (a) look in the technical metrics which cause suspicion, and offer expansion of tracking. ** Openness in communication ** * You turn constructive criticism into action, you turn non-actionable feedback. * You see the problems and offer solutions based on objective limitations. * You prefer direct communication, but keep the necessary level of formalization for quality & traceability. ** Balance of specialization and generalization in the team ** * For you, the agreed responsibility is more important than the formal position. * If the team lacks narrow expertise, together you find a way to block it. * When needed, you enlist the help of developers for testing, and help them debug in real time. * When you find a hole in the heat - you offer the team a solution, not just wrap a bug with AR / ER differences. ** Company website ** www.petcube.com