[RomaoP]

Great ideia ! Just two suggestion. Why not try interval approach, the candidate could enter an interval and recruiter another interval, than just check if they intersect. Technically, why not encode the information on the URL avoiding the database ? Keeping the information in some database could bring lot's of headaches :-)

[LuisCampos]

Hey :) Thanks for the comments.

a) Why would the interval approach be better? It's the same thing as checking if candidate min > recruiter max but with some extra unnecessary information?

b) The information cannot be in the URL because the main point of the tool is to hide that information. :)