Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I think there can be good stories that capture interest, however you should use some sort of method to first test the waters whether this sort of story would be interesting to the other party.

Reading the blog post, the story about tripping due to bad shoes to me would be a turn off to hear. Because are they going to tell this story from out of nowhere?

If they started off with "I had a crazy scare today, I almost slipped and fell walking high up.", I might appreciate it more since I can choose myself then to ask whether I want to hear more details about the story.

Otherwise the story just takes up too much time and it's not polite to interrupt them. It's a risky investment of time that the other party might not appreciate or care for.

Of course it depends on the personality of the person who you are telling the story to. Some people definitely may appreciate the detailed visuals etc, but to me when someone ends up with a long winded answer, I tend to think "man, they could've just summed all of this information up with one sentence".



I took the story as simply an example of the difference between an interesting vs uninteresting anecdote. I think it's implicit in the article that the story you choose to tell is relevant to the interview situation you're in.


Yes, however still to me people sometimes will talk too much, when it would be much better where they are concise at first and I can ask immediate interactive follow ups about the details. Interview is such a limited time so to me it seems most efficient to have a dialogue out of the box.

Or they should at least make pauses to give opportunity for cuts.

I don't want to listen to prose someone studied word by word.

I don't need to "feel" the challenge as the author said. I need to be able to figure out during 1 hour the problem solving capability of the candidate. If they spend unnecessarily much time on stories, I would be concerned whether they are a bser and want to limit my ability to ask questions as the time runs out.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: