Jeremy Roberts, VP of Customer Experience from Hiring Solved takes the HR Tech stage with Chad & Cheese to talk data and a shocking new announcement.
Do you believe in something so much that you would shut down a product because of that belief?
Hiring Solved explains data, HiQ ruling impact, and why they are shutting down Prophet - their Chrome sourcing extension. Nothing but the best from your beer buddies Chad & Cheese :)
And of course your friends at Jobcase, who supports great EXCLUSIVE podcast content.
PODCAST TRANSCRIPTION sponsored by:
Jobcase: This Chad and Cheese exclusive, HR Tech podcast is sponsored by Jobcase. Jobcase is on a mission to empower hourly workers to achieve work-life success. But don't take my word for it, listen to the words of a Jobcase customer, "Jobcase, there is no one like them. The urgency, the communication, the data, the scalability by brand and by location. The niche versus the standard, they get it all. Jobcase understands our business and the deliverables of high volume hiring teams," Cat Barcelona, Senior Recruiter, Whole Foods Market.
Intro: Hide your kids. Lock the doors. You're listening to HR's most dangerous podcast. Chad Sowash and Joel Cheesman are here to punch the recruiting industry right where it hurts. Complete with breaking news, brash opinion and loads of snark. Buckle up boys and girls, it's time for the Chad and Cheese Podcast.
Chad: Start it off?
Chad: Go ahead. Start it off.
Joel: What's up everybody? HR Tech 2019, let's give it up to this rowdy
Chad: Hey guys.
Joel: Hung over crowd.
Joel: Very nice. We are the Chad and Cheese podcast.
Chad: And we are loud.
Joel: For those of you who don't know, we cover industry on a weekly basis. We do a lot of other fun content. I am your cohost Joel Cheeseman.
Chad: And I am Chad Sowash.
Joel: Is your mic on?
Chad: Is my ... you give me a little bit more?
Joel: Hot mic.
Chad: Gave me more. Oh there it is.
Chad: Man back there is hooking me up.
Joel: I'm surprised a lot of return visitors from yesterday's show, which we were going to do the same content and we said, no, that's not going to work. So we wanted to bring on a special guest, so everyone give it up to Hiring Solved former source con head, Jeremy, you're looking at me like I'm doing this wrong.
Jeremy: You're doing well.
Joel: You want to take it over?
Jeremy: No, you're doing well.
Joel: All right, Jeremy, do you have a nickname? You need a nickname, I
Jeremy: I don't have one. Let's not do it off the fly.
Joel: Racing cap ramer or something, I don't know what it is. All right. Young blue eyes. Because it's the third day and we're taking it easy, we're just going to tap open some Guinness for today. We have a few extras if anyone's interested and to make it more enticing, these are actually from Ireland.
Chad: That's right, Shane Gray from Clinch. [crosstalk 00:00:02:53].
Joel: Can I get a hands up for anyone that wants Dublin Guinness.
Jeremy: Is Shane here?
Chad: He's outside.
Joel: There we go.
Chad: Who wants a beer? Woo, there we go.
Joel: Let's hear for ...
Chad: Guinness, Anyone?
Jeremy: She's even wearing a shirt.
Joel: My name is Shawna Williams. I am ...
Chad: Where's Barry at? Barry wants a beer now. He's over there talking, selling shit. Russell?
Joel: From Dublin dude, come on now.
Jeremy: He's still on coffee.
Joel: All right. All right, so everyone knows who we are obviously. That's really good.
Jeremy: That is good.
Joel: Give us the elevator pitch on you, Jeremy.
Jeremy: My name's Jeremy Roberts. I'm the VP of Customer Experience with Hiring Solved. I've been in recruiting since about 2002 I started off in the agency world and then moved into corporate. I started some sourcing functions with different companies. My last recruiting job, I was a Sourcing Manager for a large RPO and had a team of about 25, and then I moved over to Source Con and I was the Source Con editor and conference organizer for about three and a half years. And from there, I made the transition to the HR tech side and started working with Hiring Solved, so.
Joel: Anyone not know Source Con? Sourcing candidates. Okay, good. So we wanted to bring on Jeremy because there are some really hot issues going on right now with privacy, GDPR, data, profiles, collecting data from all over the web. I want a little bit of a historical perspective of what sourcing data used to look like, simplified. And then we'll get into the dark world that it has become. But I want to set the stage for what 2013 looked like in terms of going out on the internet and getting data.
Jeremy: Yeah, no that's excellent. So basically when I started in recruiting, I remember being in the office and we had to actually, we would print files and resumes. We had what we call back files, just huge file cabinets full of resumes.
Chad: Wow, cabinets.
Jeremy: There was not a lot of electronic things going on.
Chad: Back in the file cabinet days.
Joel: Do you have folders full of women too?
Jeremy: Fast forward, and then we had LinkedIn started and there started to be a lot more data online. So then when I joined as a Source Con editor-
Joel: You don't want to throw this.
Jeremy: When I joined Source Con as an editor in 2013, it was a very manual process. So we were showing people how to go find a profile on a social or professional site, and then how to find them-
Joel: Google query type stuff.
Jeremy: Right and how to use boolean to find all that person's other social presence and then kind of construct this unified profile, and then go find their contact information. If you couldn't find it, how do you guess it? But it was a very manual process. So then in about 2012, 2013 the people aggregator movement started. And I remember we did a panel at the first Source Con I organized in Seattle in 2013 and Sean Burton from Hiring Solved was there. They were launching their first version of hiring solved.
Jeremy: And then we did a panel, people on the panel included like John Bishky from Entelo and Pete Kazanjy from TalentBin. And then we had Dice Open Web, Shravin Goalie was there. And then there were a couple more. So there were a lot of aggregators at that point, and they were all doing the same thing. They were just crawling for public information about people, creating profiles and selling it. And at that point, if you could match a Github profile, to a LinkedIn profile and a Twitter profile everybody was excited. And then if you can find a phone number, they were really excited. So it was pretty innocent at that point. And there was a market for it.
Joel: When did LinkedIn sort of look at this automation thing and say, nah, we're not for that, or we're not happy about that? Like tell talk about the early days of LinkedIn's reaction to the aggregation automation game.
Jeremy: Yeah. So I started to see them right about this time, they were at every conference I organized, they were in the audience kind of listening to what sourcers and recruiters were doing, and I would write an article and then all of a sudden the URL would change. And, oh, they changed the URL pattern now that doesn't work anymore.
Joel: What URL would change?
Jeremy: Well, if you would teach someone how to do something on a social network, and then you publish it.
Chad: URL patterns, right, patterns. Yeah.
Jeremy: So you say, okay, write your search query like this based on this URL pattern, and magically the URL patterns would change.
Jeremy: So I started to notice that in like 2013.
Chad: So that's your whack-a-mole thing.
Joel: The first whack-a-mole was sort of that, right?
Jeremy: If you remember like back when Shally would release his job machine, they would release their cheat sheets, those things would work for years. You would print them and pass them around the office and then you can use those-
Joel: Yeah, that used to be his business card.
Jeremy: Yeah, you could use those Google queries for years. Now pretty much every company with public information, they changed their URL structure and kind of the way everything is out there. So those break in a week or two, you could never circulate something like that for very long.
Joel: All right. So the dawning of the automation game starts, LinkedIn isn't happy about it, starts doing some basic whack-a-mole.
Jeremy: I think everybody did, yeah.
Jeremy: Yeah, everybody did.
Joel: This was around the time, because then Entelo's original model was, we're going to look at LinkedIn activity and say someone is about to leave the company. Right? So they just updated their profile, they added something or they're searching for stuff. So LinkedIn really early said this isn't cool and Entelo had to change their business model. Am I correct on that?
Jeremy: I have no idea on Entelo's business model.
Joel: Okay. I seem to remember I covered their launch and there was something like that.
Jeremy: I do think there were a lot of people who would say they're going to watch everything going on socially to make those kinds of predictions.
Jeremy: I don't think any of them, I don't think the people who are not the owner of that data are doing a great job of making predictions based off social data.
Joel: Gotcha. So at some point in this you guys had some legal, I know you weren't there with the company at that point.
Jeremy: Yeah, I was covering it.
Joel: But there was some legal stuff. Talk about that.
Jeremy: So I was covering it from the SourceCon perspective, and there are a couple of good articles, and there's Matt Charney wrote one a on Recruiting Daily and then I had some on Source Con and there's an interview I did with Sean before I worked at Hiring Solved right after the case settled. So if you could go find those, that would be-
Joel: What were they mad about?
Jeremy: Due to the ... Basically they just don't want people crawling their site and repurposing the data.
Joel: So you guys settled out of court.
Joel: Terms not to be disclosed.
Jeremy: Due to the terms of our legal settlement I can't go into a lot of detail.
Jeremy: But one of my favorite things about Hiring Solved, this was before I worked there, they had to destroy the servers and they actually went to the desert, as a part of the settlement they had to destroy the servers and instead of just deleting the data-
Chad: Like office space.
Jeremy: They went to the desert and blew it up with military grade weapons.
Chad: Yeah. C-4, yeah that's cool.
Jeremy: It was pretty awesome. So that was a pretty neat way to do it.
Chad: Take that god damn fax machine out to the desert. Yeah.
Joel: So the birth of more sites like this come about. We have SeekOut, Hiretual. You could go on and on.
Jeremy: Yeah, no, it's gotten really popular.
Joel: And then there's a case with HiQ, a site that does that similarly, and then they currently won again against LinkedIn to basically have these profiles available to scrape and use. What's sort of your take on that legal decision, does LinkedIn give a shit? They're just going to keep whack-a-mole and make it harder and harder to scrape, we'll get to a point where the data is already there, so no one cares anyway. But talk about the case with HiQ, what LinkedIn's status is now, where are the other companies that are scraping data, how they feel about this decision.
Jeremy: Yeah. Well first off, can I go back and then if I don't answer the question?
Joel: You're our guest man, you can do whatever you want.
Jeremy: Okay, I want to go back a little bit. So 2013, it was pretty innocent. Everybody's just gathering this information, creating unified profiles, adding contact information and selling it. That was just, it was new, it was exciting and everybody was excited about whatever you could provide them. Fast forward, there are all kinds of data breaches on the internet and then wow, these Chrome extensions right after that big breach that was in the news, there are a bunch more email addresses on the Chrome extension out of Poland, or wherever. And so as this has happened, the data is becoming more and more commoditized. If you guys have been paying attention to the news, there's a file that was found on AWS with 400 million cell phone numbers from Facebook.
Chad: they tie to profiles, right?
Jeremy: Tied to profiles.
Chad: Tied directly.
Jeremy: Directly to profiles.
Chad: So they're not just numbers.
Jeremy: Not just phone numbers.
Joel: Let me repeat that, 400 million.
Jeremy: 400 so that means your cell phone numbers.
Joel: There's 325 million Americans.
Jeremy: Have been released.
Chad: Thanks, Facebook.
Jeremy: So not this guy's.
Jeremy: So, anyway, the point of this is, this was because of ... It was a bug in the system. Basically if you put a phone number in, it would say, yes, this phone number belongs to this profile and this person, it would show the person's face and then you can match that with the LinkedIn profile. So now you know the number associated with that profile, and there are about 600 million phone numbers in the US, so you could write a script and bring back every phone number and which profile it's associated with in a very short amount of time.
Jeremy: And so at Hiring Solved, we knew about that. Irina Shamaeva, if you guys know Irina made that knowledge ... She basically pointed it out to everybody that that was possible. So Hiring Solved knew how to automate that and we never did anything with it, just because ethically it's a little odd. There are kids in numbers in there and you can't control what people do with it.
Chad: Well taking stolen data-
Jeremy: That's not stolen.
Chad: It's just public.
Jeremy: It's public.
Chad: Just public.
Jeremy: But if it's kind of a gray area, I don't think there was anything illegal about it, it was a bug.
Chad: Wasn't illegal.
Chad: Man, that just doesn't feel right.
Jeremy: It doesn't feel right.
Jeremy: So situations like this have, in my opinion, made data, public information like this, it's very commoditized marketplace. At this point, we've got the early people to the game in 2013, the TalentBin, Intello, Hiring Solved. We were all kind of doing it on a more innocent level. At this point it's gotten a little bit shady, and the ones who win are going to be doing things that others might not feel comfortable with. The good news for the consumer is the price is going to go down. Everybody, imagine all the people who heard about that file and are hacking away building a Chrome extension right now in some little apartment.
Jeremy: In the Soviet Union.
Chad: Everybody's doing it.
Joel: I think that's an important message, is that developers, hackers, whatever you want to call them around the world now know how to create databases with this information of cell numbers, profiles, data, where you work, all that information.
Jeremy: Oh yeah, well there was a Business Insider article about it.
Joel: That's a mainstream publication. That's not some hacker black hat stuff.
Jeremy: And then on, I think it was Hacker News, there was a, how to crawl everything.
Joel: So are we going to see an influx of these tools of Chrome extensions
and sites that you can search all this data for whatever purpose you want?
Jeremy: Yeah, absolutely.
Jeremy: I would say there are a bunch, the price is going to go down.
Joel: Okay. So for the companies in this expo hall that make their living on that data, as that gets commoditized-
Chad: Where are you at?
Joel: Prices get cheaper, but so do profits, profits gets less, right?
Jeremy: Yeah, a lot less.
Joel: Not only your own company, I mean you're in this universe as well. Your decision of what to do about it is one thing, but as a whole, are we going to see more solutions here at HR Tech for finding data? Are we going to start seeing less because there's no money in it?
Jeremy: I think you'll see less. I think they're going to start to disappear. So the great thing about being an early entrant to this space, so our founders are, when they gathered, we had about 500 million profiles starting in about 2012, and so they connected those to neural networks. So our algorithms have been learning from that data since 2012. When I joined in 2016 we were complete, all of our revenues came from selling data. But the algorithms used to manage that data were getting smarter and smarter. And then so today, luckily we've transitioned our business model to where we're using the algorithms, the search and match and find me, you know, here's the job description, which person is best for this job based on all of these profiles? I mean it's trained on those 500 million profiles, but now our revenues, the majority of our revenues come from enterprise data, so large ATS and CRM systems and matching and managing that data.
Jeremy: So we're no longer dependent on data sales, so it's great to say as-
Chad: Big data is everywhere, everybody has big data.
Jeremy: Yeah, everybody has it now.
Chad: Again, you can't make money off of it. So therefore you guys are looking to make a smarter way, or you are making a smarter way to make that match against the job description versus all the candidates.
Jeremy: The job description using all of your ATS. So you've got 3 million in your ATS, 500,000 in your CRM and you've got a 2 million from a legacy ATS.
Chad: So it's your database. Gotcha, yeah.
Jeremy: So which is the best from all these candidates you already own. That's what we're using it for now.
Joel: Now, you guys have a really popular solution called Prophet that's a Chrome extension that a lot of people use. Are you guys going to keep that around? What's the future of that?
Jeremy: I think it's safe to say that we'll be moving on from that.
Jeremy: In the very near future. We'll take care of clients with contracts. But I think as other tools get deeper and richer with data that we're not willing to use, it's like
money that hasn't been laundered.
Joel: How many sourcers use Profit right now?
Jeremy: How many people use Profit?
Jeremy: I think 50,000 per month, active users.
Joel: Okay. There might be a few pissed off users.
Jeremy: Most of them use it for free.
Joel: Okay. Fuck them.
Jeremy: But I think that there will be other alternatives. If you're just going after a phone numbers and email addresses, I think there are going to be quite a few alternatives.
Joel: Let's talk about the privacy, the regulation side of things. So last year Europe implemented GDPR, which were some really strict privacy rules. What was your company's response to that? What does that mean for sourcing there and the new California rule that's as close to GDPR as we have in the States, and do you have any predictions for what the United States will do to follow GDPR? Are we going to be independent from that? Separate from that? What are your predictions there?
Jeremy: Yeah. Well first off, this goes back to the public information thing. So if you follow GDPR to a T on the public information side, it's really risky. I mean there's a lot of rights, so holding that information, being the controller of that information is a pretty risky thing. And it also, it creates, you have to get an opt in to deal, there's a lot around that. So it makes the public information piece even more difficult. And then when you're dealing with ATS and CRM data, it makes it a lot more of something that we can handle because we are just the data processor and that situations. So we have a ton of-
Joel: What was your company's response to GDPR? Which I thought was interesting.
Jeremy: Yeah, so we're GDPR compliant and basically I am going blank on the ... I was in on-
Joel: So we interviewed Sean last year at your annual event, and he had announced that, I think it was 29 million profiles that you just said they're gone, because when they're going to deal with this stuff.
Jeremy: Yeah, we did, we deleted them and just didn't even want to fight that fight. So other people-
Joel: Did other vendors follow suit?
Jeremy: No, I mean I think there were some that they would, you know, hey, here's a profile and then you would click on it and it be like-
Chad: But that fight is still going to be fought here in the US.
Jeremy: Yeah, so it'll happen here too.
Jeremy: Yeah. It would be-
Chad: Is that going to be just a public dump of all your data and then you're just going to serve off of the ATS data or the client data?
Jeremy: Yeah, eventually, that's why we're moving more towards ... Luckily the algorithms are trained, we're having success and yes. So yeah, we would eventually, we're in a position to walk away from it now.
Chad: Right, right, right.
Chad: So do you think other companies will actually follow that lead? Because this is really kind of a squirrely-
Jeremy: If the have a ... At this point we're not dependent upon that revenue stream anymore.
Chad: That data. Right.
Jeremy: So we can do it right now, and we've been working hard to make that trans ... When I joined in 2016, that was my biggest anxiety because I had been at Source Con reading about GDPR and hearing all of this, and I knew that that we needed to evolve. I call it an evolution instead of a pivot because we didn't ever turn, we just kept growing forward.
Chad: You're doing the same thing, it's the data that you're using.
Jeremy: At this point now that we don't depend on those revenues, we could turn it all off today and it wouldn't affect us. I think people coming into the space right now within the last two years, crawling Github and get selling phone numbers and things like that, I mean if their revenue stream is 80% dependent upon selling data, they're going to have a hard time making the transition.
Chad: So the Seek Outs of the world, they are totally off of LinkedIn and Github. That's where they get all their data and it's all public data. I don't believe they have their own database. Right?
Joel: Yeah. I think all those companies that are funded and here in exhibiting, real companies are going to have to follow your example of how do we survive a world where this is a commodity.
Chad: Especially if I'm making money just doing that.
Joel: And where this is illegal to me.
Joel: To me, and correct me if I'm wrong, if anything close to GDPR hits the US, that thing, that's an asteroid T to the industry of sourcing automation.
Jeremy: Well it becomes an opt in world. I mean it's back to job boards. No, seriously.
Joel: You hear that job boards? You're back baby.
Chad: You're back.
Jeremy: You're coming back.
Joel: CareerBuilder can't hear us.
Chad: Job boards are back.
Jeremy: They're in the front corner.
Joel: 10 by 10 booth in the far corner.
Jeremy: And there's only one of them there this morning, I'm sure.
Joel: Yeah, there's only one of them there today. That's interesting. Does LinkedIn ultimately, are they the biggest winner in this? Because everyone that's on LinkedIn chose to be there. They're relatively active. In a world of privacy that we're building, to me, LinkedIn is the biggest winner. Am I wrong?
Jeremy: Yeah. I mean it appears that way.
Jeremy: It appears that way.
Chad: Aren't they still going to have to jump through some hoops just to ensure even though you put your data there, it's your data and you have to have the ability, public, private, whatever it is. I mean they have some of those things, confidential.
Jeremy: Well it will be interesting. You asked about the HiQ settlement. The HiQ settlement basically says they cannot claim control of your, it's-
Chad: Our data.
Jeremy: They can't own the fact that I am who I am and I have the job title that I have. That is not theirs to control. So what will be interesting to me is do they just make everything private? Because they could do that at this point I would think. I don't know ...
Chad: Why wouldn't they?
Joel: They don't need Google anymore, right?
Jeremy: I don't think so.
Joel: Search traffic.
Jeremy: So I don't know it.
Chad: Why wouldn't they? It just makes sense.
Jeremy: It doesn't make sense why they would-
Chad: Just go ahead and make it a wall guard. A real wall guard. Because they've pretty much shut Google out for the most part.
Joel: Now I guess one angle would be if they did that, then your LinkedIn profile wouldn't show up on Google when people searched PHP developers in Seattle or whatever.
Joel: So that they would suffer from that.
Jeremy: So for SEO purposes, it'd be interesting how much it would affect them to just limit maybe one job title, one company.
Joel: Yeah, they could show Google an abbreviated profile, but then, okay.
Chad: They'd just making it available on bing.
Joel: Bing, yeah, bing and job boards are back baby.
Chad: All right, bing. You're going to do it baby.
Jeremy: You have to use Explorer.
Chad: This is it. This is your one chance.
Joel: Do you have any take on Google Hire shutting down?
Chad: I was kind of bummed. We used Google hire.
Joel: Oh your company used Google Hire?
Chad: Tell us about that.
Jeremy: Rally good.
Chad: Tell us about that.
Jeremy: And they were-
Chad: Seriously, you liked it?
Jeremy: It's was a good experience for a company our size. We vetted everything out there and we're pretty, under 40 people. It always worked out well for us. It was easy to share information, the recruiter would put us on teams.
Chad: You're a Google shop already.
Joel: G suite?
Chad: Yeah, G suite. Yeah, so too easy, right?
Jeremy: Yeah, so it was easy. They took no training to share a candidate with a manager and walk them through the process request them back.
Chad: So why do you think they shut down? Why do you think they're looking to shut down in a year?
Jeremy: I don't know. I guess like is cute to them, it's just they have so much money that this whole room, the biggest room in our industry is just kind of cute.
Chad: A little bitty [crosstalk 00:25:44].
Joel: Yeah, this is their cafeteria.
Chad: Or wash room. Yeah.
Jeremy: I don't know, I guess they just, yeah. They just have so much money
that it's not worth ...
Joel: Do you want to see if there are any questions?
Jeremy: It's a very difficult space to understand. I mean people try to simplify what we do but there's so many layers and so many-
Joel: I have some insight in this, and I think you might have some insight as well, but what my understanding was they were using a third party to parse resumes within the system and that the relationship with that vendor sort of went away, and Google couldn't parse resumes effectively enough to provide it as a service to hire. And my understanding is parsing jobs is a far easier thing than parsing resumes. Now you guys deal with data and profile data all the time. Does that make sense to you or no?
Jeremy: I don't know. Sean, is it easier or harder to parse resumes or jobs?
Joel: Jobs versus profiles or resumes?
Jeremy: A little harder on resumes.
Chad: A little harder on the resumes.
Joel: A little harder on the resumes.
Jeremy: A little harder on the resumes.
Chad: Do they shut down because of that?
Jeremy: So there's one vendor we could thank for getting Google out of our
Chad: That could be.
Jeremy: Is that what you're saying?
Chad: I don't think I'd say that.
Joel: My understanding there were three main reasons. One was the parsing of data. Two was the G suite users, they had less than 5% penetration of G suite users. And the customers they had were more or less small businesses that were a pain in the ass. So it was sort of a business decision to say, do we want to continue to sort of service these folks? And then the third one was the privacy issue, because they ultimately wanted to build a LinkedIn competitor. So yeah, you can search your own resumes, but eventually they wanted to do a web search where you can search the web.
Jeremy: Bring back Google+.
Joel: Yeah. So once GDPR and privacy happened, they were like, well fuck it. We're not going to be able to compete with LinkedIn because of that data is not ours. So those three reasons sort of built the foundation for them to say, we're fucking out.
Jeremy: Hasn't GDPR been around?
Joel: And you throw in any throw in, which we talked about on the show was the antitrust issues of like, do we want to be in court with every single country in the world for the next 25 years?
Chad: Yeah, end to end.
Joel: They said, no we don't, so we're out.
Chad: Yeah. Not worth it. Might as well cut that limb off for little HR because search is where it's at. Google for jobs, my beers out. So I'm done. So I'm going to go ahead. We're at time. I'm going to cut this off and I want to give away some tee shirts. So if you guys want to pop up.
Chad: Awesome Chad and Cheese t-shirt. Feel free, to come get it. Thanks guys.
Jeremy: Thank you guys.
Joel: First come, first served.
Chad: Thank you, Jeremy.
Joel: Thanks, Jeremy. We out. Oh, we have Tau Route tee shirts too.
Tristen: Hi, I'm Tristen. Thanks for listening to my stepdad, the Chad and his goofy friend, Cheese. You've been listening to the Chad and Cheese podcast. Make sure you subscribe on iTunes, Google play, or wherever you get your podcasts so you don't miss out on all the knowledge dropping that's happening up in here. They made me say that. The most important part is to check out our sponsors, because I need new track spikes, you know, the expensive shiny gold pair that are extra because, well, I'm extra. For more, visit ChadCheese.com.