4 ms·

I go so far as to immediately say no to any candidates who have Meta in their history. Every meta person I’ve interviewed has been an asshole in one way or anot

by op00to 2y ago

I go so far as to immediately say no to any candidates who have Meta in their history. Every meta person I’ve interviewed has been an asshole in one way or another, and not a fit for my team.

jameskraus 2y ago
Meta, like many big tech companies, has some fantastic engineers, some lousy ones, and some in between. At this point I don’t pay too much attention to where someone worked previously, and try to get to know candidates individually. They’re all just different people, like you and me!
- AlotOfReading 2y ago
  There are definitely things you should adjust depending on where a candidate is from. People tend to inherit things from the overall culture, particularly if it's been a major part of their career. It's better not to ask an Apple employee what they worked on in any detail, or an Amazon employee why they're leaving, for example. Helps avoid potentially uncomfortable situations on both sides and increase the signal/noise ratio.
anon84873628 2y ago
So what else are you prejudiced about?
- oefnak 2y ago
  People who worked for cigarette companies.
  - _DeadFred_ 2y ago
    Or DraftKings/gambling sites. Basically those that exploit addiction for profit.
- op00to 2y ago
  Job hoppers. Cisco management - truly horrible people. We see a lot of applicants from Red Hat who “drank the kool aid” there for way too long.
muglug 2y ago
Not in my experience. I've helped hire/onboard a couple of really great former Meta engineers, and currently collaborate with a bunch of great engineers at Meta.
jedberg 2y ago
Generally a bad practice to automatically say no based on a single entry on a resume, no matter what that entry is. If Meta was their first and only job, maybe you could justify that view. But for example, I've had a few exceptional coworkers from Netflix go to Meta. In part because they got to work on exactly what they wanted with nearly unlimited resources, and in part because they got paid fat bank to do it. Doesn't make them bad people. Would gladly work with them again at any time.
- linotype 2y ago
  Working for a company that knowingly harms children (especially young women and girls) to get paid “fat bank” is up there on my list of reasons to say they’re bad people. https://www.cbsnews.com/amp/news/facebook-instagram-dangerous-content-60-minutes-2022-12-11/ https://www.cbsnews.com/amp/news/facebook-instagram-dangerou...
  - jedberg 2y ago
    I'm going to assume that the people I'm talking to are the ones who are against that and trying to fix it. At this point in my life, I've seen enough people desperate for work that I'm not going to fault someone for working for an "evil" company. Maybe they really needed that money. Maybe they really needed that insurance for a loved one. I really don't know their situation and I'm not going to judge them just for that. If, after talking to them, they talk about how excited they were abound working on code that helped exploit addiction in young girls, then I'll reject them. But if they were just there because they really wanted to work on react.js, I'm going to fault them for that.
    - op00to 2y ago
      Just because someone needs a job doesn’t mean I need to blow up my well meshed team consisting of sane, non-assholes with some twat whose head is 100x the size it should be. They can work for oracle or something. We tried meta folks before. Every other sentence was “at Meta…” what works at Meta does not work everywhere else. Plenty of other places for them to work. I am not responsible for their well-being.

by op00to 2y ago

I go so far as to immediately say no to any candidates who have Meta in their history. Every meta person I’ve interviewed has been an asshole in one way or another, and not a fit for my team.

jameskraus 2y ago

Meta, like many big tech companies, has some fantastic engineers, some lousy ones, and some in between. At this point I don’t pay too much attention to where someone worked previously, and try to get to know candidates individually. They’re all just different people, like you and me!

AlotOfReading 2y ago
There are definitely things you should adjust depending on where a candidate is from. People tend to inherit things from the overall culture, particularly if it's been a major part of their career. It's better not to ask an Apple employee what they worked on in any detail, or an Amazon employee why they're leaving, for example. Helps avoid potentially uncomfortable situations on both sides and increase the signal/noise ratio.

anon84873628 2y ago

So what else are you prejudiced about?

oefnak 2y ago
People who worked for cigarette companies.
- _DeadFred_ 2y ago
  Or DraftKings/gambling sites. Basically those that exploit addiction for profit.
op00to 2y ago
Job hoppers. Cisco management - truly horrible people. We see a lot of applicants from Red Hat who “drank the kool aid” there for way too long.

muglug 2y ago

Not in my experience. I've helped hire/onboard a couple of really great former Meta engineers, and currently collaborate with a bunch of great engineers at Meta.

jedberg 2y ago

Generally a bad practice to automatically say no based on a single entry on a resume, no matter what that entry is. If Meta was their first and only job, maybe you could justify that view. But for example, I've had a few exceptional coworkers from Netflix go to Meta. In part because they got to work on exactly what they wanted with nearly unlimited resources, and in part because they got paid fat bank to do it. Doesn't make them bad people. Would gladly work with them again at any time.

linotype 2y ago
Working for a company that knowingly harms children (especially young women and girls) to get paid “fat bank” is up there on my list of reasons to say they’re bad people. https://www.cbsnews.com/amp/news/facebook-instagram-dangerous-content-60-minutes-2022-12-11/ https://www.cbsnews.com/amp/news/facebook-instagram-dangerou...
- jedberg 2y ago
  I'm going to assume that the people I'm talking to are the ones who are against that and trying to fix it. At this point in my life, I've seen enough people desperate for work that I'm not going to fault someone for working for an "evil" company. Maybe they really needed that money. Maybe they really needed that insurance for a loved one. I really don't know their situation and I'm not going to judge them just for that. If, after talking to them, they talk about how excited they were abound working on code that helped exploit addiction in young girls, then I'll reject them. But if they were just there because they really wanted to work on react.js, I'm going to fault them for that.
  - op00to 2y ago
    Just because someone needs a job doesn’t mean I need to blow up my well meshed team consisting of sane, non-assholes with some twat whose head is 100x the size it should be. They can work for oracle or something. We tried meta folks before. Every other sentence was “at Meta…” what works at Meta does not work everywhere else. Plenty of other places for them to work. I am not responsible for their well-being.