I think "culture fit" here is a replacement for: "He isn't young and single and probably has a family, therefore he won't want to work 70 hours a week and stay in our awesome fully stocked with free soda and snacks office 24/7 and instead actually go home after normal work hours, and we can't have that."
Indeed, I find it a big red flag when I hear mention of "efforts" to reduce homogeneity. Frankly, any mention of any "social engineering" terms is a big red flag for me.
The only thing that matters is professionalism, work-ethic, and skillset (and my personal favorites, politeness and personal-space respect).
Age, race, gender, nationality should not matter in any way for hiring decisions. But then again, I fall into the "leave it be" side of human freedom and anti-discrimination efforts, rather than the "let's meddle and try fix it with reverse-effects" camp.
People who are all alike tend to have the same blindspots. If you have a group with different POVs, they can more easily catch things that others might miss. Race/gender/age/&c.-related blind spots may be more important in some domains than others, but these blind spots are very salient in a wide variety of places in American life.
fit the culture is just pc phrasing to dodge hiring issues. its a cover, nothing more. some people saying it may believe it to be a true concern but its just code for "we don't want your type"
Focus on cultural and racial diversity in my experience tend ignore age as part of diversity. Lets not pretend 'they' would actually give a fuck about older developers.
> Diversify was a weekend event at Spotify in Stockholm, where 40 tech students of diverse backgrounds came together and designed, wrote code, and found new friends.
Maybe having students to this is in part pointless, but that picture is not of a group of Spotify employees working on diversity issues.
Not all companies are like that. We put a huge emphasis on culture fit but it's nothing like what you suggest. We've gotten far more diverse as we've grown.
What is your definition of culture fit then? Be specific about traits which are indicative of a good or bad culture fit for your team/company in particular.
Is this person going to be goddamn annoying to be around 40-45 hours a week? (Oh, how this has happened.)
Does this non-medical phd demand to be addressed as doctor? (Yes, this happened.)
Does he or she seem willing to do his or her share of the scut work?
Is he or she a failed academic who is getting an industry job and going to be a pain about it, or is this what he or she wants to do?
How much supervision does the candidate require? Initiative? If he or she runs out of work, is he or she going to to sit there and do fuck-all until I notice or will the candidate be proactive about getting more to do?
I understand some of our code is under tested, but unlike TDD wankery, there is a real business cost to spending a bunch of time writing tests and, since those systems are either mostly finished / slowly changing, or on their way out, is this candidate going to be difficult or suck it up and deal? (Yes, this happened. See also scut work and/or the realities of living in our fallen world.)
We've made a decision to standardize on scala/java and js/some frontend package I'm not sure of. I understand this isn't react or the new hotness; does this candidate seem like he or she will throw a fit then spend two months working on a service in a language nobody else uses (yes, this happened. And he was surprised when he was terminated. There were other issues but this was the proverbial straw.)
Hygiene. This should go without saying, but apparently I am cursed. If I can smell you in an interview, we're done. (And yes, this has happened.)
One more set of edits as the bad memories come back:
You look at my two female data scientists and a female engineering peer and the one female office manager and ask why there are so many secretaries working here? Yes, this happened.
You call one of my female directs "sweetie." Yes, this happened.
We're talking on the phone and you couldn't be arsed to spend 10 minutes on our site and come up with a 1-2 sentence summary of what the company does. You can be wrong, but you must demonstrate minimal interest. And to be clear about the level of detail: if I were airbnb and you said platform to allow people to rent out their homes for short stays, that would be awesome.
I don't think any from that list is really cultural. They range from basic professional behavior to basic polite society behavior. I've run into people with the hygiene part. I've dealt with farmers who have just dealt with their pigs that smelled better than some folks I've encountered.
Also, "sweetie", really? When I was younger (teens) I offended someone by saying "Ma'am"[1], but I'm pretty sure I would have took a swat to the head from my parents if I ever said "sweetie".
1) I'm pretty sure at this late date (20+ years ago), she was a bit ticked that I used "Ma'am" instead of "Miss" implying she was older than she was. I'm pretty sure she was between 18 and 20, and I was 15 and looked a lot older.
Professional and polite behavior is cultural fit :) Or at least the working definition at this and previous employers where I've been a hiring manager.
>I don't think any from that list is really cultural
It looks to me like a laundry list of requirements that they wouldn't admit in polite company or want to have documented in their company records, or advertise on their website.
They wouldn't want to put off any investors with bad breath, a PhD, or a penchant for saying 'sweetie', after all.
Also, one of the items clearly advertises an objective deficiency in their working practices. It's pretty plain why they'd want to keep that under wraps.
So yea, less about culture and more about having a list of hidden requirements.
>I understand some of our code is under tested, but unlike TDD wankery, there is a real business cost to spending a bunch of time writing tests and, since those systems are either mostly finished / slowly changing, or on their way out, is this candidate going to be difficult or suck it up and deal? (Yes, this happened. See also scut work and/or the realities of living in our fallen world.)
I had a feeling that somewhere along the list of "candidate must not make us put up with any of their bullshit" there would be something saying "candidate must be willing to put up with a metric ton of our bullshit".
either mostly finished / slowly changing, or on their way out
Most of those old systems support a part of the business that is dying and are maintenance only, but occasionally they do need some extra duct tape. We minimize any investment at this point. At this point it's a day or two of work a month spread across a team, but everyone takes a turn.
I don't see the point. Either shut it down completely because it's not worth the investment to maintain or do it properly.
Test driven development is a practice that is most valuable on legacy code. Only doing it on new code and not old code is ass-backwards. If anything it should be the other way around.
A half assed hack job to support remaining customers will likely only end up alienating them when you inevitably break stuff they rely upon with duct tape. Alienated customers tend to drop you forever and run into a competitor's arms. YMMV but that's always been my experience.
The point is money. It shouldn't be hard to imagine a business that is earning money but will never again grow, is worth no further investment, and is therefore being run out. I reread what I wrote; you appear to be deliberately obtuse.
> Hygiene. This should go without saying, but apparently I am cursed. If I can smell you in an interview, we're done. (And yes, this has happened.)
Just a note: sometimes this is BO caused by medication. You want to avoid saying "I didn't hire you because you smell" because that may be a result of a protected characteristic. A reasonable adjustment would be that the person has a trusted friend who will tell them if they smell or not, and will shower before they get to work and will use deodorant products.
Back in high school I worked with a guy who had BO. His roommate (who I also worked with) told me that he didnt actually have a hygiene problem. Showered every day but for some reason he still had BO. I'm not sure how true that is but thats one data point.
Since some food and medicine can cause your pee to smell really weird it makes sense it can screw with the smell of your sweat too.
> Does this non-medical phd demand to be addressed as doctor? (Yes, this happened.)
WTF is wrong with that!?!? It is polite to address someone the way they want to be addressed. I address my PhD holding colleagues as Dr. very often though none are medical doctors. I can't imagine how this is an issue for anyone ever.
Unless you're an MD, I'm not calling you doctor, and it's a 5-nines indicator you're a jumped up prick. In english, Dr. is a honorific reserved for MDs, dentists, and psychiatrists.
If you ever have to work in an academic setting then you will probably see a lot of folks requiring the title. It's a pecking order thing and there are rules.
DEAR MISS MANNERS: My future sister-in-law just graduated with her PhD She told me to call her “doctor,” but I was always told that if you don’t work with someone directly in their field, that doesn’t apply.
Is that true? I understand it’s out of respect, but I have never addressed other persons with their PhD as “doctor.” They also put PhD at the end of their names, teach at universities and don’t go by “doctor.”
GENTLE READER: There are two attitudes that individuals and universities take toward the use of the title “doctor” for those who hold PhDs.
One is that having been earned, it should be used, not only in professional situations when needed for identification, especially in academic positions, but also socially.
The other is not to use it — not socially, but especially not in academic positions, because that level of education being assumed, it need not be expressly mentioned. As one professor (namely, Miss Manners’s Uncle Selig) once put it, “A PhD is like a nose — everyone has one. It’s only conspicuous if you don’t have one.”
Which form of snobbery is preferable, or perhaps more effective, others can decide. Obviously, your prospective sister-in-law espouses the first-named approach. And she is covered by two rules:
You're conflating personal and professional. In your private life, you're free to be a prima donna and demand whatever your family and friends will put up with. At work, you're not, and unlike Ms Manners, I'm neither your friend nor a family member that has to humor you. Demanding that people play status games is going to get you a fiat no-hire from me, in part because you will find many of the tasks beneath you. And such a person would be unlikely to tolerate calling his or her managers Mr. / Ms. X. As should be obvious, if being called doctor is a deal breaker for you, there are lots of other employers. I think you're unlikely to find many in the valley that will tolerate such nonsense, but it's a free country -- anyone can keep looking until he or she finds a company that tolerates it.
"Culture fit" in this case appears to mean "don't say or do anything, no matter how minor or symbolic, that might be construed as a challenge to my authority over you".
i.e. it's a big fat euphemism.
Just say "no prima donnas" on your list of requirements. Most people will be able to read between the lines and know that you're looking for servility, fealty and obedience in your employees. I, for one, would be happy to screen you out based upon those words. I'm pretty sure you wouldn't like me, I wouldn't like you and I wouldn't want to waste your time or mine interviewing with you. Those three words would save us both a lot of trouble.
I get the feeling in my extended family that words would be spoken to the sibling to indicate that the future sister-in-law was either "too big for her breeches" or the sibling might want to reconsider the whole thing. No disrespect intended to either the future sister-in-law or Miss Manners, but family is first names or nicknames.
I get that there's an academic pecking order around this. But I work in industry and see previous post about people who couldn't hack it in academia and want to come to industry and treat it as if it were academia. They will not work out, and I'm uninterested in having their pecking order games in my team.
I, OTOH, am appalled by how the medical profession has stolen the title 'doctor.' A doctor should be someone who has expanded the sum total of human knowledge by performing original research; an MD is just a technical degree.
I always refer to those who have earned an MD as 'physicians' or 'surgeons.'
What you describe isn't culture fit, but not hiring arseholes. 'Culture fit' suggests traits that aren't suitable for your company, but are suitable for others. Your list is a series of bad points for pretty much any company.
It's interesting how many red flags a company can throw up so quickly. Often before you've even finished browsing their website.