> I never experienced an interview where somebody wanted to do something else than assess my technical skills.

I don’t understand why interviews in the software I industry are so different compared to other industries. I also get the impression that during many interviews what you’re about and what you’ve done matters very little. All that matters is if you can solve two Leetcode hards in an hour multiple times.

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".

Maybe at the beginning. But later they will definitely want to hear more about what was accomplished on past projects, and that lends itself to the story.

You lost an opportunity...

https://aphyr.com/posts/341-hexing-the-technical-interview

It probably depends on the company, the 'tier' of companies or your level. After reaching 'staff', the bulk of time spent in interviews is on the behavioral side, which is literally storytelling. Even interviewers tasked with evaluating technical competencies reserved 10-15 minutes at the end to ask 'loaded' TMAAT questions - 'Tell me about a time when you wanted to quit on the spot', 'Tell me about a time when you were publicly humiliated' - and the likes.

>I never experienced an interview where somebody wanted to do something else than assess my technical skills.

That's such an outlier I struggle to believe it. Nobody has ever asked you about your work history? Never about a time when you needed to work in a team to solve a problem, etc.?

According to the article, had you spun an interesting enough yarn full of half truths, you might've been able to skip all that stuff as you lulled your audience into a false sense of security.

Well yeah of course. Even the article didn't think story telling is appropriate for technical interviews; its the behavior ones you tell stories in.

you are 100% right

Nobody cares about anything except that coding question that is given during the interview

Even if you have an impressive portfolio of dev related work - the only thing you are judged on is that leetcode task during the interview

maybe at the vp/em level - where the job is talking it might be more appropriate