Our company, BeamJobs, is in the hiring space. Since we started in May of 2018 I’ve had the opportunity to talk to close to 1,000 software engineers about their job search. Far and away the most common feedback I get from engineers is how much they thoroughly love looking for a new job and how when they’re on vacation they yearn for those times when they were updating their resume. Just kidding, getting a new engineering job generally sucks (roughly ⅔ of those 1,000 engineers had a negative experience in their most recent job search).
For the last few weeks I’ve been trying to figure out an angle to write about why looking for an engineering job is so egregiously sucky (it's in merriam-webster so I'm counting it as a word). I think the fundamental reason is that there is a huge cost to finding, applying, interviewing, and ultimately landing a new engineering gig in terms of time and effort required. In this article I’m going to calculate the opportunity cost for the average developer to get one job offer. Opportunity cost is the amount of money that you could have earned if you had been working instead of say, doing an interview. Now, this is not to say that you necessarily would have spent an hour working instead of interviewing (if history is any indicator I likely would have spent that hour napping) but it’s a helpful framework for converting time spent into dollars.
I don’t want to bury the lede so here are my results. Based on some rough calculations (which are detailed below) it costs the average software engineer $1,814 and 1.7 vacation days to get one job offer. I broke the job searching process into two stages to get to this total. First, it costs $600 to find and apply for the requisite number of jobs to get one offer. Second, it costs $1,214 to interview at the requisite number of companies to land that offer.
At BeamJobs we have a free product for software engineers to deliver highly customized monthly job recommendations right to your inbox. We search the internet for the engineering jobs you’re looking for so you don’t have to. We’re looking for early beta users and we’d love your feedback!
In my experience engineers are generally in one of two states of applying for jobs. They’re either actively applying or passively applying. Active job candidates are reaching out to their network, looking on job boards, using job marketplaces like Hired, etc. Passive candidates are largely responding to cold emails or LinkedIn messages from recruiters or are selectively applying to roles that they stumble across. The big difference is that active candidates are seeking out jobs to apply to and passive candidates are letting new opportunities come to them.
I make this distinction because the cost (in terms of time) of finding and applying to jobs is significantly higher for active candidates than it is for passive candidates so that’s who we’ll focus on in this section. To get at the cost of finding and applying to enough jobs to get one job offer for the average software engineer we’ll make the following assumptions:
This $600 opportunity cost applies mostly to engineers who are actively applying to new roles. The opportunity cost for passively looking engineers is largely concentrated in the interview process (which we breakdown the cost of in the next section). Reduce this cost by using our job recommendation tool. We’ll send you five hand-picked jobs each month that you’re qualified for and that match your interests, no effort required on your end.
Congrats, you got past the resume review part of the application process and now you can start the interviews. This is more expensive part of the job searching process for engineers both in terms of opportunity cost and in terms of stress. We’ll make the following assumptions in arriving at the opportunity cost of interviewing for enough engineering jobs to land one job offer:
Based on this model, the total opportunity cost for software engineers to interview until they get one job offer is $1,214. This is in addition to the very real cost of having to take 1.7 days off work! Keep in mind, this is a conservative estimate. We’re not factoring in take home assignments, the time it takes to prep for interviews, travel if needed, etc…
There are cool companies in the hiring space, like the aforementioned Triplebyte, that are reducing this cost by having engineers do one coding challenge to get multiple in-person interviews. The issue for engineers is that only 3% of people who take Triplebyte’s coding challenge pass it. Therefore the other 97% are left to incur all of these interview costs.
Very few non-sadistic engineers actually enjoy the process of finding and getting a new job. It takes time, it’s stressful, and you often don’t know where you stand with a given company. The framework we laid out here is just a very basic tool to approximate the opportunity cost of getting a job offer for an engineer. There is a ton of variation around all of the assumptions that I’ve laid out. I wanted to go through this exercise to give our company something to strive for. Our ultimate goal is to reduce the opportunity cost (and associated stress) of finding the right job for engineers to as close to $0 as we possibly can. We’d love if you joined us on our journey!