Average Duration of Hiring Process For Software Engineers: 35 Days 179
itwbennett writes: Despite the high demand for tech workers of pretty much all stripes, the hiring process is still rather drawn out, with the average time-to-hire for Software Engineers taking 35 days. That's one of the findings of a new study from career site Glassdoor. The study, led by Glassdoor's Chief Economist Dr. Andrew Chamberlain, analyzed over 340,000 interview reviews, covering 74,000 unique job titles, submitted to the site from February 2009 through February 2015. Glassdoor found that the average time-to-hire for all jobs has increased 80% (from 12.6 days to 22.9 days) since 2010. The biggest reason for this jump: The increased reliance on screening tests of various sorts, from background checks and skills tests to drug tests and personality tests, among others.
Drug Tests. (Score:3, Funny)
Of course hiring process takes time. A friend of mine had to quit smoking weed for like 10 DAYS to get the job.
Re: (Score:2)
Hardly Surprising (Score:5, Insightful)
This is hardly surprising:
- It seems like an unwritten rule that the tools and websites (third-party and homegrown) that business use for hiring are horrible. I have to assume they're designed to be a gauntlet so that only the most stubborn and persistent candidates make it to the end.
- Automated tools that scan resumes looking for specific things have led to people putting all sorts of crap on their resume, just in hopes of getting a foot in the door. This leads to interviews like "So it says you have a lot of experience in SQL. Can you elaborate on that?" Candidate: "Oh, yeah, I took an online class a few years ago and I did some SELECTs!"
- Most recruiters have a clear conflict of interest and some of them take a scattergun approach that interviewers need to filter through.
- Wishy-washy managers always want to wait and put off giving an offer "in case something better comes along" (I've heard that many times in post-interview discussions).
- Internal politics when there's any kind of restriction on how many open seats will be filled leads to infighting between groups, delaying an offer because nobody knows who they'd work for yet.
I could go on and on, but suffice to say that HR at most places is filled with depressing things, but the hiring process is one of the worst.
Re: (Score:2)
Re: (Score:2)
HR at most places is filled with depressing things, but the hiring process is one of the worst.
The hiring process is filled with depressing things, and the HR department at most places is one of the worst.
Re: (Score:2)
If the hiring process involved some kind of online form filling or the interview is a barrage of tests, I know that job isn't for me and I don't want to work at that company.
Re: (Score:3)
Re: Hardly Surprising (Score:2)
See, you'd know that if you'd gone to college.
Re: (Score:2)
It's not experience though. You should say on the resume that you've had a class in it, but not that you have lots of experience with it.
Re: (Score:2)
I did. My resume clearly states: "SQL class, 3 days, 2012, no practical experience" - meaning I understand what a SQL statement does when I read it, but I struggle building one from scratch.
I'm getting requests for interviews from various companies on a monthly basis, for jobs which involve excellent SQL knowledge which I don't have and was clear about it in my resume.
Re: (Score:2)
Ever had somebody trying to recruit you as a SQL Server DBA because you put SQL on your resume (in any capacity)? That's more of a recruiter thing, though.
Re: (Score:2)
Confirmed... I've been hiring. (Score:3)
Brought on three software developers in the last four months. Once the verbal offer is accepted it's about a month for our company. Background checks, references verifications, etc make it a lengthy process indeed. I just agreed to bring on a contractor who already has a background check, and he won't land for three weeks even though he's on the bench.
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
Except that it doesn't keep the applicant from straying. If he gets a better offer from the time he accepts and the other company gives him a firm start date of next Monday while the first company still has two more weeks to go of dicking around with their internal paperwork, odds are the first company is going to get a phone
Re: (Score:2)
Right so what do you do instead? A background check takes a long time. Do you delay the interview for a couple weeks, or delay the start of work for a couple weeks? Very often candidates want a week or two before starting anyway (but the workaholics won't). For my last job the results didn't arrive until after I had already been working there. I have run across a couple of cases where an employee was terminated within the first month when problems showed up with the background checks. I've seen it hap
Re: (Score:2)
Interviews, downselection, possible second interviews, verbal offer with requirement of passing background and reference checks, checks performed, written offer. Then start date set, usually two weeks or more out.
That's why it takes so much time.
Re: (Score:2)
Right so what do you do instead? A background check takes a long time.
Pay more for the background check, apparently. They shouldn't take a long time, especially since they're mostly worthless.
Re: (Score:2)
No, paying more doesn't help.
I know of several background check companies. One of them checks everything in your resume - they verify that yes, you attended College U. between those dates you claimed, and that yes, you were in the right department (that information's mostly public). They even go and verify your past employers. When you hire people from other countries, it takes even long
Re: (Score:2)
If I find out that a place fires people after they start when the background check finally gets done and comes up with something bad, I'm going to be very reluctant to accept an offer. My background is positively boring for those people, but I don't know them and don't trust them not to get me confused with somebody who had a more interesting past.
Re: (Score:2)
You give the verbal offer and *then* do the background & reference checks?
Yeah, I was wondering about that too. WTH?
Hopefully the verdict is in before he gives notice at his old job ...
Re: (Score:2)
You give the verbal offer and *then* do the background & reference checks?
Yeah, I was wondering about that too. WTH?
Hopefully the verdict is in before he gives notice at his old job ...
I assume it takes a month because all of the background checks take two weeks and then they have to wait for the employee to give the current employer a two week notice. That is what happened in a company change I made earlier this year, although it only took a week for the background checks.
Re: (Score:2)
Background checks can be expensive, so I suspect those get done last. I had my results arrive after my first day on the job. I remember back in the day that for jobs requiring security clearances that the employee would be hired and paid but have no actual job assignments for a few months until the FBI background checks were completed.
Re: (Score:2)
Yes, but the verbal offer is explicitly contingent on passing the background check.
Cost of legal protections (Score:2)
Now you know one of the prices you are paying for legal protections. Legal protections are a good thing. Good things cost you. Knowing what good things cost you can help you decide how many good things you can afford.
Survival of the fittest (companies) (Score:5, Insightful)
Say you interview at two companies. You're awesome, and they both love you. One gives you a firm offer the next day. The other sends you a firm offer 35 days later, which isn't even slow for the industry.
Are you still waiting on day 35 for that second offer? Probably not.
Nimble companies will score the best employees. The real question: does the slow-as-hell hiring bureaucracy weed out bad employees and help the company overall? If not, they're at a competitive disadvantage.
Re: (Score:2)
Re: (Score:2)
Application rejected (Score:2)
Subject tested positive for a personality.
personality test? (Score:2)
What is this, a job for Scientology Programming?
Re: (Score:2)
I'm guessing "personality test" simply means you're trying to screen people out who have horrible personalities that won't work well with others. If you've had the misfortune of working with people like that before, you might understand the reasoning behind that sort of test.
I can't personally conceive of how such a test might work, short of just getting a few members of the team together to chat casually with the interviewee for a while, and even then, most antisocial people probably know how to behave pr
Re: (Score:2)
I can't personally conceive of how such a test might work
Young, white skin, doesn't speak with an accent. Passing grade is 2 out of 3 or better.
Re: (Score:2)
Are companies hiring H1B's in droves or are they discriminating against brown-skinned people with accents?
Re: (Score:2)
It's OK to have slaves if they are brown. But you shouldn't give them stock options, a retirement plan or a path to promotion.
Re: (Score:2)
Re: (Score:2)
And for bonus points, like Disney [slashdot.org] or Edison, have your old white guys being laid off train your brand new brown imported slaves.
Re: (Score:2)
And checking references. And checking calling up "Joe" who worked with you at company X and is now at the same company the candidate is at to see what "Jo" thinks. If you have an area where tech workers are concentrated and people circulate from one employer to the next you can look someone's reputation up. It is also easy to 'blackball' someone if they burn you. I've heard of it, the casual get together at the bar, the exchange of banter, and a brief mention that "Tom" isn't working out so well because he
Re: (Score:2)
It's also solving a non-problem. Having a mixture of personalities in a workplace is better than having a monoculture - for instance Enron with hard driven floor trader types that had never grown up was like a high powered fighter jet pointed directly at the side of a mountain. Selecting for such types resulted in an epic failure with a
Re: (Score:2)
It helps to have some idea of what personality they're looking for when taking the test. As a long-time role-player, I'm used to keeping spare personalities around.
I have a friend who was very nervous going into her first job after getting her doctorate. She went to the interview as her character in a secret agent campaign, out to infiltrate the hiring organization, and it worked.
Google effect (Score:2)
Re: (Score:2)
Totally this.
The last time I went through the ordeal of looking for a job (about a year ago), it was pretty common for them to make me come back for a second afternoon of interviews. What balls these people had to make me take a second half day of PTO to interview with them! Pad the schedule for the first round next time, I have better things to do! And I'm not talking about cool companies you'd really want to work for here, not Google or Apple etc, but some pretty mediocre places.
HR bullshit (Score:3)
Drug tests? Seriously? (Score:2)
And they actually manage to find any? Wow, impressive! Or rather, can I get a list of these companies so I can short their stock, since they apparently resort to people that desperate for a job?
Our (illegal) drugs-of-choice vary, but I can count the number of programmers I know who don't use anything on one finger (and even she has "tried" weed, "back in college").
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
> Wait... Some companies actually give programmers a drug test?
One of the tricks of doing this is that it reveals medical issues and medical history, which can be quietly collected and assessed even if discrimination is technically illegal. Much like the interview and job description tuning that be used to select only for H1B visa holders instead of hiring American, the paperwork and even the tests themselves can reveal productivity and medical cost relevant conditions such as gender, age, pregnancy, dep
From When to when? (Score:2)
I couldn't see in the article but what are the time measurements between? Is it from job going live to someone accepting? In which case 30 days for a high level role is REALLY REALLY low. Some of the roles I hunt for take 3 months just to find someone who can do the job...
Re: (Score:2)
Economist? (Score:2)
What the fuck for? Its a job listing website.
Re:Economist? (Score:4, Informative)
>> So a job listing website has a "Chief Economist" on staff? What the fuck for?
I'll bite. Back in the back I was an intern for an economist at a huge phone company. We were part of the marketing division, and our job was to parse economic trends to figure out things like which regions were growing fastest (so we could reallocate resources there to capture market share), which seasonal trends were emerging (e.g., non-Christian holidays) and which corporate markets were healthiest based on indicators like sector stock performance. It was never double-digit percentage revenue stuff, but at a very large company it made sense to spend a million on economists to capture a few extra dozen million or so in revenue.
Meanwhile, average duration of firing (Score:2)
is now less than one microsecond.
Hypothesis: results from firing restrictions (Score:2)
With all the regulations and civil litigation around termination, and articles on the psychological "harm" caused by being too honest with certain types of people (read: millennial special snowflake types), is it any wonder that companies that have to go through an act of congress to fire someone are more wary of hiring someone without a lot of verification? Consider also that since about the late '90s, when someone called you as a reference for someone, you could only say, "Yes, that person worked here on
Meanwhile back in reality (Score:2)
Re: (Score:2)
35 days is an underestimate (Score:5, Interesting)
Re: (Score:2)
It has also become a revolving door between Google, Facebook, and several other big tech companies -- people get a little bored, go elsewhere, eventually realize the grass was gre
Pointless HR busywork (Score:2)
So why all the extra bullshit that current employees didn't have to go through apart from HR empire
Re: (Score:2)
Drug testing doesn't have to be about strict liability. Depending on how competitive the market is that your company does business in corprate espionage may be a real concern. An illegal drug habit can make for strong blackmail material.
And then there's Google..... (Score:2)
One of the elephants in the room in hiring tech these days is Google. Many interesting people in technology today put in applications for the variety of roles Google advertises. But Google apparently doesn't interview for the particular roles, and they have an _extraordinarily_ long time between application and phone screen that may be for a different job, another period of weeks or even months before scheduling the on-site interview that again is often for a different job, and weeks or even months before m
My experience so far (Score:2)
One HR skype interview (~1 hour)
One technical skype coding interview (~1.5h hours)
One manager skype interview (~1 hour)
One home exercise (~8 hours over one week)
One on-site interview
It took some time (around 40 days), but I thought the overall process was fair. The worst part was that after every interview it took around one week to get any response from the company, they should had really streamlined the process so I could take the several interviews in a row and take the home exercise in a single day.
And it's due to... (Score:2)
Background checks. SKILLS CHECKS - isn't that what the hiring manager is supposed to ascertain via the a) resume, b) phone interview, c) personal interview?
This, actually, points directly to where the problem is: HR, who DO NOT KNOW what they company does or what they're hiring someone to do, AND DON'T CARE TO LEARN. To paraphrase the old line from SN, they're ignorant sluts, Jane".
Here's another point: it takes 35 days (is that business days, or calendar?). Then, in a lot of cases, they'll be there 3 years
Re: (Score:2)
This isn't possible on all systems. Thanks to bullshit in the tech industry, a bunch of us are stuck on laptops with a "720p" display, because for years the industry thought it would be awesome to lock everyone down to this size, despite having 1600x1200 become semi common places years prior.
TLDR: It shouldn't be up to the use to fix bad design by designers. And these titles getting cut off is getting seriously fucking annoying.
Re: (Score:2, Insightful)
Brilliant advice. Next you'll tell me to get a larger monitor for the headlines that don't even fit in a maximized window. BTW, some of us like to use our remaining screen real estate for other uses (multitasking, how does it work?). How about instead demanding that they not overlay icons over the headline text any more?
Re: (Score:2)
h2 {class="story" style="margin-right: npx;"}
Re:So what? (Score:5, Interesting)
So the duration is 12 days longer than the average, so what?
The problem is that while you are evaluating the job candidate, the candidate is evaluating your company, looking at other opportunities, and going to other interviews. It is the best candidates that are most likely to get other offers. You might think you are being more selective by dragging out the process, but the actual result is that you are losing the wheat and keeping the chaff.
There is little evidence that dragging out the process helps. Checking references doesn't really help, since you have no idea if you are talking to their ex-boss or their roommate. Even criminal records have been shown to have no correlation [economist.com] with job performance.
When I schedule an interview with a prospective hire, I prepare the paperwork to make a job offer at the end of the interview. If they look solid, and everyone involved gives a thumbs up, I make the offer. More often then not, they accept on the spot. Others sleep on it, and call and accept the following day. But we lose a lot fewer good candidates that way.
Re: (Score:3)
Re: (Score:3)
When I schedule an interview with a prospective hire, I prepare the paperwork to make a job offer at the end of the interview. If they look solid, and everyone involved gives a thumbs up, I make the offer. More often then not, they accept on the spot. Others sleep on it, and call and accept the following day. But we lose a lot fewer good candidates that way.
How does that work if there's multiple candidates? Do you simply hire the first one who passes the "thumbs-up" test or are you flexible enough you'll hire as many good people who shows up at the door? Most places I've worked for you get permission to hire a new person from up high, you get a round of candidates and pick one. If you give the first guy an offer, well you don't really have anything to offer the rest.
Re: (Score:3)
You interview the ones who look good enough in descending order of, umm, apparent gooditudenessity. If one is not so good in the interview, or says no, you move on to the next.
Re: (Score:2)
So you have one open req, you interview one person on Monday and another person is scheduled to be interviewed in Friday. Do you hire the adequate person on Monday evening or do you wait in case the Friday candidate is better?
Re: (Score:2)
Did you actually read what I wrote?
Think of it working like a Dutch auction.
Re: (Score:3)
How does that work if there's multiple candidates? Do you simply hire the first one who passes the "thumbs-up" test or are you flexible enough you'll hire as many good people who shows up at the door?
The latter. You should always be in "hiring mode". If you hire smart people with a track record of getting stuff done, you can always find a place for them. The criteria I use is that they should be a "top third" prospect, with an expectation that they will be better than 2/3rds of current employees. If I don't have a vacancy, then I fire one of the bottom third people to make room.
Re:So what? (Score:5, Informative)
The norm for big software companies seems to be: you have some number of open reqs for your team, and you're eager to fill them (both to get the work done, and because the might vanish). So you work your pipeline as best you can, interview anyone who passes a phone screen, and hire anyone who passes the interview. At most places I've worked, we end making an offer to about 1 in 20 people we phone screen (about 1 in 3 who we bring in); where I am now we make an offer to about 1 in 5 we bring in, and they don't always accept of course, so that's maybe 50 people who look good enough to phone screen to hire 1. You're much more likely to have too few qualified candidates than too many. Normally, if you end up with an extra guy you'd like to make an offer to, another team will be delighted to take him.
Re: (Score:2)
I've made that mistake before.
I'm not saying you should never turn down a definite for a maybe, but the maybe would have to be pretty darned good.
Re: (Score:2)
If you're impatient enough that you won't wait two weeks for an offer letter, I've got a long line of qualified applicants that will. At the end of an interview, we always tell the person what to expect. We're required to interview a minimum of three applicants for every requisition this is due to compliance regulations. After the interview, the selected candidate has to be approved through multiple layers...HR, legal, compensation, and normally a couple layers of engineering management. That typically
Re: (Score:3)
So how is your hiring record then? How many of those employees that you have hired that way are still with you? How many of them would rate as excellent in job fit? Culture fit?
Re: (Score:2)
When I schedule an interview with a prospective hire, I prepare the paperwork to make a job offer at the end of the interview.
Then you're fortunate not to be working for a large company. The hoops we have to jump through include approvals from a couple levels up, along with HR, Legal, Compensation, etc. That normally takes a minimum of 5 days after the interview.
I Doubt it is Statistically Significant (Score:2)
If you look at the listing of 20 tech positions, the Software Engineer position is a strange outlier. Its 35 day duration is almost 7 days higher than the #2 position, Senior Applications Developer, which is 28.3 days. The rest of the time-to-hire durations group together much nicer, which the overall trend being more senior positions taking longer and entry level positions taking less time.
So the duration for senior level tech positions appears to be around 27-28 days, which is what the summary should have
Re: (Score:3)
What is the difference between the two? I have yet to hear a good definition of the roles.
Re: (Score:2)
There is no real difference. I've been a Senior Software Engineer and a Senior Software Developer with essentially the same job at different companies. I think Senior Software Engineer sounds cooler, but Senior Software Developer is probably a more honest title. (I have no degree in a computer field, nobody cares whether or not I've passed any tests, and what I know about software engineering I've picked up on my own.)
Re: (Score:2)
But is there a REAL difference? Is there an agreed upon criteria or is this just whatever someone feels like that day?
Re: (Score:2)
My current job took over 6 months to get me the offer. First they interview me. About a month goes by and I finally hear back that one of the interview committee dropped out so they had to start over again. I was brought back for an interview with the same panel with one different person. They then proceed to ask me the exact same questions they asked me the previous time. I found out later they have a rule that all interview questions are prepared ahead of time, approved, and then must be asked of every c
Re: (Score:3)
So, how's Oracle as an employer shaping up for you? Do you like working there?
Re: (Score:2)
It's that long because there's oversupply of tech workers, so they get to wait for 100 applicants and then run through everyone to negotiate as low a salary as possible. This is the result of government-supported college education and a poor K-12 primary education system, instead of market-supported career education and a functional K-12 primary education system.
Re: (Score:3, Insightful)
Not really. The prospective employee usually has a job, and is working. You have a vacancy, so you're not really "losing" work. It does however balloon scheduling issues and leaves some low priority work undone. In theory the low priority work is necessary to do, but does not cause anything to explode if it waits a couple weeks. There is certainly some lost work here: people are being rejected, losing some amount of man-hours on each reject in the screening, background checking, profiling and interviewing.
Re: (Score:2)
I don't necessarily think the pool is adequate. Even if we're desparate for an employee to fill a long vacant position, we're not going to hire the first warm body that submits a resume. No employee is sometimes better than an inadequate one that wastes everyone else's time. Of course where I am there really are fewer qualified people with relevant experience and skills; though in a high volume popular job type with high turnover (IT grunt) the time it takes to get hired is probably faster (show your Mic
Re: (Score:3)
We're hiring engineers, not fast food workers who only need to be warm bodies. It takes time to evaluate someone. If you hire the wrong person you waste far more money than if you actually verify if the candidate is a good fit.
Your emphasis on "every single time they change jobs" is a bit bizarre. It would be a good thing if we slowed down the revolving door, get employees who stick around longer. If you want employers to stop treating you like an interchangeable cog, then you need to stop treating your
Re:So what? (Score:5, Interesting)
Works both ways man.
Have you considered why applicants have a history or job hopping? Hint: the common factor is the employer not the employee. So, as an employer, be different - stop being 'that guy'. You might be ahead of your competitors by being a more attractive employer.
Is it possible that holding job hopping against a candidate is really a sign that you, as a recruiter, are ignoring the job market? You know, the real job market where there is little to no vertical movement? The one where a person can only be 'promoted' by lateral movement in switching companies... perhaps to a competitor?
You are dealing with an environment you spent decades to create. Now you bitch that it didn't produce voluntary slaves?
Might not have been you personally but fuck yourself. You spent time following along rather than trying to change things for the better.
Life isn't fair is true. So, there are two choices: follow along fucking other people trying to avoid getting fucked yourself (ie - just bend over) -or- try to change things so life is more fair than before. (ie - fix that fucking problem!)
What side are you on?
Re:So what? (Score:5, Informative)
There's a reason previous generations stayed in their jobs longer, and it has nothing to do with the current generation's lack of work-ethic/loyalty/etc., and everything to do with the changes employers have been making over the last couple of decades: No more pensions, no more promoting from within the ranks (You're either management caste or you're not), constant cost-cutting (what training budget?), layoffs at the drop of a hat, etc..
Employers have been systematically training any sense of loyalty out of the workforce, don't complain that you've been successful.
Re: (Score:3)
If you want employers to stop treating you like an interchangeable cog, then you need to stop treating your employer like an interchangeable paycheck provider.
Did it ever occur to you that many of us have just adapted to the environment that you (the royal you) created?
Let me put it this way: If I remained at the employer I worked at 10 years ago, my salary ($50k/yr at the time) would still most likely be less than 1/2 of what I'm making today, and that's counting the 'OMG we're hurting so bad financially but look - we're still being so generous!' 1-3% annual raises. Nice folks to work with, but yanno? fuck that.
BTW, it's not just money - I left my last non-contr
Re: (Score:2)
Unfilled vacancies translates to lost sales. As a hiring manager, we get pounded by upper management to fill slots as quickly as possible, and end up wasting time reexplaining the process to them every year or so, even though our numbers have been consistent, and lower than industry averages.
Re: (Score:2)
several of our Software Engineer jobs have been open for over 2 months and they are still open.
Vacancy duration is a different problem. This study was about Interview duration.
My guess is we don't pay enough - or people presume we don't pay enough.
More likely your HR department is bottom feeding, only sending you candidates who are asking for below average salaries.
Re: (Score:3, Insightful)
If you want me to take less money, you need to provide additional value elsewhere. Better environment, equity, bonuses, vacation days, work/life balance, etc. If you don't why should I work for you over taking the money? If you do, you need to sell that.
But having positions open for 2 months, especially if you're looking for experienced developers, isn't uncommon- in fact if you were filling most of your positions in 2 months you'd be amazingly good at recruiting. Good developers are hard to find- that
Re: (Score:2)
Well maybe, but it sounds like the right kind of candidates aren't showing up for the interview which makes it kinda hard to give them offers. Unless they're being overly up-front and present a low and narrow salary range, I'd look into other reasons why they're not attractive enough. If they are scaring them away, be less specific and say you're ready to offer competitive terms for the right candidate. Then you might at least get the right kind of people in the door and maybe sell them on the other benefit
Re: (Score:2)
There are the cool jobs that everyone wants but hardly anyone gets. Then there are the uncool jobs (anything not at Google) that no one wants because they're still trying to get the cool jobs. Plus if the skill sets you want don't match the current fads then it's hard for the recruiters to find people. The economy is still pretty crappy right now and a lot of smart people still want to stay put where it's safe and stable.
Sometimes the recruiters just aren't good at finding the right people.
Re: (Score:2)
Since they often don't know what the key words actually mean it's very difficult for them to do so. That's the problem with using general recruiters instead of getting someone with a skillset related to that of the person you want to employ involved early in the piece. If the perfect employee lists a skill of which the desired skill is a subset the general recruiter is going to reject them because they only know the key words and not wh
Re: (Score:2)
That doesn't make sense, unless you're saying there are more A people than C people.
Otherwise, having B people in charge, who would be happy to hire C people, should make hiring *easier*.
Re: (Score:2)
I hope they make exceptions for the cream of the crop, or otherwise they will have very few.
For an industry which has billion dollar IPOs without their prospectus's even being read they are awfully selective.