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; the p2p communication layer for Web3.
As a team, Status has been completely distributed since inception. Our team is currently 200+ 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.
After a pause during which the Status team focused on our mobile application, the development of Status Desktop was restarted in 2020 with a clean sheet QT / QML UI codebase.
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.
- 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
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!
- 3+ years as a QA test engineer
- Experience in testing Qt/QML applications
- Experience in testing desktop applications for Windows/OSx/Linux
- Experience in creating test strategies and manual test execution
- Experience with open source development workflow (including github)
- Self motivated, strong sense of ownership and result oriented autonomous worker, you’re willing to try new builds/features as many times as it’s needed to make sure they finally work :)
- Good communication skills in english
- A strong alignment to our principles: https://status.im/about/#our-principles.
- You show a strong interest for blockchain and have a good understanding of Ethereum
- Have experience designing and implementing scripted automated testing tools
- Have worked in a distributed environment that values asynchronous communication.
We are happy to pay in either 100% fiat or any mix of fiat and/or crypto.
The hiring process for this role is usually as follows (sometimes adapted):
- Introductory conversation - Talent team
- Technical Interview with the Hiring Manager - Nastya
- Interview with member of QA Team
- Final interview with, a talk with Product Strategy Lead - John
Status desktop - why and what ? blog post