There are numerous guides and articles on how to interview.  They all provide some great suggestions.  However, I rarely see an essential recommendation for technical interviews.  Some technical interviews require dry and detailed answers.  Nevertheless, you will make a better impression when you focus on stories instead of buzzwords.

We Solve Problems

The most important aspect of our skills is how they are used to solve problems.  While a series of buzzwords can be useful for a job search, that is not the best way to show your skills.  It is good to include those buzzwords in your answers to technical questions, but not sufficient.  Turn the simple responses about your skillset into stories about how you used them.

For example, when asked how much Java experience you have, do not leave the answer at a number of years.  Instead, talk about your most recent Java project.  You can keep it short, but make sure you let the listener know that you have used those skills. You might even talk about a group of projects you have done and how you used those skills to solve problems prevalent in the industry.

Application Is Better Than Coding

We are approaching the point where much of the code creation process can be done by automation or templates.  While there is still a demand for raw coding skills, those are becoming a commodity and not a path for a career.  The competition and compensation make it not worthwhile.  Therefore, avoid getting into a conversation about your skills.  Focus on how you apply that knowledge.  Think about it.  Do you ask an auto mechanic about how good they are with a wrench?  Why should we waste more than a passing mention of skills instead of how we apply them?

The Future Is Stories Instead of Buzzwords

We have seen a steady increase in lampooning the buzzword culture.  Dilbert cartoons made Scott Adams rich from this form of ridicule.  There is no reason for us to get sucked into that trap.  Likewise, people are starting to see that technical interviews are not as effective when they only focus on raw skills.  Softer questions about how you work with a team, communicate or approach problem-solving are becoming far more common.  Make it easy for the interviewer and try answering questions with stories instead of buzzwords to show your technical prowess.

Episode Challenge: Convert your resume summary into more of a story and less a dry list of skills.

Read more about advancing your career.

Rob Broadhead

Rob is a founder of, and frequent contributor to, Develpreneur. This includes the Building Better Developers podcast. He is also a lifetime learner as a developer, designer, and manager of software solutions. Rob is the founder of RB Consulting and has managed to author a book about his family experiences and a few about becoming a better developer. In his free time, he stays busy raising five children (although they have grown into adults). When he has a chance to breathe, he is on the ice playing hockey to relax or working on his ballroom dance skills.

Leave a Reply