In the part of the article that lists "Rejection Reasons" one rejection type is "Too Enterprisey". Could someone please clear up what that means for me?
Resumes suck for hiring engineers
91–100 of 172 posts
Re: Resumes suck for hiring engineers
#92The startup where I serve as in-house recruiter, FutureAdvisor, recently ran an experiment in hiring without resumes. It was called StaffupWeekend. The Chronicle's careers blogger wrote about it here: http://blog.sfgate.com/gettowork/2014/10/31/staffup-offers-a... We recognized that resumes were poor indicators of performance. In fact, we believe that the only thing that correlates with performance -- is performance.…
> The solution we came up with was to invite people to work on projects for a weekend at no cost other than their time. As in working for you for free, and on a WE to boot? For a student or someone who is unemployed, that might work. For someone with a job and a family life, I don't think so. Especially if that person can command a $120k+ salary.
Dude, they get to contribute to the company for free.
Re: Resumes suck for hiring engineers
#93The experiment looks flawed. It seems that ALL (or almost all) resumes are, at least, OK. Resumes can work for weeding out bad fits, or people doing things clearly out of the scope of interest. They are not, and cannot, be a tool for choosing the best. (Unless success is so spectacular, that you know the person by name anyway.) It's HR's delusion that previous -perceived- presented achievements written on one's resum…
It was about 50/50 for the 6 samples I was given.
Re: Resumes suck for hiring engineers
#94I'm in the process of going through technical interviews with a bunch of companies (some I approached, some approached me.) The coolest thing has been some peoples' reaction to the little details on my CV (Resume.)
Compared to the other very unsuccessful interview, where the MD just listened to me talk for a few minutes and said "you're not what we're looking for" (no programmer in the interview), getting engineers to ask me end-of-interview questions with a smile on their face was really fun (whether or not I get the jobs in the end.)
The OP says that engineers were quite good if the CV contained enough detail about what the candidate had been doing, the substance of the projects. In both cases, the little question was where I had included a bullet thinking "noone in HR will know what this means, but I think it's cool" were the ones that got the smile question.
For the record, all my CVs are skills-based (that is, a set of bullets around "programming", "teamwork", "communication" etc) followed by a brief chronology of work and education, rather than having to list every position (student volunteering included) in order to say what I did there that was relevant. Customising which bullets (and even sections) you include on a per-application basis is extremely important, of course, so that the HR person can see "skill that we asked for: 5 bullets" right there on the first page.
Re: Resumes suck for hiring engineers
#95I'm in the process of going through technical interviews with a bunch of companies (some I approached, some approached me.) The coolest thing has been some peoples' reaction to the little details on my CV (Resume.) Compared to the other very unsuccessful interview, where the MD just listened to me talk for a few minutes and said "you're not what we're looking for" (no programmer in the interview), getting engineers t…
This may be off-topic, but it sure sounds to me like what you're submitting is not a CV but a resume. Those are two different items. CVs are a comprehensive history of yourself and your accomplishments, resumes are short, tailored briefs of why you are fit for the job.
Re: Resumes suck for hiring engineers
#96I'm in the process of going through technical interviews with a bunch of companies (some I approached, some approached me.) The coolest thing has been some peoples' reaction to the little details on my CV (Resume.) Compared to the other very unsuccessful interview, where the MD just listened to me talk for a few minutes and said "you're not what we're looking for" (no programmer in the interview), getting engineers t…
This may be off-topic, but it sure sounds to me like what you're submitting is not a CV but a resume. Those are two different items. CVs are a comprehensive history of yourself and your accomplishments, resumes are short, tailored briefs of why you are fit for the job.
in the UK, they're all called CVs.
Re: Resumes suck for hiring engineers
#97In the part of the article that lists "Rejection Reasons" one rejection type is "Too Enterprisey". Could someone please clear up what that means for me?
Here is a parody of what they're terrified of
https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...
Re: Resumes suck for hiring engineers
#98Funnily enough I've been working on this a lot lately for a book I've been writing[1].
It seems there are several audiences for a CV (recruiter, hiring manager, supporting interviewer) and a fundamental error that people make is writing a CV for more or less than these three types of people.
The fundamental truth is that no-one wants to read a CV. They're at best an advert, but people tend to overstuff them or fill them with things irrelevant to the position they're applying for, so they get ditched by people who have tons of them to read through.
I have a free email course about career hacking for anyone that subscribes to my book's mailing list. It's focused on people who want to become penetration testers but the career material is applicable to anyone wanting to get into a discipline that they're not already in.
[1] - https://www.rawhex.com/
Re: Resumes suck for hiring engineers
#99Earlier quoted context omitted.
> Where's the evidence that there is a better alternative? Where's the evidence that resumes are better than random selection among applicants into the next round, much less enough better to be a net positive given the resources that go into reviewing them?
Huh? I think you're confusing the concept of "top of the funnel". Are you suggesting that I randomly select people to interview from a pile of resumes? What if I get a marketing person who has no software experience in the pile for a software developer job?
I am not suggesting anything, I am asking where the evidence is that the practice of asking for and reviewing résumés has positive expected meet utility as a filtering mechanism, and your responses suggest to me that for you that practice is not evidence based but based in unchallenged intuition.
Re: Resumes suck for hiring engineers
#100The real questions are:
What would be better than sending a resume?
Should the job ask for a resume as well as have every applicant submit a project somewhere, one which will be "unit tested" automatically to filter candidates? Should they just ask for the project?
Should there be something other than a resume like a timed coding test or something (where the applicant needs to take half an hour and write a program to do X in the language that they will need to work in, probably something really simple)?