Hacker News new | ask | show | jobs
by anotheryou 2612 days ago
I think I do a good job, but coming up with a nice story is difficult.

Success stories are short: you intervened early, spoke to the parties involved, made a plan everyone could agree on and moved on.

The interesting stories often only have OK-ish endings: You are facing extreme issues that are not under your direct control and you somehow keep things working (bad hires, dis-functioning external teams, legacy code falling apart from all ends, bad higher management).

And than there are non-issues you tackled early enough. E.g.: Newly established workflows and documentation between departments, getting you a compliment once and there might be less conflicts and pressure now, but it's hard to quantify.

Maybe good questions would be (answers I'd like to hear in brackets):

How and when do you...

- criticize (reviewing work, in a constructive manner)

- praise (frequent and honest praise, but no participation trophies)

- get involved in a grudge between team members (pro-actively, in private)

- escalate to higher ups (as a last resort and for serious violations)

- talk to individuals about work related, but not directly task-related things (one on ones, actively checking on those you don't communicate with often)

- encourage autonomy (take risks, keep pushing, give feedback)

- Do you approach different people in different ways? If so, make 1-2 examples. (adjusted level of politeness and formality when communication with other cultures (I'm German, we really have to change gears depending on who's on the other line), adjust how much guidance is needed when giving tasks, don't be racist/sexist/etc.)

- And to include something less people focused: When and how do decide to get a 2nd opinion? (acknowledge when you are out of your depth, do research, learn and ask others)

1 comments

I think it's just absurd to believe you can get to know someone within 60 - 90 minutes. A good liar/imposter can fool people for years. That's why you always ask for references and cross check stories.
On the other hand a bad gut feeling proves to be right often too. And I'm relatively sure it's not just confirmation bias :)
What we call gut feeling is often a subconscious interpretation of the person’s body language, physical appearance and tone of voice. It’s always good to try to explicit why you had that feeling before basing your decision on it.

I often think that shy people are assholes at first. Now that I’m aware of that I try to test the shyness hypothesis first when I have that feeling.

So exploit it, it’s something humans developed for good reasons. Just be aware of the biais and use it as a good starting point for a behavioral interview.

I'm totally with you here. One should not try to get rid of these quick form of prejudices, because they exist anyways and they might be useful.

To make them less "dangerous" it's good to be aware of them and stay doubtful about them to give anyone a chance to proof you better.

Reminds me of how I handed my phone to a couple once and wasn't sure if they'd scam me, but I willingly took the risk of loosing my phone to be able to help people when they ask.

They where honestly quite sketchy... I still wonder if they maybe just spontaneously decided not to scam me because they felt I was prepared for it.