This is a fantastic read and one that resonates with me as I face some challenges finding the right…

I dabble around in the FinTech space - Like travel, music, golf and fishing - Looking to leave a mark on the world - The guy behind @StockSwipe @ChronicTimer

Jul 27, 2016

In the short term, improving collaboration across different teams involved in hiring is a good start. As we saw, engineers are better at judging certain kinds of resumes, and recruiters are better at others. If a resume has projects or a GitHub account with content listed, passing it over to an engineer to get a second opinion is probably a good idea. And if a candidate is coming from a company with a strong brand, but one that you’re not too familiar with, getting some insider info from a recruiter might not be the worst thing

Resumes suck. Here’s the data.

Aline Lerner

36114

This is a fantastic read and one that resonates with me as I face some challenges finding the right opportunity in today’s market. I have written a short story detailing my experience and struggles. I also believe the current recruiting process is broke and am surprised even the tech industry isn’t fixing this as they should be at the forefront of innovation.

In an attempt to stand out, I revamped my resume and wrote about it here. To be honest, I’m not even sure if I made things better or worse. Ultimately I agree that the current format for displaying your skills and experiences is broken. At the same time, what people expect to see on a resume various widely. Some recruiters want you to include every keyword possible, others only care about grammar/punctuation while some only care about number of years of experience.

The biggest complaint I have is my experience with recruiters who don’t seem to collaborate with a technical person to access a resume. This fundamentally leaves the system broken because recruiters will naturally only look for keywords and numbers, rather than understanding the technical experience and knowledge a candidate may have.