Video: When is Sourcing Actually Hacking?

If you’re a smart and creative sourcer, be careful. It’s easy to cross the line into what could legally be considered hacking. Today, on the SourceCon Live Google+ Hangout ON AIR, we were joined by Nicole Strecker. Nicole is an attorney who also happens to be a knowledgeable sourcer. 

DISCLAIMER:  This article and any links provided are for general informational purposes only and should not be construed as professional or legal advice. Receipt of these materials does not create an attorney-client relationship nor is it a solicitation or advertisement to provide legal services.  The views expressed in this article may be outdated or repealed by current law. Do not act upon this information without seeking professional counsel in the appropriate jurisdiction.

Article Continues Below

Jeremy Roberts, SPHR, is VP, Customer Experience at HiringSolved. He is the previous Editor of SourceCon. Prior to joining the ERE Media team, he spent over a decade working as a recruiter, sourcer, and sourcing manager. This time was spent in diverse environments, including third party agency settings (retained and contingent), recruitment process outsourcing (RPO) providers, and internal corporate HR departments. His previous employers include the MHA Group, Ajilon Finance, Korn Ferry Futurestep, Raytheon Space and Airborne Systems, and Randstad Sourceright, US. He resides in Corinth, TX with his wife and 3 children.

Topics

5 Comments on “Video: When is Sourcing Actually Hacking?

  1. For those that are not going to the first SourceCon – where can we get information to pass on to CEO of company regarding this topic to ensure we are not “sourcing” and getting into illegal action/issues? I don’t know what this advanced API stuff is or anything taught beyond normal AIRS/Boolean course work- should we be concerned with Boolean search and normal sourcing methods? What is the future of sourcing should laws be established? Are there going to be any guidelines established for sourcers to protect ourselves so we do not have any issues?

    1. There are laws against accessing systems and information for which you are not authorized, and these vary depending on where you live. Obviously, you do not want to get yourself involved in any sort of illegal activity.

      However, there are gray areas. What if a company unknowingly leaves private information on a public server? What if a hacker group dumps the contact information for the engineering department of your competitor to the web?

      I’d say the best bet is to check with your legal department before proceeding in these circumstances.

      1. Well, lol, we don’t have a “legal department” our company is less than 50 people. Talked to COO today, all these “techy things” that are being addressed are probably things I am not aware of, such as API – whatever that is. I am assuming if we are only using Boolean type searches or those taught by AIRS and Boolean experts we can be safe. Worse case if I ever goofed up, which it sounds like I have no idea what stacking or anything else, I am sure company would assist with any assistance needed. I can say I honestly didn’t understand 95% of the items discussed in the video… I still would like to locate someone to discuss what I am doing to ensure no legal issues at all…

Leave a Comment

Your email address will not be published. Required fields are marked *