In all seriousness though, have you ever tried to analyse unstructured text? It's hard. How would you realistically improve it? Do you start with a preconceived list of technology key words and count them in the resumes? People misspell words. Words have multiple meanings depending on context.
I've been writing code like this since 1985. Then, it was in LISP.
It's actually trivial to me at this point. You end up with a meaning trie with differential probability vectors, and some of the roots wither away as you go down. Making a machine decision is harder, but not entirely impossible.
I get incredibly annoyed at people like Lazlo Bock who want to put everyone's resumes into a form that basically allows Google (Lazlo Bock works for Google) or other companies to magically allow you to come into a new job under the horse collar of a performance review of your previous job which they were in no way involved with.
The whole "HR metrics" industry... uh... kinda pisses me off? I pick companies based on criterion other than standard metrics. If they pick me that way... they do not deserve me. Mostly they stumble into me, I fix them, and then I exit.
I understand the "OMG we need people who know what they are doing and not recent graduates!" panic. Does not mean I sympathize.