About Status
Status is building the tools and infrastructure for the advancement of a secure, private, and open web3.
With the high level goals of preserving the right to privacy, mitigating the risk of censorship, and promoting economic trade in a transparent, open manner, Status is building a community where anyone is welcome to join and contribute.
As an organization, Status seeks to push the web3 ecosystem forward through research, creation of developer tools, and support of the open source community.
As a product, Status is an open source, Ethereum-based app that gives users the power to chat, transact, and access a revolutionary world of DApps on the decentralized web. But Status is also building foundational infrastructure for the whole Ethereum ecosystem, including the Nimbus ETH 1.0 and 2.0 clients, the Keycard hardware wallet, and the Waku messaging protocol (a continuation of Whisper).
As a team, Status has been completely distributed since inception. Our team is currently 150+ core contributors strong, and welcomes a growing number of community members from all walks of life, scattered all around the globe.
We care deeply about open source, and our organizational structure has minimal hierarchy and no fixed work hours. We believe in working with a high degree of autonomy while supporting the organization's priorities.
<div class="careers-block__trix external-panel text-left">
The role
Status Desktop is currently in beta for Mac, Windows and Linux platforms. Current product focus is on the privacy-centric messenger and group chat functionality, and we’ve just kicked off development of our new ‘multi-chain from the ground up’ crypto Wallet. ÐApp browser and blockchain node functionality will follow next. Status desktop is currently built using Nim & QT for the frontend, and it shares a common backend with Status mobile that is written in Go. We are currently in the middle of a large refactor of our architecture. This refactor includes transitioning the QT front end from Nim to C++, moving all business logic to our status-go backend, and upgrading from QT5.14.2 to QT6.2. As we work in the open and are fully open source you can get a better idea of who we are and the work we are doing by browsing our team wiki here and taking a look at our Status Desktop, Status Desktop QML component library and Status Desktop and Mobile Go backend GitHub repos. You can find more information about our desktop effort in this blog post.
The desktop team is looking for a QA Test Engineer to help us create a Status desktop product with consumer level quality. In this role you will be working closely with designers to fully understand the design vision for the product, and working with the product and devs to identify, reproduce, document and communicate the bugs and issues that need to be solved. The desktop team is spread out in North America, Europe and Australia, with crossover work hours being the European timezone afternoon on Monday, Wednesday and Friday. Work is async using Status, Google Meet and Github, typically in Scrum Sprints.
Responsibilities
- Identify, record, document and track bugs (functional bugs, perf. issues, ensuring implementation matches designs, janky transitions, etc…)
- Help developers with extra testing of the new features to help them identify issues and root causes
- Perform thorough regression testing when bugs are resolved
- Create detailed, comprehensive and well-structured test plans and test cases
- Estimate, prioritize, plan your testing activities
- Participate in the prioritization of the backlog of bugs/feature
You ideally will
Don’t worry if you don’t meet all of these criteria, we’d still love to hear from you anyway if you think you’d be a great fit for this role!
- Be located in a timezone between GMT +/- 4 hours
- Have experience testing desktop applications for Windows/OSx/Linux
- Have experience testing mobile applications
- Have experience creating test strategies and manual test execution: provide artifacts of a test case, test plan, check list, bug report
- Have Github knowledge (ability to distinguish between branches, releases, what a pull request is, commit, etc)
- Have the ability to work with Figma and other design tools
- Have experience working with TestRail
- Show a strong alignment to our principles: https://status.im/about/#our-principle.
Bonus points if
- You show a strong interest for blockchain and have a good understanding of Ethereum
- You have prior experience with automated functional testing, and in particular using Squish for automated testing of QT apps
- You have experience designing and implementing scripted automated testing tools, and in particular Froglogic Squish
- You have worked in a distributed environment that values asynchronous communication
- You have experience working in an open source organization
Hiring process
- Introductory conversation with member of the Talent team
- Interview with QA Team Lead
- Interview with QA Engineer
- Interview with the Program Lead