Quality Assurance Engineer

---

Job Description

Tofugu is looking for an experienced Quality Assurance Engineer. Because we're looking for someone to guide and develop our QA process, we are looking for someone who is at or near the top of the software testing field or has the potential to get there. In addition, candidates should have deep experience with test tools (e.g. Capybara), as well as knowledge and understanding of HTML, CSS, and Javascript. WaniKani is built on Ruby on Rails, so some background or ability there is considered necessary as well. Being a Japanese learner and/or a past or present WaniKani user is a plus, but not required.

This role will work closely with the Engineering team to test new features and do regression testing on existing features as code gets updated and bug fixes are made. For example, right now, we are refactoring our front-end code to make WaniKani more flexible for future plans, so you would be working on that. At the same time, you'll be directing, developing, and improving our test processes in preparation for what comes after: new features that we think will have a direct and positive impact on the tens of thousands of learners who interact with WaniKani and Tofugu. You'll be a big part of that!

Responsibilities

• You will determine the best, most efficient way to test new WaniKani features and define the testing standards for the site.


• You will recommend, decide on, and implement tools for executing the test process with the rest of the engineering team.


• You will create and document the WaniKani test process.


• You will test with accessibility in mind. Our properties aren't perfect in this regard, but we do our best to code for different people and different circumstances.


• You will test with security in mind, too. Our users' private information is, of course, extremely important!


• You will implement, where it makes sense, test automation to improve test efficiency. You should be able to provide good feedback to our engineers and help bring up the quality of our overall product.


• You will advocate for WaniKani users. "Hey, this isn't working how it's supposed to, and let's fix this!" or, "I think xyz would improve the learner's experience and help them to make more progress in their goals of learning Japanese."

Qualification

• Can use QA tools (like a browser stack) and use them well. You can set up various browsers for testing on different devices


• Have experience with Javascript, HTML, CSS, and Ruby.


• Are near the top of the software testing field — or make us feel you have that potential.


• Have a decent eye for design, color, and whitespace and can spot when spacing or color is off.


• Enjoy working with and collaborating with a team, but you're also a self-starter who takes initiative and can get work done.


• Are not bothered by ambiguity. If left alone, you know what the important stuff is and can take the initiative to figure out how to create value.


• Can speak your mind while at the same time graciously (and happily) accepting feedback.


• Are good at, and not afraid to, provide feedback to others, as well.


• Work pragmatically. That is, you get the work done with organized, efficient, well-documented, processes.


• Have a passion for delivering quality to our WaniKani users


• Can identify what is important for actual progress, then do it, even if it isn't always "fun." Don't worry, there's fun stuff to do, too.

About Tofugu

Almost everybody at Tofugu has taken a Japanese (or English, or French, or whatever) class or had tutors. But we experienced a lack of explanation and had to move at the speed of the slowest students. We learned kanji by writing them hundreds of times because "that's just how it's always been done." We all thought there must be a better, more effective way to learn Japanese, even if it's not "traditional." So we began writing. We learned how humans actually learn and made WaniKani for learning kanji because sometimes tradition is overrated.

To supplement our studies, we turned to textbooks and the Internet. Though practical, we found them to be overly-dumbed-down. "This is just the way things are," they said. When we dug deeper into linguistic papers, we found the answers we were looking for, but they were way too weedy and technical for the everyday Japanese learner. So we kept writing, and we've been bridging the gap between Japanese linguistics and you, the Japanese learner, ever since.

We are building tools and writing about the Japanese language for our past selves: people who were (and still are) excited about learning. Then we are sharing everything we can with you. We want to be the Japanese teacher we never had, for you.