I understand that's exactly how it works. I was just pointing out the friction points.
The example that I pointed out is a major cognitive leap for an user and you'll see a high drop off rate at that point. For an user like me, I'm happy with my current position for the moment and I haven't thought about what time frame I am looking to make a jump but I may be willing to make a jump if the right opportunity comes along. The question of "When are you available to start a new full-time job?" is a major turnoff for me because I haven't made the cognitive leap to actually apply for a job.
DeveloperAuction should be in the position of collecting as many highly qualified people as they can whether or not they are actively looking. Over time, you can use this database to raise conversion by tempting/teasing the people in your system. Example: "Hey, XYZ, I know you said you aren't currently on the market, but there are these 8 companies that are looking for your EXACT skillset, might you reconsider?" What you'll find is that top talent are never actually "looking" but rather a better offer comes their way.
Also, I'm on the belief that registration forms should not turn people away (via required fields/errors) but rather encourage people to provide more information to gain more functionality (ie "Please tell us these information to submit your profile for review" or "You're 90% of the way there, provide this information to get closer to completing your profile.")
Anyways, just a thought. Best of luck to you guys.