Hire the Wanderer: What Early-Stage Founders Get Wrong About the "Unfocused" Résumé
A founder who's only ever worked inside a single, stable career path has to be taught to expect the unexpected. Someone who's already lived through four unrelated industries collapsing, pivoting, or quietly changing the rules doesn't have to be taught that.
The candidate with one job and a straight line up sounds safer. The one with five jobs and no clean story is usually the one who's actually run into the problem you're about to hit.
Every founder eventually writes some version of the same job posting: looking for someone driven, adaptable, comfortable with ambiguity, who thrives in a fast-paced environment. Then the applications arrive, and the same founder quietly filters out anyone whose work history doesn't move in a straight line - because a résumé with six employers across four industries reads, at a glance, like a warning label instead of exactly the qualification the posting asked for.
That instinct deserves a second look, and the reason is structural, not sentimental.
A job description at an early-stage company is close to fiction. It gets written before the company knows what the role actually needs to be, and it's usually wrong within ninety days. The person hired as "operations lead" ends up doing customer support during a rough launch week, drafting the first version of a pricing page nobody else has time for, and sitting in on a sales call because the founder is stuck in traffic. Nothing in that sequence was in the job posting. All of it is normal. A company at ten people doesn't have departments. It has problems, and whoever's closest picks them up.
That reality quietly breaks the standard hiring filter. A tidy, single-industry resumé signals someone who has thrived inside defined roles, clear reporting lines, and processes built by people who came before them - genuinely valuable traits, at a company that already has those things. An early-stage company doesn't have those things yet. It needs someone whose comfort zone is the absence of a lane, not the presence of one.
There's a candidate worth picturing here: eight jobs by their early thirties, four industries, no obvious narrative thread. Hospitality, then logistics, then a stint in retail management, then something administrative that paid the bills while a longer-term plan sorted itself out. On paper, a hiring filter reads that as risk. In an interview, the more useful question is what that person actually watched happen eight separate times - how eight different operations handled a cash crunch, a bad hire, a customer who wouldn't be placated, a slow month that could tip into a very bad quarter. Someone who's stood inside that many operating environments has a working mental model of what breaks a small business, built from repetition most single-industry candidates never get access to. That's not baggage on a résumé. That's applied pattern-matching, acquired for free by someone else's payroll before this company ever met them.
This maps directly onto the three disciplines that consistently separate startups that make it from ones that don't: a real growth mindset rather than a defensive one, treating speed-of-learning as the actual job instead of a byproduct of it, and building honest best-case and worst-case scenarios instead of running on pure optimism. Those aren't abstract virtues. They're habits, and habits get built by repetition under pressure. A founder coming out of one long, stable career often has to be taught to expect the plan to fall apart, because their own experience never required that lesson. A candidate who's already watched four unrelated business plans get rewritten mid-year doesn't need the lesson. They need the founder to recognize that they've already learned it somewhere else, on somebody else's payroll, for free.
Worth separating from all of this: the commissioned hire versus the accumulated hire, because startups tend to only build a pipeline for the first one. Early revenue teams are usually built around quota-driven, commission-structured roles — recruit fast, train on a script, measure the close rate. That pipeline works well for building a sales floor. It does not surface the generalist a ten-person company actually needs in its second or third hire: someone who can move between functions without a script, because no script exists yet for what they're being asked to do. A founder who only knows how to hire through the commissioned funnel will keep finding confident, well-trained closers and keep missing the versatile operator who's never been the top of anyone's leaderboard because no leaderboard has ever measured what they're actually good at.
All of this gets at something the early-stage-startup literature already half-understands, even when it isn't phrased this way. The three disciplines that separate ventures that make it from ventures that don't - a genuine growth mindset, treating learning faster than the competition as the actual job rather than a side effect of it, and building real scenario plans instead of pure optimism - are, functionally, the exact instincts someone develops by surviving multiple industries instead of one. A founder who's only ever worked inside a single, stable career path has to be taught to expect the unexpected. Someone who's already lived through four unrelated industries collapsing, pivoting, or quietly changing the rules doesn't have to be taught that. They already know business plans are provisional. They just haven't had anyone tell them that instinct is hireable.
There's a compensation problem tangled up in this too, and it's worth naming directly instead of glossing over. The generalist hire is usually being asked to take a bet - an undefined role, a title that will change twice in the first year, equity instead of the security a specialist role at a bigger company would offer. That's a real ask, and it deserves a real answer instead of vague enthusiasm about "wearing many hats." What does the equity actually vest into? What does the role look like in month six if the company is still standing? Founders who can't answer those questions specifically are asking for the flexibility of an early-stage hire while offering none of the transparency that makes the trade worth taking.
What would change if the interview asked what each previous job required that the next one didn't, instead of asking why the candidate left? What's actually being screened for when a founder filters out anyone without a tidy narrative - competence, or just a story that's easy to summarize in one sentence during a partner meeting?
None of this is an argument for hiring chaos on principle, or treating every scattered resumé as secretly brilliant. Some candidates really did just drift, and a founder still has to make that distinction in the room. The test isn't tenure. It's whether the candidate can say, specifically and quickly, what each stop actually taught them and how it applies to the mess sitting on the table right now. That's a five-minute conversation. Most interviews never get there, because the resumé got filtered out by an applicant-tracking system before a human ever read it.
The practical fix is smaller than it sounds: write the posting around the problem that actually needs solving in the next ninety days instead of a fictional permanent job description, screen resumes for range instead of tenure, and replace at least one interview question with "walk me through the messiest thing you've had to figure out with no instructions." Founders who are honest about their own early hires will usually admit the best ones didn't look perfect on paper. They looked like someone willing to do a job that hadn't been defined yet, because they'd already done three jobs that weren't clearly defined either.
Building the actual hiring process around that reality - instead of defaulting to the resumé shape every other applicant-tracking system is already trained to prefer - is one of the quieter, higher-leverage decisions an early-stage company makes. That's part of the operational design work DSL Life exists to help think through.
