Snippet
- Why fixed job descriptions and resume-to-JD matching fail once a role starts changing shape.
- A six-signal framework: adaptability, learning velocity, ambiguity tolerance, judgment, ownership, and role-shaping ability, each with a direct interview prompt and follow-up probes.
- How to structure the interview itself, including incomplete-information scenarios, trial projects, and what a candidate’s own questions reveal.
- A structured scorecard for separating durable capabilities from role-specific requirements.
- The hiring signals founders tend to overweight for undefined roles, and why they predict less than they seem to.
You write the job description knowing it’s already half wrong. Six months from now, the role will look nothing like the doc you posted, and you’re hiring someone today for a job that doesn’t fully exist yet. Most founders handle this by hiring for the JD anyway, then wonder why a strong resume turns into a mediocre hire once the scope shifts under them.
The fix isn’t a better job description. It’s evaluating for what stays valuable as the role changes, including adaptability, learning velocity, ambiguity tolerance, judgment, ownership, and the ability to help shape what the role becomes.
The real hiring question isn’t whether this person can do the job as you’ve defined it today. It’s whether this person can succeed as the job changes under them.
Why Standard Hiring Criteria Break Down for Evolving Roles
A fixed JD assumes a static job, so scoring against it is accurate on day one and stale by month three.
- False precision: Evaluating candidates against every listed responsibility rewards experience that may be irrelevant in six months.
- Resume matching favors the past: A candidate who held the exact title before may have less to offer than one who has repeatedly built new capabilities under changing conditions.
- Over-specified requirements shrink the pool: Founders screen out people who could grow into the role because they don’t already resemble its future version.
This matters more as AI reshapes job composition. The World Economic Forum’s Future of Jobs Report estimates that 39% of workers’ existing skill sets will be transformed or outdated between 2025 and 2030.
Separate LinkedIn research shows employers who prioritize skills over credentials see roughly 60% more successful hires. Both point the same way: hire for trajectory, not task-fit.
A Framework for Evaluating Candidates in an Evolving Role
This is where the hiring decision gets made. Six signals, each testing a distinct capability that survives a role changing shape, each with a prompt, a set of probes, and a way to tell a rehearsed answer from a real one. This is specifically crucial in early-stage startup hiring.
1. Adaptability
Adaptability shows up in how someone responds once the original plan stops working.
Look for a material change they’ve handled before, such as priorities, customers, resources, or direction shifting mid-stream.
“Tell me about a role where expectations changed significantly after you started. What did you do?”
Push past the headline answer with three follow-ups.
- What changed, specifically, and how did you find out?
- What did you stop doing, start doing, or change entirely?
- How did you decide that was the right response, and who did you check it with?
A strong answer gives you a sequence of decisions in order. A weak answer stays at the level of “I just adapted” or credits the outcome to the team without describing their own move. Hire an engineer who can adapt to the evolving startup environment.
2. Learning Velocity
An evolving role will eventually need a capability that didn’t exist in the JD when you hired for it. This tells you how fast someone closes that gap, not how much they already know.
Look for a time they had to become effective in an unfamiliar tool, domain, or technical area, and focus on how they learned it.
“Tell me about something you had to get good at quickly because your role changed.”
Probe the mechanics of how they learned it.
- What did you try to understand first, and why that first?
- Where did you go for information when you got stuck?
- How did you check whether your understanding was correct?
- How long until you could operate without help?
A strong answer has a method you could repeat. A weak answer describes the outcome (“I figured it out”) with no visible process behind it.
Confused about what your perfect JD should say? Here’s an efficient JD builder to overcome this bottleneck.
3. Ambiguity Tolerance
This tests whether someone can make progress when the problem, process, or ownership isn’t defined yet.
Give them an incomplete situation and watch whether they separate what needs clarifying from what they can just move on.
“If you joined and were handed a problem with no clear process or owner, what would you do first?”
Their first three moves tell you more than their final answer.
- Do they name a concrete first action, or do they stay abstract (“I’d figure out the lay of the land”)?
- Do they identify who to talk to and what to ask them?
- Do they form an assumption and say how they’d test it, rather than waiting for certainty?
A candidate who says “I’m comfortable with ambiguity” without a concrete first move hasn’t answered the question yet.
4. Judgment
An evolving role in a growth-stage startup generates decisions with no playbook behind them. Judgment is what lets someone move without constant direction, and it shows in how they explain a choice.
Ask them to walk through the reasoning behind a real decision.
| What to probe | What it reveals |
| What options did you consider? | Breadth of thinking |
| Why did you choose this one over the others? | Decision quality |
| What trade-off did you accept? | Commercial and practical judgment |
| What information were you missing at the time? | Comfort with imperfect information |
| What would have made you change the decision? | Ability to update on new evidence |
An engineer who can name the trade-off they accepted, and what could have gone wrong, is giving you a usable signal. A candidate who can only report that it worked out is giving you a story.
5. Ownership
Ownership matters most when the boundaries of the job are still moving, because someone will eventually run into an important problem with no name attached to it.
“Tell me about a problem you took ownership of that wasn’t formally your job.”
Follow the story past the moment they noticed the problem.
- What did they do in the first week after noticing it?
- Who did they pull in, and how did they get buy-in without formal authority?
- What structure or process did they put in place so the problem didn’t just depend on them personally?
- How did it resolve, not just how did they feel about it?
The signal is the ability to spot where ownership is missing and build just enough structure to move the problem forward without waiting to be assigned.
6. Role-Shaping Ability
The strongest hire for an emerging role doesn’t just adapt to it. They help you find out what it should become, which is a different skill than asking for more scope.
“Six months in, you find the company’s needs are different than expected. How would you decide what your role should focus on?”
Listen for whether they connect a proposed change to a business outcome.
- Can they name the problem a new responsibility would solve?
- Can they say how they’d know, concretely, that taking it on created value?
- Do they frame it as “here’s what I noticed and why it matters,” or as “here’s what I’d like to be doing instead”?
The first framing is role-shaping. The second is scope creep dressed up as initiative, and it’s worth telling the two apart before the role is six months old.
How to Interview for a Job That Doesn’t Exist Yet
Behavioral questions show how a candidate has handled ambiguity before. The interview format itself should test how they handle it live. Here’s how to assess if a candidate is startup-ready:
- Run an incomplete-information scenario: Give a realistic problem with deliberate gaps, similar to what they’d face in month one. It tests ambiguity tolerance, judgment, and problem-structuring at once.
- Use a take-home trial project where practical: It replaces self-reported behavior with observed behavior, and for a role with no fixed scope, it’s often the clearest signal available.
- Loop in stakeholders outside the hiring function: An evolving role will cross boundaries early, so a candidate who struggles to communicate across functions is a risk worth catching now.
What candidates ask is its own signal.
| Candidate behavior | What it indicates |
| Asks how success will be measured in 6 months | Outcome orientation |
| Clarifies the problem before proposing solutions | Problem framing |
| Asks what’s expected to stay flexible | Comfort with evolving scope |
| Needs the scope fully fixed before engaging | Weak ambiguity tolerance |
Turn These Criteria Into a Practical Candidate Scorecard
Score each signal only against a concrete example, never a general impression, and set 2 to 3 role-specific must-haves separately.
| Signal | Strong score requires | Weight |
| Adaptability | Specific example of adjusting after a real change | High |
| Learning Velocity | Evidence of getting effective fast in unfamiliar territory | Medium |
| Ambiguity Tolerance | A concrete first move with no defined process | Medium |
| Judgment | Named trade-offs and reasoning, not just outcomes | High |
| Ownership | Unassigned problem taken to resolution | Medium |
| Role-Shaping Ability | Justifies new scope with value, not just asks for it | Medium |
Weights shift by role. A founding product hire leans on judgment and ambiguity tolerance; an emerging functional lead leans on ownership and role-shaping. Keep must-haves short: a scorecard with ten of them usually means the JD needs work before the interview does.
Check out this quick founders’ vetting checklist for better understanding.
What Founders Should Not Overweight When Hiring for Undefined Roles
- Exact title match: A past title describes someone else’s structure, not how they’ll perform in yours.
- Resume-to-JD alignment: A tight match shows past fit, not capacity for the next version of the role.
- Years of experience alone: Ten years in a narrow scope can score lower than two years of varied, increasingly complex work.
- Interview confidence: A polished answer isn’t evidence of sound judgment.
- Claimed adaptability: “I’m comfortable with change” is a statement. A specific example is evidence.
- A JD that’s really three roles stitched together: This is a scoping problem, not an evolving role, and it’s worth fixing before you interview against it. Write a JD that gets your right and startup-ready candidates, with clear requirements and not a copied list of skills.
The Final Test: Will This Candidate Grow Into the Role’s Next Version?
The goal was never to find someone who performs an undefined job perfectly on day one. It’s someone who creates value while the job becomes clearer, and stays the right person for it once it does.
Before the offer, ask:
“If this role looks significantly different 12 months from now, will this person have grown into it, or will we have to redesign the role around their limitations?”
Today’s job description is the starting point. The candidate’s capacity to navigate and shape change should drive the actual hiring decision.
