Hacker News new | past | comments | ask | show | jobs | submit login

I also keep recommending this book to everyone. The TL;DR is: NEVER ask questions about hypotheticals. Ask people about what they do, how much they pay, how much time it takes, and so on. Facts, not answers to "Would you use this if...?"



Interestingly enough, that’s also a principle of behavioral interviewing. Hypothetical questions allow the bullshitters to shine, but specific targeted lines of question about what the interviewee did in a specific situation is frequently enlightening.


For a technical sales job, I would have people do a role play about suggesting a technology. They’d always start saying “I would tell them about...” and I’d pause and ask them to tell me the thing, not talk about telling me.

My point is that I believe hypotheticals take a lot pressure off and allow you to be super vague in interviews. For the past, talk about real situations. For the present, do a role play.


Indeed! One of the things I found frustrating about the article is that he talks about people 'lying' constantly... when if fact he had just asked meaningless questions.


He used the word lying. They didn't know they were lying.

They were miswanting. And it's a HUGE glossed over fact when talking to customers.


Yes, it's the customer development version of the XY problem.

https://en.wikipedia.org/wiki/XY_problem




Registration is open for Startup School 2019. Classes start July 22nd.

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

Search: