6
Boogie
5y

I went to a job interview about 3 weeks ago. I got an email that I didn't pass, so I asked for a feedback. Their response was that I have required technical skills, but the reason I was not accepted was "your personality is incompatible with our team". I mean, WTF. How can you get my personality after one hour of me talking about code?

Comments
  • 1
    It's fairly easy to see if you're shy, outgoing, etc. (Anything that defines your personality)
  • 2
    Takes me 20 seconds to figure out if I wanna work with somebody I’m interviewing. Don’t whine. See where you might have gone wrong. The only person introspection is gonna benefit is you.
  • 0
    @grumpyoldaf How do you know?
  • 12
    @Boogie Your look, your posture, your computer, the way you're shaking hands, if you're prepared, where you look, how you're speaking, the words you're using, etc. Everything you're doing consciously and unconsciously tell a lot about yourself. You are not necessarily aware of those things but you "feel" them.
  • 1
  • 8
    It’s a blessing, you don’t want to work in a place like that that values “personality and feelings” over code.

    Things will never get done and they move slow. You want to work at a place that appreciates talent, not who’s friends with who
  • 1
    When I’m interviewing someone I know if I would want to work with them within 30secs... I continue asking questions which will either reassure my previous view or make it worse.

    I specifically wanna know how the person thinks ... that’s how I judge weather they will be good on the team or not
  • 3
    Some people (including me) have this way of writing in which they write something that is ambiguous for example as in this rant:
    "I got an email that I didn't pass,"

    This I may interpret as an email that was not "passed".
    [or]
    An email which said that the subject did not pass something.

    I somehow always do this. It's interesting. Anyway.
  • 0
    @Jilano But do you think that when you base your opinion on those observations - you could have issues with working next to me?
  • 10
    @champion01 If you think that dev is just sitting there and producing code, I have bad news for you. The 1980s are over, and they will not return.

    These days, you have to interface with PMs, testers, other devs, maybe even customers (especially for non-trivial troubleshooting).

    If you cannot operate in a team, you are unsuited for most of today's dev tasks. Hard but true.
  • 3
    @Fast-Nop your not wrong, your very right in fact. My point is that sometimes that good social intent like your example can perpetuate to something where it becomes less about the code and more about the social actions.

    Some dev teams I see spend more time sending memes and YouTube videos than they do talking about code
  • 1
  • 0
    In addition to be observed by experts during the interview (HR with a lot of experience or psychologist) your personality scores (e.g. FFI, standard questionnaire) can be calculated from your social media activities.
  • 2
    @champion01 a happy team is a productive team.

    Where they draw their happies from is usually up to them.

    You'll find the team that wastes the most time, is the team that also delivers the most, or in some cases doesn't deliver anything... there's always exceptions 🤷‍♂️
  • 2
    @lastNick Just another reason to avoid FB, Twitter, Instagram & Co.
  • 2
    @Boogie Insufficient data for a meaningful answer. I do have a general idea about how you are in general, but I'm missing some key element to fully "assess" you.

    @Fast-Nop Well said. So many people forget that no matter what, you have to deal with other human beings at work. Even if you're the greatest developer ever, you will not get the position over a less talented one that can work with others.
  • 2
    @Jilano There's even a "logical" point of view for that: genius lone wolfs just don't scale.
  • 1
    Single "can do it all alone" people are nothing any company should want. If you are not talking with your team the only judgment on your code is done by yourself. And without external feedback you might produce unmaintainable bullshit while thinking "damn I'm so great".
    And if you work alone on certain topics you are a bus factor, meaning if you get run over by a bus the business is fucked.
    So the only reasonable thing to do is build teams not single performers.
Add Comment