How To Explain A Career That Doesn't Add Up

JOB SEARCH STRATEGY WITH EARLY.

On paper, one of our members looks like three different people.

He spent 8+ years in HR at big tech, at Tesla and Amazon, and ran his own coaching practice on the side. Now he wants to do people work at a startup.

To me, that sounds like an exciting career. He’s explored his interests and applied his skills to multiple different roles.

But those career turns can short-circuit a hiring manager’s brain. They might not see range, they’ll see a puzzle to solve.

Hiring managers are laser focused on how you’ll fit neatly into the requirements of the given role, and a squiggly timeline could make them think “can this person do the job we need done?”

If you don’t answer that question for them, they’ll fill in the gaps for you, and sometimes in an unflattering way. Maybe you got bored. Maybe you couldn't hack the role.

I’m not saying you should hide the twists and turns in your path. You might have taken a career break and feel worried about sharing it (which I can assure you, you shouldn’t).

The fix is to tell the story yourself and take control of the narrative.

You might not be an obvious candidate on paper but you can stand out as a stronger choice, if you can demonstrate how your experience and choices could benefit their company.

Our member did exactly that, and I'll show you how it played out.

IN THIS ISSUE:

1. Get the offer in writing

2. Turn the hiring manager into your advocate

3. Make the ask, then go quiet

4. Don’t anchor to the benchmark

1. HE DIDN’T WAIT TO BE FOUND

Let’s call our guy H.

H is a part of the Early job-search accelerator, and we’ve anonymized him for the purpose of this newsletter. But the details are all there.

H’s search took ten months, and it was by no means a linear search.

He hit final rounds and got rejected, at one point after a full on-site. For most of that time he was doing everything right and still getting nowhere.

He made two big shifts in his strategy that changed his outcome. Both of them are uncomfortable things to face but necessary if you want results.

First, the groundwork.

H joined Early in February and started by wiping the slate clean and getting clear on what and who he was actually targeting. That clarity is what made everything after possible.

Before he could explain his path to anyone else, H had to be clear on it himself, why he left big tech, why the coaching chapter mattered, and why startups were next. You can't sell a story you haven't made sense of.

He was in Atlanta, where startup roles were unfortunately thin, so he widened his search to the whole country and got his wife on board for a move. If your market is small, the fastest fix is often to make your surface area bigger. If you can’t find fish in a pond, you’re going to try fishing in a different, maybe bigger pond.

He kept sharpening his resume and LinkedIn until they told his story clearly. Your profile is the one thing every hiring manager checks, so it's worth treating like the billboard it is.

Then came the first uncomfortable move. H went back to people he hadn't spoken to in years and pushed past the awkwardness of the cold reach-out.

This in when the wheels were set in motion. An old colleague referred him, and that got him the interview. We know that most startup roles get filled through network, so the outreach that you’re dreading is really the shortest path in.

The second move happened in the interview.

After his screens with the hiring manager, instead of a generic thank-you, H took a real problem that the manager had raised and built a doc to show how he’d solve it.

He didn’t want them to take his word for it, he wanted to show that he could do the job.

It worked. H landed the role of People Business Parter at a Series F unicorn startup with a 98% PitchBook IPO Success Probability, matching exactly what he wanted.

He got hired because he took control of his story, carried it to someone who could open a door, and proved he could do the work before they'd even asked.

The door doesn't open on its own.

So the rest of this issue is how you build a story worth carrying, starting with working out which turn you're actually explaining.

2. THE FOUR SITUATIONS WHERE THIS MATTERS MOST

A squiggly path usually comes down to one of four moves. Work out which one is yours, because each raises a different doubt you'll need to answer.

The first is coming back after running your own thing.

Whether it was for two years or a decade, people will want to know what happened and what you're chasing now.

The assumption will be that something went wrong. Whether that’s true or not, you’ll have learned hundreds of lessons during the experience. Use those to your advantage and explain how they play into your next step.

The second is switching functions, moving from something like operations into marketing.

Here you have to explain why the change makes sense and why you'll be effective on the other side of it.

