I call a roadtest "a product review." That's how I describe it when I speak with our sponsors. And that's what the roadtest sponsors want: someone who can take a look at their product, experiment with it, and then write about those experiences and make some conclusions based on those experiences.
You don't need to be a genius to be a roadtester. Granted, some roadtests require specialized knowledge, such as FPGAs. But I always try to run roadtests on products that anyone with a basic electronics or engineering skill level can handle. A good example of what I'm talking about is this roadtest: Multicomp Pro Non-Contact Voltage Tester
Some roadtests require a little more skill or the desire to use the roadtrest as a way to build your skills. This is a good example of that kind of roadtest: Arduino Nano 33 IoT Embedded Dev Kit Now, there are many members who have a passion for Arduino products. So, even someone who doesn't have a lot of experience with Arduino products can get some help right from the element14 community. Remember, you have to ask for help. Use the comments section on the roadtest page to ask questions; it functions as a de facto support community. Our sponsors want to get feedback by people who aren't geniuses. They produce products and want to understand how all skill levels experience their products.
Some roadtests require an extra brain (my words). This is a good example of this kind of roadtest: Intel Neural Compute Stick 2 If you had no experience with this kind of product, you have to think about whether you can build enough expertise in 60 days to review it. This may not be a roadtest that is your "best fit." That's fine. Expertise in today's world is specialized.
Picking a roadtest to apply for has a lot to do with you figuring out what roadtest is your best fit. Once you have figured that out, you need to communicate in the roadtest application that you have the basic skills and you have a plan for roadtesting it.
RoadTest Program Manager