让搜索更有效的五种方法-5. 不要抱怨人才数据库,相反,你应该想想怎么去利用好它

Danny讲的数据库原则还是简单了点,如何用好有限的数据库资源其实有很多值得发挥的地方,特别是搜索方式,搜索组合,关键字,行业关键字,前任公司信息等等,总的来说就是高效的用好线索人,有技巧的有目的沟通。
永远不要认为你完全了解候选人的情况,因为情况会发生改变。候选人上个月或者上个季度不愿意换工作,并不一定意味着今天他们也同样不愿意换工作。
候选人不是问题的关键,问题的关键在于猎头自己;我有一个积累了35年的人才数据库,里面有数千的候选人数据。可是,如果现在你问我公司里的任何一个资深猎头,他们中的绝大部分并说不出来数据库中所有候选人的情况。他们会说,那些只不过是些很旧的电话信息了;想了解情况的唯一方法就是立即打个电话,开始新的搜索。
尽管如此,有一些事实是所有的猎头都必须了解的,那就是数据库永远不会自动更新;它没有这个功能。你永远不应该说你已经查阅过了数据库并且没有发现合适的候选人能达得到要求,因为你应该把数据库看成是搜索目标的有机组成部分,它是活的,会呼吸的,并不断发展和变化的。
这里我讲一个我个人亲身经历的故事。我和我的一个同事Tim一起负责招募一个工程师的职位; 我从数据库中找到了一个叫John Doe的候选人,我试着给他推荐这个职位;
他说,”不用了,谢谢你,我非常喜欢我现在的工作,不过我会帮你看看是不是有合适的人选给你推荐.” ,然后我挂断了电话,并继续搜索其他的人。
一个小时以后,Tim来到我的办公室说,”嘿,我找到了一个合适的人”
“真的吗”我说,“那你找的是谁啊?”
“John Doe,” Tim 回答道.
“不,不会吧” 我说。我想Tim一定在撒谎,因为当时我们俩正在进行一个推荐人数的比赛,我想他一定是在作弊。所以我对他说,”Tim,别扯了,兄弟。我一个小时前刚刚跟他聊过,他跟我说他现在工作得开心得很”
Tim说道:”不,兄弟,你别扯了;我15分钟前刚刚跟他聊了一下,他告诉我说他刚刚被公司裁掉了。”这就是数据库的特点—数据库永远不会自动更新。这就是猎头和招募者的搜索底线:永远不要认为你完全了解候选人的情况,因为情况会发生改变。候选人上个月或者上个季度不愿意换工作,并不一定意味着今天他们也同样不愿意换工作。
——————————————–原文如下—————————————————-
Don’t Blame the Database. Instead, Think About How You Use It.
Never assume you know all of the candidates because situations are also subject to change. Just because a candidate wasn’t interested in making a move last month or last quarter doesn’t mean that they might not be interested in the position you have to fill today.
It’s not the legacy candidates that are the problem, but the legacy recruiters. I have a 35-year-old database with thousands and thousands of candidates in it. If you asked any of my senior recruiters right now, most of them would probably say they know all of the candidates in the database. They would say that there are only the same old people in there, and the only solution is to jump online or get on the phone and begin cold sourcing.
However, there’s something every recruiter must understand – the database is never updated. It can’t be. You should never say that you’ve already checked the database and no candidates meet your criteria because a database must be seen as an organism. It’s a living, breathing thing that is constantly evolving and changing.
Here’s an example from my own experience. I was recruiting an engineer job along with another recruiter in my office, Tim. I called a candidate from our database, who we’ll call John Doe, and tried to recruit him for this position.
He said, “No, thanks, I love my job. I’ll see if I can think of anyone for you.” So I hung up the phone and moved on.
An hour later, Tim comes in my office and says “Hey, I got a send out on a job.”
“Really,” I said. “Who are you sending out?”
“John Doe,” Tim replied.
“No, you’re not,” I said. I thought Tim was lying because we had a send out contest going on, and I thought he was making it up. So I told him, “Tim, you’re busted, dude. I talked to John an hour ago and he’s happy where he is.”
That’s when Tim said, “No, you’re busted. I talked to him 15 minutes ago and he just got laid off.” That’s the deal with the database – it’s never updated. That’s the bottom line for recruiters. Never assume you know all of the candidates because situations are also subject to change. Just because a candidate wasn’t interested in making a move last month or last quarter doesn’t mean that they might not be interested in the position you have to fill today.


