How do Software Developers choose between job opportunities?
How do Software Developers choose between job opportunities? What do they consider before applying; once they apply, what they value, and what do they hate?
Index
Introduction
If you are an employer who is trying to recruit good Software Engineers, you’ve got to ask yourself - why would a candidate be attracted to work in your team, as opposed to any other team in London? When applying to roles, what do Software Developers value the most? Is it flexible working, or specific technical tools, or perhaps simply compensation/salary? And once they talk with a potential employer, what do they dislike the most?
I believe that information like this is very useful. If a particular company/team is self-aware about how attractive they are to the external market (i.e. the pool of talent in their industry), they can address their weaknesses and play to their strengths, in order to maximise the chances of securing new employees.??
The Covid 19 pandemic and the ensuing shift towards remote working had significant effects on the job market within Software Engineering in Financial Services. One of the effects has been blurred lines/separations between various industries, when it comes to developer choice of where they want to work. I’ve seen an increasing number of developers from Banking migrate towards crypto companies, fintechs, or even big tech companies. And interestingly I’ve seen the opposite trend too - a lot more people from tech companies moving into more traditional finance / trading firms, etc.!
This fluidity, together with the fact that the post-covid market seems to be overall booming (there are lots of advertised job opportunities), definitely makes this a “candidate-short” market where good Software Developers have a lot of choice. In the recent months, I have seen many clients in the financial sector struggle (a lot!) to reliably attract & secure candidates.?
All of this made me question - is there a common trend on how developers choose what opportunities they apply to, and what they generally like / dislike once they actually engage in the interview process? Of course - to some extent, everyone is different - but given a large enough sample population, perhaps it would be possible to discover general insights, which employers could use to increase their probability of success in attracting talent???
Survey??
This article is based on a survey of Software Developers, mainly the mid-senior end of the market, within Financial Services (trading technology) - across Banking / Crypto / FinTech / HFT Trading. 52 participants completed the survey. The survey has 2 parts:
Results Part 1 - what do Software Developers value? (1 - value least; 5 - value most)
Also, a couple of survey participants said:
Results Part 2 - once they apply to a role, what do Software Developers hate (or dislike most)? (1 - dislike the least; 5 - dislike the most)
Also, a few survey participants said:
领英推荐
Analysis
Part 1 - what factors do developers consider when comparing roles / companies?
What’s interesting is that even though the technical aspects of a role (such as tech tools / interesting project) are still quite high up in the priority list, they are surpassed by the more “soft” factors in this list - i.e. culture fit and work-life balance/flexibility both rank higher than the “technical” qualities! The most valued factor, perhaps unsurprisingly, is compensation.?
This suggests that, generally speaking, when choosing between job opportunities, software developers mostly care about money, as well as the quality of their personal & intrapersonal lives. That is not to say they don’t care about the “technical” aspects of a role; but that compensation and work-life balance/culture seem to be of paramount importance, in comparison with all other aspects.?
Another way to phrase it would be: it’s reasonable to predict that, generally speaking, no matter how interesting a technical problem or how exciting the technical stack, a developer will not be attracted to work in a particular team if he/she is underpaid, doesn’t like the people in that team, and / or cannot incorporate that role into their personal schedule (work-life balance).
Another interesting finding - what developers valued as their lowest priority factor was company brand (external recognition / prestige). This suggests that programmers (at least within Financial Services) are generally quite cynical / disinterested towards overall corporate image.?
The reason I think this is interesting is - I have personally seen a trend where companies that have good / impressive names, such as the big Tier 1 Banks, or some of the well-known firms in the fintech / crypto world - behave in a slightly assumptive manner towards candidates. The implication in their behaviour seems to be that the brand in itself should be enough to attract most candidates. This contradicts the findings in the survey - I would predict that if the top desired factors are not present (compensation, work life, and good culture), even top firms will struggle to reliably attract talent.
Part 2 - what do developers hate most during interviews?
According to the survey, the clear “most hated” event encountered during an interview process is unpleasant interviewer personality. To me this is not surprising. As a recruiter, I have witnessed a lot of good candidates being immediately put off by interviewers who appear either arrogant / abrupt / aggressive / non cooperative / unenthusiastic / disinterested, etc. In my experience, even if these interviews are for “good” companies and roles, such an interaction usually leads to the candidate withdrawing from the interview process or at the very least losing a lot of interest in the role. I suppose that this naturally ties in with the previous section category company culture, and reinforces the point that programmers care a lot about culture fit.
The 2nd “most-hated” factor encountered in the interview process was a long and/or slow interview process. Once again - personally I don’t find this surprising. In a fast-moving market where candidates have opportunities across multiple industries, they are exposed to a wide spectrum of interview process types, and many of the more modern firms are very slick in this regard. And it’s not just the “techy” firms which exhibit efficiency with their interview process - even teams in traditional Banking can be quick. In those cases, the entire process can be completed in 1-2 weeks (all the way from initial intro to offer on the table).?
On the opposite side of the spectrum, some Investment Banks take 2-3 weeks to even shortlist a CV for an interview, then have 5-7 interview steps (with delays for feedback in between), and the entire process there can take 2-4 months. By the time this hypothetical client selects their first batch of CVs to interview, those candidates could already be gone from the market!?
Advice to companies - 4 Scenarios
In reference to the above survey, companies & their interview processes can be classified into these basic categories:
In the real world, it’s not black & white, and most companies will fall somewhere in between Categories Attractive & Unattractive; and their processes between Attractive & Unattractive. However, generally speaking, my advice would be:??
Companies & teams within those companies should be aware of how “Attractive” they are to the external pool of talent in the market. It is reasonable to assume that this quality (Company / Role Attractiveness) determines how many good applicants the respective hiring manager will receive. According to the above survey, the top 3 company/role characteristics that Software Developers value most when considering opportunities are:
Some company / role characteristics such as Compensation may be very difficult to change (though not impossible); however, I would argue that there still are aspects which a company may improve, for example:
After the CV submission stage, when the interview process begins, companies & teams should be mindful of their approach to conducting interviews, because this leaves a strong impression on the interviewed candidate (which can be positive or negative). Even if a certain role appears as a very desirable one and entices a lot of good candidates to apply to it, a poor interview process can significantly impact that team’s ability to reliably attract talent.?
Here are some things which companies can do to make their processes better:
Conclusion
I think that in a candidate-short market, employers should recognize that they are in fierce competition for talent. They should understand how they measure up against their competitors in terms of the various factors that Software Engineering candidates find important - such as Compensation, Work-Life Balance, Technology Stack, Culture, etc.?
If your company cannot pay the highest salaries, what are the other characteristics of your team that would be considered attractive? Make sure to clearly highlight these!
Also, during the interview process, it is important for employers to be conscious of how they come across. For a candidate, the interviewers are the face of the company. If the candidate doesn’t like the interviewer or the interview process, it’s quite likely that they will also lose interest in the role.
Whether you’re a hiring manager working for a large Investment Bank, or at a small fintech / crypto company, these days (perhaps more so than ever before) you are competing with a lot of other teams for the best engineering talent. I would advise you to play to your strengths in order to ensure successful recruitment efforts.??
very interesting read Gus. Food for thought in there for employers about whether they actually test/assess interviewing skills specifically as a competency of their team before kicking off a recruitment drive. I think it's just assumed that anyone can do that - which is definitely not true and your research shows the potential consequences..
Operations Director for Pulse Doctors and AHP (part of the Acacium group - Responsible for Locum and Perm across NHS and Private Health Care
2 年Sharing for further reach. Thanks Gus for sharing