About the role
Posted
You’ll get to
1. Work with us to review the app and create and update a reusable, comprehensive QA checklist.
2. Perform QA every Tuesday and Wednesday on the weekly main release, on mobile web (primary) and desktop (secondary)
1. Clearly document in Slack what work has been done since the previous release version.
2. Clearly document in Slack the pass/fail for each checklist item.
3. Run lighthouse checks on the main app pages to determine if any regression in performance occurred.
4. Clearly communicate next steps to the engineering/product team based on the results of QA.
5. Update the versions of the released packages
3. Depending on availability, QA ad-hoc releases as necessary during the week, though usually only for urgent items.
4. Spend time reviewing the app functionality and code, suggesting ways to improve QA and gain more confidence on releasing.
5. Develop and implement our automated testing plan as we grow.
Who we are looking for
* 3+ years of experience in QA roles, such as testing or building processes for shipping quality software
* A strong attention to details such as design, browser/device specific differences, copy and performance.
* A passion for delivering polished experiences
* Ability to test the application in the top browsers on physical mobile phones (ios and android) and desktop.
* Expert skill level in typescript.
* Knowledge of a wide range of tools, including those geared towards automated testing. Specifically we use: Jest, playwright, supabase, postgres, typescript, React, nextjs, nestjs and docker.
* Excellent ability to document processes and problems
* Be a team player with excellent communication skills
* An “owners mindset”
Bonus:
* A demonstrable passion for tattoos
* Knowledge in some of our front end tooling - React-query, chakra ui.
* Passion for shipping! Someone that loves a fast-paced environment
* Strives in ambiguity. Eager to think creatively to solve problems that are less clearly defined. Taking initiative to seek out and overcome obstacles that may not have a clear path through.
* History of success in remote work
* An understanding of web3 and experience in testing web3 code.