Modern Tribe’s QA team works on a lot of cool projects: over the past year alone, we’ve tested sites built by our dev team for big-name clients including Columbia Law School, Bon Appetit Magazine, Eventbrite Academy Blog, Harvard Law School and What Should We Do (WSWD). (Want to see how we did? The links above highlight some of our work). And that’s not even including our family of WordPress plugins led by The Events Calendar.
We’ve got a slew of cool projects we are working on in 2020, and need another member for our QA team. If working on high-profile sites for large clients gets you excited and a serious case of attention to detail is your jam, we should talk.
Who You Are
We love working with each other because we have built a culture that suits us well. We work primarily with freelancers and coordinate their talents for large projects. To be on our team, you must be:
- HAPPYWhere there is a will, there is a way. Having a positive disposition allows us to achieve great things and to support each other.
- HELPFULAlways looking for ways that you can help others.
- CURIOUSIt is essential that you have a passion for learning. Technology changes daily, and life has a way of constantly raising the bar.
- ACCOUNTABLEOur clients expect us to get the right thing done on budget and on time. Communicating expectations and meeting them is the cornerstone of success.
- A FREELANCERThis means that if you live within the USA, you will also maintain your own personal client list and that Modern Tribe will only comprise a portion of your total income. Regardless of where you live, you need to be already freelancing.
QA is responsible for ensuring all aspects of quality at Modern Tribe. It’s a tall order for sure: learning how a site works, creating test plans covering obscure use cases, and then putting it all into practice when testing every aspect of site functionality…it’s a lot of ground to cover. But we’ve got an established workflow down that helps make sure we’re setting the team up with the tools they need to proceed and succeed.
Though every project is different, here’s the gist of our QA flow:
- KICKOFF MEETING.Just a kickoff — meet the PM; get your questions answered; set expectations; and schedule milestones.
- PREPARING DOCS.Getting started with internal documentation early is hugely important to getting the project into your brain.
- REVIEW APPROVED COMPS.Before you start QA or even get a walkthrough, you’ll review the comps to understand the project + prepare a list of questions to ask on the QA walkthrough.
- QA WALKTHROUGH.Once development is far enough along for QA to begin, you’ll do a walkthrough with the lead developer to get an overview of the functionality.
- PREPARE QA CHECKLIST + TEST PLAN.After seeing each component of the site in action, you’ll put together a first draft at a comprehensive QA checklist and a higher-level overview of what you’re planning to test, in what order, and when.
- HEAVY DUTY TESTING.You’ll put the site through its paces and give it a few rounds of full pass bug hunting. Beyond just hitting buttons, you’ll be thinking from a higher level: are there usability concerns? Does what we’re doing here actually make sense as the best way to solve the problem? etc.
- CELEBRATING A SUCCESSFUL LAUNCH.What feels better than kicking back after a successful launch? If QA has done their job, the project will launch smoothly, the team will have a finished product to show off, and — most importantly — the client will be happy. It doesn’t get much better than that.
* Our QA team also generally leads client training and prepares training documentation/videos when appropriate, so be prepared for some direct client communication.