We want it to be playable by people who have demanding commitments like families, jobs, etc. This affects our level design (the first six will actually time out after 30 minutes; they're beatable with the right script in seconds or minutes after you get it working or by hand in ~10 with play at least as good as mine) and how we go about executing on the business.

Ultimately the mechanics of our matchmaking come down to "Starfighter spits a heck of a lot of signal about you at Thomas/Erin/Patrick; we try to decide if it makes sense to introduce to to clients and, if so, to which." All of us are working parents. We will certainly not penalize people for prioritizing piano lessons over being one of the first 5 people to crack a new level.

I won't commit to "I'll never look at time between a level is first opened and when it is solved" but, as somebody who has fed his family with code for as long as I've had a family, that strikes me as being among the least interesting things I could possibly learn about an engineer's ability.