Is ‘culture fit’ merely a code word for unethical discrimination?
I have been researching hiring in the tech industry and this is the glaring elephant in the room. In the very least, the widespread acceptance of this abstract category opens up a convenient laundering term for abuse. And in reality, it’s glaringly exactly that.
The general HR rhetoric seems to only highlight the problem. If ‘culture fit’ is merely a matter of good/bad attitude, why are we referring to it as “culture?” These are very clearly separate items. The way they are being treated as interchangeable is beyond suspicious to me. “Culture fit” is used in broad contexts while any query is answered with concerns amounting to attitude differences. In a time when “identity” also suffices for “culture”, how can this possibly be reconciled?
I argue it can’t be and this is another shameful chapter in the tech world’s going list of hypocrisies. Prove me wrong.
62 comments
[ 2.0 ms ] story [ 123 ms ] threadI can't, I agree with you.
Company "culture" is whatever management decides it is. Unlike real, organic cultures, company cultures are engineered and dictated from the top, and employees don't alter it (as members of organic cultures do) but are merely expected to conform to it. Amazonians didn't create Amazon's culture, collectively, it is literally the cult of Jeff Bezos, and is "peculiar" by mandate.
So "culture fit" is just a meaningless box into which to throw the personal prejudices of whomever is hiring you (or choosing not to hire you) and to provide them with sufficient plausible deniability, because they can't just say they don't hire anyone over 30, or that they would rather not have women or certain ethnicities around, because it makes them uncomfortable.
So anecdotally, it seems like culture fit for Amazon is largely about what you're willing to put up with. There might be a component of that at a lot of places, but clearly different companies do have very distinct "cultural" differences. Basecamp is certainly no Amazon. The diversity of different criteria among businesses makes me feel like it's not a particularly unethical practice (obviously it can be, but I don't think it is typically), and overall cultural fit would probably make you happier at whatever job you do end up at.
And so you say they’re not a good fit, and that’s that. It can’t be proven incorrect because culture fit is a nebulous idea to begin with. It’s a catch-all for whatever you don’t like, basically.
conservative compliance vs. going right to the edge of the law
meticulous design and testing vs. move fast and break things
command-and-control vs. self-organization
IM vs. voice calls
9-5 vs. flexible hours blurring work and non-work time
likes the same kind of music as me vs. doesn't
Some of those seem okay to me to consider, and others don't. I don't see a bright line. I'd tend to agree that "cultural fit" with no further explanation tends to mean something bad.
1. We don't like you and we don't know why
Or
2. We don't like you and don't want to tell you why because the reason is against their law/might lead to a lawsuit.
Or finally:
3. We don't like you but want to sugar coat it a bit because we don't want to make you extremely annoyed/upset.
In some cases, that can really be a codeword for discrimination, since telling someone they're not hired because of their race/gender/age/nationality/whatever is against the law. But in other cases, it can often just be that the company has one way of working/prefers one environment and the candidate has another. If someone just doesn't get along with the people already at the company, well that's not necessarily discrimination if they don't get hired by that company.
So yeah, it depends really.
YMMV
Culture fit is also a way of excluding jerks. You encounter some abrasive, abusive, or misogynistic personalities in tech. People usually don't want to say "this candidate is a jerk", so they use "bad culture fit" as a euphemism. Once the answer is no-hire, the details don't matter anyway.
Building a team that works well together is extremely difficult. Unless you've actually hired dozens of people and seen them either work well as a team or kill productivity with interpersonal conflicts, better not to sit in judgement of people who have.
I think it is simply a convenient, sufficiently vague, unarguable reason to say no.
It's important to understand that people feel very uncomfortable rejecting another person, and in recruiting, companies really prefer not to give any reason at all - this is because they don't want the candidate to come back arguing with the reasons given for the rejection.
So "not a cultural fit" is just an easy way to say no thanks, whilst giving a "reason" that can't be argued with.
It's not discriminatory.
Maybe it's not necessarily discriminatory but almost certainly has been in instances. So really it can be either.
Same industry, same demographic mix, same company even. Very different cultures (which, interestingly enough, both worked well). Then, they merged the two factories into one organization, and you saw that "culture fit" was not at all an abstraction; the first year was very rough for all concerned, and a lot of people quit.
Also, in this case, because it was a bunch of engineers with a similar demographic mix, not a code word for racism or any other unethical practice. It was culture; I can think of no better word for it.
To some people culture fit might mean "I'd hang out with this person on Sundays." This of course is problematic and can let in all kinds of biases leading to discrimination.
Ideally culture fit is about whether a person can fit in to the processes in place. Do they value testing? Are they comfortable with the level of ambiguity that will be found in their assignments? Etc.
I'm in favor of the latter, but it needs to be evaluated based on direct questioning to limit the impact of biases i.e. "Would you be comfortable being required to have 100% test coverage on the code you write?" I've certainly seen folks come out of an interview confident that someone wouldn't be comfortable with ambiguity just because they said that at their current job they are given detailed specs to implement.
"Culture fit" is a lazy term that, at best, means easy compatibility of work style. Normally, though, it means "like me", and from there it's a pretty short road to unethical forms of discrimination.
I would argue that most companies really want/need "culture add" and "values fit". The stated values of the company tend to at least be aspirational and exclusive of things you don't want at your company. But the culture is an emergent aspect of the people who happen to be there, what they're into (good or bad), and how they prefer to interact. If you only want people who fit into that box, you may be numerically growing, but you're stagnant in perspective.
I personally believe it is a way to discriminate. If you interview someone and you can't give specifics as to why you don't like them other than culture fit, it's something you are scared to say out loud.
But some have that for a good reason. I applied at a tech company recently whose product I am a fan of. Did well on the phone and in person technical interview. But after that, they kept asking how I like to work and how I felt about open office spaces(told them I can deal with it so long as I can put headphones on while doing technical work that needs concentration and that I felt some tasks are best dealt as a team while some should be developed and matured before involving others). Needless to say, I haven't heard back from them. But my point is that even I felt a bit of a cultural incompatibility( I was willing to make it work but they saw it as unworkable I guess).
Frankly, I don't see how a 50 year old person (not myself,I'm in my 20s) can be culturally compatible with people young enough to be his/her grand child. Or how a coder from asia can have the same work culture as west cost americans.
There is this view that the culture and values made all these tech unicorns what they are. Maybe that's true but I keep wondering whether or not the same group of smart people but culturally diverse could have acheived the same goal so long as they all agree to use rationality,communicate openly(in an inclusive way) and agree on what the goal and their role in the organization is.
I like to think silicon valley startups to be more or less as culturally exclusive as 80s era IBM,bell labs or Xerox. Which is why I keep doubting the culture narrative. Smart people make smart companies and smart enough people should be smart enough to make cultural diversity work (my humble opinion).
30 years is generally one generation, not two.
And "culturally compatible" enough to work together is way different from being culturally compatible enough to date, or whatever.
Aegism in silicon valley is a chronic problem, are you saying it doesn't exist or are you claiming "culture fit" isn't used to push out older workers at some companies?
This is my interpretation of those terms and how I use it personally. My basis for behavioral traits is based on personal experience as well in working at a large number of companies in various roles, industries, and positions. I don't believe that it is at all discrimination because I'm using my best judgement for who can work most effectively with my team. That's just smart business.
This alone may not dissuade me from hiring someone, but things like this add up in the negatives column.
A lot of the candidates we’ve interviewed just don’t have the experience working in that sort of environment. We don’t have time to write code perfectly at the moment with pairing, full test coverage, fully TDD, etc. Yes people can learn this, but if you come across as someone who will just spend all day conplaining about that I don’t want you on the team.
Another thing is simple skills like turning up on time. We recently had a couple of on-site interviews (after phone calls) where the candidates turned up more than 30 minutes late, with no good excuse.
That alone certainly isn't sufficient to make the criterion acceptable under US law. Like, for an obvious stupid example, a team full of men who don't think women belong in the workplace doesn't let you reject all the women. This is true even though the female candidate would genuinely be less effective at the job because of this. (And I don't mean to suggest that you think otherwise--I'm just saying that the criterion you give is not sufficient by itself.)
For real, it gets murkier. A team full of kids who grew up rich, and are (like most of us) most comfortable around their own kind? A team that happily and effectively resolves its technical conflicts by yelling insults at each other, and then getting drunk at a bar? This is where the culture wars get fought, and the lawyers make their money...
Yelling insults at each other is a perfect example. In some cultures that works, in others it does not.
At some point, the disparate impact of selecting for a behavior may select against a protected class by enough that it becomes illegal. You also have potential to get stuck in a local maximum, where you're hiring the best candidates to work with your existing team, but in doing so excluding a huge chunk of the global candidate pool. I agree that team fit is important, but it comes with a lot of asterisks.
Does one behave their race or gender away? No.
However, I also once faced with a case, when manager didn't want to hire an engineer, because she thought he wasn't 'culture fit', although he was a great engineer. Technical members of hiring committee managed to convince her otherwise and then this person became in a sense the heart of the team, everybody liking him more than anybody else.
So, in my opinion 'culture fit' should always come from within the team a person works in and it should be a collective opinion, not an opinion of a single manager.
I was on another committee one time where the candidate was muslim and had to pray during the four hour onsite technical interview. My boss said we couldn't hire him because he wouldn't be a good culture fit.
One of those teams I stayed on for 2 good years. The other I wish I had quit earlier.
To me, it doesn’t matter if the candidate “fits in” with today’s culture, it only matters if I will still want to work at the company after the new person is part of its culture.
If only you could actually predict this from interviews!
As is, all you can do is try to put the candidate in job-like scenarios and evaluate specific “culture” attributes like “is open to criticism” or “listens to collaborators” or “codes with a concern for future readers” or “has a positive attitude toward code reviews”. It’s still much easier to disqualify than to endorse on those criteria. Hiring is hard.
1. Can they do the job 2. Will they like the job 3. Will I like working with this person
The third is really where "culture fit" comes in. When you have multiple candidates that qualify for a role, how do you choose between them? You will naturally pick the person you hit it off with the most, which will more than likely be someone like yourself. It is definitely unconscious bias, but I'm not convinced it's unethical discrimination. This is the basis of all hiring ever...not just tech.
People are going to prefer who they choose to prefer. You're not going to build a better team or get better hires by consciously picking people you or the team doesn't want to work with...at least in collaborative fields. To call that unethical is disingenuous.
The way to minimize the influence of "culture fit" is doing more upfront thinking in the "can they do the job" category so you aren't just choosing between two people who both know javascript. Usually the only soft skill I see on a job description is "effective communicator," which is fluff. Think seriously about what it means to contribute to a team, how they contribute, and how you want teams to reach consensus and work together.
This was the best place I have ever worked. Problems (and successes) were shared. Internal conflict was very rare. If one person was overloaded, the team would work out who might be light on work at the moment and could assist. Work hours were very flexible - outputs not inputs were what mattered. We had a lot of autonomy and were encouraged to be creative and take some risks in developing new tools and services.
The employees were from a diverse range of ethnic and religious backgrounds. The male/female ratio was probably around 60/40 for a company of mostly engineers. Age of employee was mixed but favoured younger engineers. The company was a consultancy so it was a place people would work at to gain diverse experience then move on to specialist positions elsewhere. It was rare for older engineers to be looking to gain diversity of experience.
Given the personality types - this meant we had lots of really interesting discussions about different countries and cultures and life experiences. So "culture fit" at this company did not mean "the same as me" other that with respect to: will work hard, is intelligent enough, will be a team player.
Sadly, after a few years of awesome work life, some of the owners wanted to cash out and the company was acquired by a multi-national. The culture of the original company was quickly destroyed. No autonomy, ridiculous levels of authorisation (4-5 just to purchase $500 of IT equipment for example), competition from internal groups stealing clients, very few team players, inputs favoured over outputs (lots of "make work" going on). The transition experience really rammed home how real the Peter Principle is and the drawbacks of tall hierarchical management structures.
"Culture fit" to me means rejecting people that won't work within the organisational structure you are trying to build. Note that it doesn't mean non-team players should always be rejected. If you have a team of individuals that largely work in isolation and prefer to reduce communication to a minimum, hiring a team-oriented person could be detrimental.
As for "culture fit" being used as a cover for discrimination, I'm sure it happens. If someone is discriminating then they will want to cover their arse somehow and "culture fit" is vague enough that it can easily be used for that purpose.
Perhaps "personality fit" would be a better term for what I describe above? Though I have never heard it being used and I suspect a lot of-people in tech like to think that merit matters more and could find "personality fit" to be offensive.
Here's why:
Most of us, to a T, are furry trash.
We want to hire someone who seems genuinely excited about the job, and kind of excited about us by extension, so we are making a good chunk of our decision based on culture fit.
Some of our interviews have fit right in. They seem ease. Planning some cosplay or other. Others have reacted quite a bit cooler to the atmosphere. (We're immersed pretty deeply in this weird pocket of the permissive California culture, which I figure must be pretty intense to walk into for a job interview if you're not used to it.)
The ethical bit: Both the primary groups we're hiring from, furry and nerdy, are predominately very white and very male. We seem to have a sort of multiplier effect going where both groups have some diversity but just through probability we don't see any applicants who are not the traditional white male programmer. We'd happily welcome anyone who did not match the visual template, who wasn't weirded out by us, but no one really has yet. I'm guessing we're running up against some sort of systemic discrimination, despite the fact that no one involved in the interaction is intentionally discriminating.
Take that all for what you will, I guess.
--Anonymouse