Don’t try to hide behind reasons that sound legitimate or acceptable. Be honest about why you want this move, and why it’s right for both you and the business.

The third is going from big tech to a startup.

You need a clear reason for the move, and it had better not be that you're hoping to get paid more. They want to know you understand what you're walking into.

Startups are a very different beast from corporate, and for some people that challenge is the reason why. Show that not only are you up for it, but that it excites you more than spending another decade in the safety of big tech.

The fourth is jumping between stages, from an early startup to a later one or the reverse. Here you have to show how the experience you have actually carries over.

The trap here is assuming all startup experience is there. Building from nothing at a seed-stage company and scaling what already works at a Series C are different jobs, even if both say "startup" on your resume. Name the specific experiences that translate, and be honest about what's new to you.

Our member was making two of these moves at once. He was coming back from running his own coaching practice, and he was going from big tech into startups. That's the kind of path that needs a story wrapped around it, and that story has to do four things.

3. WHAT YOUR STORY ACTUALLY HAS TO ANSWER

Whatever turn you're explaining, your story has to answer four things:

1. The real reason you made the move.

2. Why your history is relevant to the role you're interviewing for.

3. Why you specifically will be effective in it, with evidence to back it up.

4. That you're genuinely excited about this company.

That last one matters, especially at a startup.

Founders are hiring people they'll be in the trenches with, and excitement about the work is a signal they're actively looking for.

The job isn't to give your life history, but you don't want a flat, purely logical explanation either. It should be a clear, confident line from where you were, through the turn, and into why this exact role is the obvious next step.

And tell it like you actually want it.

The one people fumble most often is the startup move. They lead with what the startup does for them, instead of what they bring to the table.

The reason can't be that the pay is better or the company sounds cool. Your answer has to show you understand the trade you're making, and that you're walking in with your eyes open.

One thing I've left out on purpose: how to actually structure the story itself.

I broke that whole framework down a couple of weeks ago, where you are now, the turns that got you here, and why this exact role is next. If you want the build, start there, then come back and put your pivot through it.

JOIN THE EARLY ACCELERATOR & LAND THE JOB YOU WANT

If your path has a few twists and turns in it and you're not sure how to frame them, that's a lot of what we do inside the Early Accelerator: getting clear on your story and getting it in front of the right people.

Here are some recent member wins:

• A finance operator left healthcare for fintech and landed a role as Head of Enablement at a Series B startup.

• After nine months of searching, a member landed the director role he'd wanted since before his layoff, and it came straight from cold outreach.

• Another member bounced back from a lay off and joined a pre-seed startup as its COO through connections she made in the community.

These come from the playbooks, mentorship, coaching, company research, and community we provide.

Learn more and apply today (click here).

Your challenge this week:

Take the turn in your path you're most worried about explaining, write it out and put it out there:

1. One line: the real reason you made the move.

2. Four sentences: where you were, the turn, why this role is the next step, and why you actually want it.

3. Now use it. Put that story into your LinkedIn About section, or send it to one person who could open a door, this week.

Doors won’t open unless you give them a good shove.

Let's go get you that job! 🏆

Kyle

Founder of Early

RESOURCES MENTIONED IN THIS ISSUE

• Your response to "tell me about yourself" sounds like everyone else's → https://beearly.beehiiv.com/p/standout-in-your-startup-interview-answer

P.S. Whenever you’re ready, here are the three more ways I can help you this week:

1. Apply to join the Early Accelerator - Get coached directly by me, surrounded by a community of hundreds of badass startup operators. This is everything I learned when landing my role as Uber employee 250 and transitioning post-layoff to a Series A with top VC investors. We give you everything you need to make your startup job search a success. Structure, accountability, strategies, investor-grade company data, target company lists, negotiation assistance, everything to help you win.

2. Download the Clarity Playbook (FREE) - the exact process I walk every Accelerator member through to lock in their Role, Impact, and Company before they ever write a post or send a resume.

3. Use the Proof of Work Finder (FREE) - finds the highest leverage Proof of Work you can create for a target startup, builds it with you, and pressure tests it so it doesn't read as generic.