[ineptech]

4. As a hiring manager, I'd need different "profiles" for each team (one team mobs 24/7, another almost never mobs, etc)

5. What I would want as a candidate (a blunt and specific "warts and all" description of the team I'm joining) is not what employers would provide (vague, HR-y generalities like "we use cutting-edge technology" and "we prioritize work-life balance"). This was what turned me off from KeyValues.

But I hope these are tractable, because I very much like the OKCupid model and would use the product if these could be solved.

[BrianOnHN]

Good additions. I'd like to add that these are all challenges that will be faced by all competitors of the existing model.

Personally, that's what lead me to focussing on what might be the most innovative direction I can fathom instead of the incremental direction (aka "this for that" innovation). If I didn't recognize that all of the challengers would face this same uphill battle, then I myself would've built "OKCupid for jobs" by now. It would 10X the pure-spam nature of the current market if the execution was done well, but current players are too big. To conclude, you have to outthink them and create something that can't be reproduced with effectively unlimited budget.