Jasper provides an API, and engine, to cycle through challenges that will hopefully help identify areas of knowledge or learning opportunities in the user. The challenges are designed to increase in difficulty (or obscurity) as you answer more.
I don't like most interview questions.
I think interviews for front-end developers are broken. Questions are asked and stories are told; the truthy-ness of those stories is completely up to the interpretation of the interviewers. Wouldn't it be better to simply work with the candidate for a while and get real experience with that person?
Jasper attempts to fix the above problem by providing a tool for use in various ways. One way to user Jasper is to include it on a website as an easter-egg to be found by developers. People like to find things and most people like a challenge; developers especially will rise to a challenge to prove their skill. Another way to use Jasper is to include it in an interview where a candidate and another person - or two - can work through the challenges presented. By doing "real" work with someone, a better feel for how working with them might actually be once they are hired.
I think interviews should involve some typical every-day stuff. I think that this would help the candidate relax a little since it should be an activity they are completely comfortable participating in.
To that end, I hope that this library can evolve into a tool that will help us break out of some of that wasted time in an interview. Besides, a lot of questions can be answered indirectly through just working with them rather than them telling a story about their perception of a past event.
Objective of each level in Jasper.
Talk about #Jasper, making a suggestion: