Connecting the Dots


This past weekend I read a fascinating article by Cognitive Scientist and Marketing researcher Hang-Yee Chan. In this article Dr. Chan, backed by brain-scans, supports the case that storytelling is one of the most effective ways to land your message.

More specifically, crafting a linear narrative triggers the consumer to a process called mentalizing, "which is the ability to decipher the thoughts, feelings, and intentions of others. It's what makes human beings social, allowing them to interact and coordinate based on subtle cues. Mentalizing is also key to story comprehension."

I come from a long line of great story-tellers (it's one of the things that pushed me to pivot from writing code to Product Management) but it also had me thinking about a lot of the advice I give around crafting a solid resume.

First - I think it's worth reiterating: my own views on resumes have evolved over the years. I don't think resumes carry the same weight in the job-application process as they once did. Online applications, LinkedIn Profiles, and a candidate's digital footprint fill gaps that a static resume could never fill. But resumes are not obsolete.

Resumes are for the job seeker, not the hiring manager. They're cheat-sheets/1 pager/executive summaries that help keep the job seeker focused, on-message and on-brand. If you've had your resume reviewed by me in the last 3 years, you've most likely had me ask you: "What's the narrative?"

Ever since I landed on the concept of a "career narrative" (in brief: gone are the days of the long linear careers at 1 employer, and we are now firmly in the world of multiple roles, titles, industries, companies; If you think of a connect-the-dots, each role are the dots - a career narrative are the lines, connecting the dots, to form the picture) it made me reevaluate and reframe how I pitch my own talents.

It's why I don't think pivoting a Director of Engineering, managing 30+ people and 5+ products to becoming an individual contributor as a Product Manager is much of a pivot. The same set of skills that made me successful in one role are guiding me in my next. The narrative is me, hi. (cue Taylor Swift, "it's me, hi, I'm the problem it's me.")

This is also why I value people who have made large career changes. They have outlier-dots. If you think about any good movie, book - they have narratives you may not predict. The break the mold and offer disruption. 

Connecting all this back to Dr. Chan's research, storytelling in your resume is important because, as Dr. Chan writes: "Communicators often package their messages in compelling tales for good reason. People's love for narratives seems hardwired in the brain."

Telling your own 'story' in a clear, concise, narrative that connects dots (no matter how divergent) in your resume will help you understand your own story. And, in understanding your own story, will help you better tell it. Clearly, concisely - but, most importantly, in a way that sticks. Just like any well-crafted 60 second ad campaign can.

Popular

Let's Clear Up The Ambiguity!

Image
Job seeking is hard - especially when you factor the ambiguity around expectations, the lack of transparency and consistency around process. It's frustrating dealing with the sheer subjectivity of everyone's opinions. Just think of even the basics: How long should your resume really be? Traditional black and white, or modern? Should you include a headshot? Oh - and cover letters - are those needed? Is anyone actually reading the cover letter? What are they looking for? Is there a bias for people with a more traditional background? Worst of all: The dreaded typo  that you catch only after applying to your dream job.  Are typos really going to cost you the opportunity??? To help bring some clarity to the process, I surveyed a bunch of hiring managers. The results were really interesting, and very illuminating.     If you're on the job hunt, I hope this information helps out! One final note: My recent post,  7 Steps to Writing an Amazing Resume , factors a lot of this feedba
Read more

FAQs for a Software Engineering Hiring Manager

Image
Technical Interviews have evolved a lot since the early I transitioned from being a Software Engineer to an Engineering Manager. Particularly in the post-Covid era, there's been a greater emphasis on the person, which I think is an important and welcome change. Over the decade of interviewing hundreds of coders, I've also had the pleasure of working with various bootcamps, colleges, and hundreds of individual job seekers on LinkedIn. Across all the changes over the past years, across the various locations and mediums, something remained consistent throughout: The questions I get asked.  With that in mind, I thought - why not make a FAQ from my perspective as a hiring manager? While this is my perspective, it's based off years of observation and supporting data. But that being said, advice is not fact. You may disagree with certain points, and that's OK. Opinions we disagree with allow us to better understand our own views. At best, I hope these responses help you
Read more

7 Steps to Writing an Amazing Resume

Image
  Since sharing my resume template  I've received plenty of feedback from job seekers, HR and hiring managers - all of whom value its purpose. Two (now former!) jobseekers even shared that as soon as they used my template, they were getting calls. Something about this template works, and given the traction it's getting others, I wanted to share - in more detail - why  this approach works so well.  Before continuing, let me give an important disclaimer: This resume isn't a miracle cure that's going to land anyone their dream job. Unless they're filled with lies, resumes are only as good as the candidate themselves. But they can also be a whole lot worse. This template and approach are all about maximizing the potential candidates have by highlighting and summarizing key areas.  Last point before beginning: If you don't know me, it's worth stating this advice comes from more than a decade of having hiring a broad range of coders: straight out of college, high
Read more

7 Steps to Building your Portfolio MVP

Image
Often when I suggest to coders that they build a portfolio, I'll hear back: "I don't need one..." "With all the effort it takes to apply, where will I find the time?" Simply put, having a portfolio's never going to hurt your chances at landing a job - it can only help. That second question is where a lot of struggle - because applying to jobs can be time consuming. Especially if you're wrapping up a bootcamp, or having to manually type in your resume info after uploading your resume. That's why I made these 7 steps which, when done correctly, can really help you stand out with a hiring manager. And, the best part is, it should only take you 2 days. Being the Agile-Obsessive that I am, it's all about maximizing value while minimizing effort. Fix links to your Resume, GitHub, LinkedIn, etc. at the top where they're always accessible. Link to everything here - and then remove all other links on your Resume except your Portfolio link . It sa
Read more

Work Experience vs Professional Experience

Image
In reviewing a bunch of resumes this week, I noticed quite a lot of resumes with a  "Work Experience"  section. In each of those resumes, people had de-valuing some very valuable  experience - and I write that with no exaggeration. The problem is people were looking at their experience purely through the "Job Title/Relevancy" lens and had reduced their experience down to a list of discrete, random, disconnected jobs. No interconnectedness, no narrative thread weaving through it all. As much as you may feel some jobs have no way of being connected, the reality is  you   are always the connection . To not connect them on your resume is to lose all that growth, knowledge, skills, impact, value, and trajectory. In other words - you lose the " You " in the resume. I recommended they start with a small change. Reword "Work Experience" to "Professional Experience" because, ultimately, every single job they had was in service of building their
Read more