Slashdot Mirror


When the Hiring Boss Is an Algorithm

Hugh Pickens writes "Joseph Walker writes at the WSJ that although personality tests have a long history in hiring, sophisticated software has now made it possible to evaluate more candidates, amass more data and peer more deeply into applicants' personal lives and interests. This allows employers to predict specific outcomes, such as whether a prospective hire will quit too soon, file disability claims, or steal. For example after a half-year trial that cut attrition by a fifth, Xerox now leaves all hiring for its 48,700 call-center jobs to software. Xerox used to pay lots of attention to applicants who had done the job before. Then, an algorithm told the company that experience doesn't matter. It determined what does matter in a good call-center worker — one who won't quit before the company recoups its $5,000 investment in training. By putting applicants through a battery of tests and then tracking their job performance, Evolv has developed a model for the ideal call-center worker (PDF). The data recommend a person who lives near the job, has reliable transportation and uses one or more social networks, but not more than four. He or she tends not to be overly inquisitive or empathetic, but is creative. 'Some of the assumptions we had weren't valid,' says Connie Harvey, Xerox's chief operating officer of commercial services. However, data-based hiring can expose companies to legal risk. Practices that even unintentionally filter out older or minority applicants can be illegal under federal equal opportunity laws. If a hiring practice is challenged in court as discriminatory, a company must show the criteria it is using are proven to predict success in the job."

