Two Questions to Ask Every Beta Applicant

Preface: We’re assuming that you’re recruiting via an online form, survey, or similar tool that allows you to query your applicants. As long as you have the ability to add a couple of free-form text entries, you’re all set.

The two questions we recommend asking every beta applicant are simply:

  1. Why do you want to beta test this product?
  2. What makes you a great beta tester for this product?

That’s it. The answers to those questions will get you about 80% of where you need to be to identify the top beta candidates from any group. The basic idea is that the effort and style put into these answers is an early indicator of how effectively that person will perform as a tester, allowing you to filter the best and worst candidates early, with minimal effort.

Two Questions to Ask Beta Applicants

Question 1: Why do you want to beta test this product?

  • Why you ask: Many people believe that beta testers participate just for the incentives (e.g. free product). While this is true of some, it’s not the case for most — and filtering those reward-focused candidates out of your pool is essential.
  • What you’re looking for: General enthusiasm for your product and/or company. For many products, you’re looking for people who are trying to solve a problem they currently have. This is especially true when it’s a new version of an existing product. Above all, if they mention an incentive in their answer – they’re out (although the honesty is appreciated!).

Question 2: What makes you a great beta tester for this product?

  • Why you ask: It’s important to identify how the candidates see themselves. Ego is a bad sign, and generally an unfavorable trait in a beta test. These types of personalities can turn off other testers, poisoning participation as a whole.
  • What you’re looking for: Creative applicants who answer inventively and go beyond listing previous beta tests they’ve participated in. Applicants that clearly represent the target market of the product should lead the pack.

What you’re looking for from both answers:

  1. These answers should never be required. Users who decide to ignore either or both of them are simply out of the pool.
  2. Spelling, Grammar, and Punctuation all count. These devices make both skimming and reading easier and faster, and nothing is more important when reviewing countless bugs, suggestions, forum posts, and survey replies. In other words: ALL CAPS? OUT. no caps? out. No punctuation out. Bed Spllng. Owt.
  3. There should be some substance in their answer. 1-2 lines can be a strong answer if they’re a great writer, but in general, a solid paragraph of 3-5 lines indicates that they’ve included enough thought and detail to take the question seriously.
  4. Too much text can be a problem, but not always. If it’s well written, fits the context, and gets a solid point across – that’s fantastic. If it’s 14 paragraphs but could easily be one…move along.
  5. Make sure they actually answered the questions. While this may seem obvious, you’re looking for more than style here. These questions provided your applicants with their first opportunity to show you that they can clearly follow directions — a key attribute in a beta test.
  6. While critical thinking and creativity may be hard to identify in such simple questions, there will be times you’ll notice it. Move them to the head of the pack.
  7. Honesty is hard to identify on a beta application. These questions can help, as once you’ve narrowed your candidates down, it’s useful to ensure these answers align with other demographic and technical questions you’ve asked.
  8. Most importantly, each question ends with “for this product”, aiming to rein in their answers to the context of your beta test. Pay special attention to those that latch onto that, and focus explicitly on the things relevant to the specific product they’re eager to test. These are good candidates, as they clearly demonstrate their place within your target market.

While reading hundreds of individual free-text answers may seem inefficient (and potentially frustrating and/or dull) at first, these questions offer an enormous amount of insight in a very small space. Remember that regardless of how well the product being tested performs, it is the performance of these people that will determine how successful the beta test of that product is.

We’d love your feedback on these questions, as well as any others you feel would be useful.

Request a demo of the Centercode platform!

You Might Also Like

  • Pingback: Tweets that mention Two Questions to Ask Every Beta Applicant | Centercode Blog -- Topsy.com()

  • oOBetaTestOo

    These are good answers to the questions, I have always wondered what to put as an answer this has helped.
    It should be noted though, that it is rare to be able to tie a CenterCode test down like this, more often than not
    their is less information available about what, why and when about the tests. If their was more detailed information
    available then you could as in these examples answer the question/s properly.

  • https://www.centercode.com Luke Freiler

    We’re dealing with a unique catch-22, in that generally we’re required to keep our clients identity and product confidential until tester selection is complete and NDA’s (confidentiality agreements) are issued. This isn’t something most companies have to deal with (e.g. If you apply for a test at TiVo, you’re probably testing a TiVo product, and probably love TiVo). We try to focus on the product category and a bit of text about what type of person we’re looking for. We’re also in the process of revamping our style a bit to address that issue which should help out.

  • http://twitter.com/oOBetaTestOo oOBetaTestOo

    Thank you for the illuminating comment, I appreciate the catch 22 position you are in.
    Perhaps you could put in place a min NDA where we agree to keep the clients confidentiality while allowing access to test information. I do appreciate that your illuminating post was probably based on Job postings, and you would be correct in saying what you do say, but your post was most illuminating towards the centercode process.
    May I thank you once again, and keep up the good work.

  • Pingback: 5 Ways to Increase Beta Tester Participation | Centercode Blog()

  • Pingback: Mike Fine Talks Beta Recruitment on The Startup Slingshot | Centercode Blog()

  • Pixel Junky

    can someone post a template we can copy paste in all applications