[nh2]

> No one reads em.

I do, and I know others do.

I did resume reading and technical interviewing as part of the hiring process of a Haskell consultancy. Over 5 years, interviewed around 50 people, for both the consultancy and its customers.

I read the resumes carefully. They were generally informative and accurate.

When somebody mentions expertise in a specific tech stack or theory, I ask them in the interview to explain me a key part of that, how it works and what its intricacies are. React in the CV? Show me an example. Haskell-in-production expert? Write me some code that takes down a web server, then show me how to do it well. Expert in COQ, Agda or Idris? Prove it.

It becomes apparent quickly if somebody is bullshitting in a CV, if you care to notice.

This approach worked well and wasn't changed since.