8 of 245 comments (clear)

  1. That explains a lot by afidel · · Score: 5, Insightful

    tends not to be overly inquisitive or empathetic

    Well, if the bean counters consider the lack of those qualities to be what makes for a good callcenter worker then it's no wonder that the quality of support has gone down as fast as it has. Six or seven years ago when I called into support there was about a 50% chance of reaching someone who was smart and could solve my problem without relying on a script (which never solve my problem because if it can be found in available documentation I've already tried it before calling support), today there's maybe a 5% change if that.

    --
    There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    1. Re:That explains a lot by rsxaeon · · Score: 5, Insightful

      There is no such thing as asking nicely to speak to someone who speaks English when the person you are speaking to does speak English. Regardless of how well you feel they speak it, this is always rude.

    2. Re:That explains a lot by Anonymous Coward · · Score: 5, Insightful

      Suggestion: Stop assuming they're dumb, and just fucking work with them. You KNOW they're going to break it down step by step. So instead of shouting at them and making them scroll up to re-read your initial data dump, try this:

      Agent: Hi [...] what's the problem?
      Me: I'm unable to connect to the internet.
      Agent: Can you power off the modem and power it back on?
      Me: I did that, and it made no difference.
      Agent: Can you please connect your computer directly to the cable modem?
      Me: I did that, and it made no difference.
      [... continue on giving him all of the data you've accumulated in small doses. ...]

      When you slam somebody with a fucking book's worth of diagnostic issue, and immediately jump to "I NEED TO KNOW if the problem is X or Y," you're only going to frustrate them and yourself. They HAVE to follow the script. You need to get through the script as quickly as possible to get to someone who knows more about the problem than the level 1 guy - so WORK WITH the script. I never understand why people find this so frustrating - yes, they're asking you to do things you've already done - so simply say, "okay, I did that, no change." You don't need to argue with them, you don't need to try and hurry them along - work with them, and they'll be able to help you faster.

      Sometimes getting the help you need is as easy as treating the person whose job it is to help you with a little respect - remember, you need something from them. Responding to them in a tone that says, "hey you dumb brown-skinned Indian motherfucker, speak english, and stop asking me stupid shit, because I'm a smart smart american," is just going to guarantee they'll do the minimum possible to help you. Respond to them in a tone that says, "Hey, I'm stuck, and you're the guy who's going to help me get unstuck, and I appreciate your help," might just help you get a solution (or at least get to Level 2 or 3 support) faster.

  2. Tell me about it by Anonymous Coward · · Score: 5, Interesting

    I had a hell of a time landing a federal position in the department that I had been working for years as a contractor because the automated system at OPM kept kicking my resume out of the candidate pool. If you fail to get past that, then local hiring managers aren't even aware you have applied, and have no recourse. A co-worker finally gave me pointers on "faking out" the word filters, and I went from "unqualified" to "highly qualified" overnight.

    1. Re:Tell me about it by jittles · · Score: 5, Interesting

      I actually just recently applied for a part time state position teaching computer science to high school students online. The requirement was that you have a BS in CS and have a teaching credential. I was automatically rejected immediately, for not having a temporary credential. The requirement for a temporary credential? Having been offered a teaching position inside of the state. So, a req that has been open for almost a year remains unfilled because they can't hire someone with a computer science degree who doesn't have a teaching credential already. How many people are there that have a CS degree that want to teach high school? Probably not many. I thought it would be a great way to give back to the community (the pay is terrible), but I guess not. I can't even get past the computer, unless I lie about having a temporary credential. If I lie about having a temporary credential, then the law says that (upon discovering the lie), the state is barred from hiring me. What a messed up and useless system. They will probably never fill that position.

      It's too bad, too. I was willing to give up 5-10 hours a week to help out kids who want to learn. Anyone who is already teaching probably doens't want to spend that extra time with kids.

  3. Japan doesn't have cheap labor by sjbe · · Score: 5, Insightful

    There's a growing trend of hiring intelligent Japanese, Chinese and Indian workers at a fraction of cost to U.S. ones

    You think labor rates are cheap in Japan? GDP per-capita in Japan is about 4X that of China and about 10X that of India. Japan has plenty of talent but it isn't particularly cheap or abundant talent. Japan, like the US, relies heavily on automation. Labor intensive industries left Japan years ago just like they did in the US.

    The U.S. ranks 23rd among developed nations in the percentage of students with undergraduate degrees in science or engineering who are employed in related fields

    Now figure out what that means. It's not at all clear what significance is in having a lower percentage of engineers at a portion of the population. The US is also the third largest country in terms of population so even if they produce a lower percentage of engineers than some other countries they still will produce larger absolute numbers than most of them. You seem to be implying that graduating a lower percentage of engineers/scientists will result in negative consequences. While that might be true you have to back it up with more than just vague implications.

  4. I work at Evolv by edcheevy · · Score: 5, Informative

    I'm an industrial/organizational psychologist at Evolv. I help build assessment content and I work closely with our predictive algorithms. A few clarifications from the WSJ article & responses to /. comments:

    Yes, creativity and empathy are important for some positions, even in call centers! We're not looking for hateful drones who will hang up on you when you call in. In addition to staying longer, our recommended hires perform better as well. That means increases in both customer satisfaction and efficiency (we call it "average handle time"). But it's a curvilinear relationship - somebody who is too inquisitive is going to tend to waste your valuable time (and their employer's) while trying to resolve your issue. There's a balance.

    Most test vendors put a test in place and walk away. At Evolv we take all the post-hire data from our clients and continually feed it back into our algorithms. The content, scoring, and weighting adjust over time to be more predictive.

    At Evolv, we don't pair obvious responses when we create questions. So no "I like to steal office supplies" vs "I always show up to work on time" questions. Coupled with the continual refresh & validation of the content, there is no "answer key" that will get you a job. One of the neat things about this approach that we've found is that people applying to entry level positions often don't know what they're good at. Either they've bounced around a few jobs or they're just out of high school. So when somebody applies to a call center job that's hiring for both customer service and sales positions, and we can recommend the position for which they're likely to be "fitter, happier, and more productive"... that's kind of cool. Their employer will make more money off a more stable employee, and the employee ends up doing something they will enjoy just a little bit more. I know some folks will see it from the Radiohead point of view, as creepy (and I respect that), but we think it's better than dumping somebody into a position they're not going to enjoy just because they had the right keywords on their resume or they BS'd their way through an interview.

    Science & statistics help eliminate some crazy gut-based hiring decisions. Some hiring managers want to ask call center applicants what they'll be doing in 10 years with an expected response of "I'll be working at this call center". But let's be realistic - while some people enjoy them and thrive, call center jobs are typically not where you plan to be in 10 years. We've also found that resume experience for entry level positions is less important than basic skills and attitude. It's easy to look at that and say "duh" but you'd be surprised how many people hiring & screening for these roles want to exclude applicants who don't have prior experience. So we can cut things out of the interview and hiring process that just don't mean anything.

    Evolv doesn't just do employment screening. We periodically follow up with people after they're hired. We find out what information wasn't communicated well during the hiring process, get their feedback on how their training is going, their thoughts on their supervisor, that sort of thing. We feed all of this back in to improve the process. In some cases, that means identifying the trainers whose students perform poorly when they start working. Other times it could be flagging a tenured stellar performer whose numbers are starting to dip for a new position to help reinvigorate them. We strive to improve profitability across the workforce, and do so in an employee-friendly way.

    Last but not least, we're still expanding through Xerox, so if you've called their customer service and had a bad experience it must not have been one of our hires. Joking aside, agents are people too, and even our top recommendations have a bad day. We're working hard to to make it better though!

    Hope that helps! Yes, there definitely are risks with employment testing, but we try to avoid them and build solutions that make everybody's life a little better.

    Cheers,
    Tim

  5. Re:Reason is simple: U.S. Workers are stupid by boristdog · · Score: 5, Interesting

    I have worked in Japan, this is VERY true. During much of the work day, and especially the late afternoon/early evening was almost official goof-off time. Then everyone buckled down and got to work in the overtime hours. And if you left before 9pm you were supposed to apologize to everyone. It was weird.

    Also, many Japanese Engineers are still paid hourly instead of being salaried, so it is to their advantage to work long hours. Plus, white collar workers wore "uniforms" of some sort everywhere. Often it was just the same color pants and shirt for everyone. And it was a different color for females.

    And then there was always the morning "chant" meeting where everyone gathered and did the weird company chant. Of course when I asked my co-workers about any of these things I was always told "It's a Japanese thing."