As an interviewer, when I rate the candidate that I just interviewed, I will take into account how good the candidate is at communication, but it wouldn't be a decisive factor. The decisive factor would be whether they solved the problem and wrote good-quality code.
If you have extra N hours to prepare for an engineering interview, I think spending them on practicing problem-solving and coding would be more efficient than practicing storytelling.
If you are already pretty good at interview problems, it might be valuable to invest a bit of time into communication. Doing a mock interview or two would be good way to do it.
If you have extra N hours to prepare for an engineering interview, I think spending them on practicing problem-solving and coding would be more efficient than practicing storytelling.
If you are already pretty good at interview problems, it might be valuable to invest a bit of time into communication. Doing a mock interview or two would be good way to do it.