Three career pivots can be evidence of judgment when each move shows how a candidate reads constraints, learns a new market and makes decisions with incomplete information. For a founder hiring into an uncertain product, the transitions may matter more than a perfectly linear résumé.
At 10:17 on a Tuesday morning, I was interviewing Kofi, an invented composite of several senior candidates I have encountered while building products across Ghana, Germany and the US. He sat in a quiet room in Accra with a chipped blue mug beside his laptop and called the three changes on his résumé “the obvious liabilities.”
He had moved from consumer goods into telecommunications, then into software operations, then into an AI product team. Now he wanted a role where the roadmap could change after two customer calls.
Our company had enough runway for one senior hire. Choose poorly, and the person would spend months waiting for stable requirements we could not provide. The product could miss its window while we paid for experience designed for a different kind of company.
The answer hidden inside each transition
I asked Kofi why he had left telecommunications.
He did not say he wanted a new challenge. He described a launch where the commercial team wanted wider distribution while the product still failed under conditions common outside the main cities. He had argued for a narrower release, lost the argument and spent the following weeks dealing with consequences he had predicted but could not prevent.
His next move into software operations gave him more control over the connection between product decisions and customer outcomes. It also exposed a gap. He could diagnose failures after release, but he could not yet shape what the team built before release.
That gap led him into product.
The sequence changed when he explained it. Three pivots on paper looked like restlessness. In conversation, each transition followed an unresolved problem from the previous role.
The important evidence was not that every move had worked. One had cost him seniority. Another put him in a smaller company with less support and a manager who left before his first quarter ended. He stayed long enough to learn what he had gone there to learn, then made another call.
A stable résumé can conceal an unstable fit
Founders often treat continuity as proof of reliability because uncertainty already surrounds the role. The customer may change direction. The AI model may perform well in a demo and fail on the missing page the buyer cares about. Runway may force a hiring decision before the product has settled.
A familiar career path feels like one variable we can control.
But the safest-looking candidate can still require stable budgets, clear reporting lines and decisions that remain decided. Those are reasonable expectations. They are also conditions an early-stage company may be unable to offer.
I have learned to separate continuity from adaptability. Years in one function show depth. They do not automatically show how someone responds when the function itself changes.
A pivot gives me a specific decision to examine. What did the candidate see? What options were available? What did they give up? What happened after the move? What would they do differently now?
This is the same distinction I make when assessing product judgment. A polished AI demonstration tells me less than the team’s response when a customer asks about an edge case the script avoided. That question sits at the centre of what Ama’s identity question taught the team about risk.
Test the reasoning, not the résumé shape
Back in the interview, I gave Kofi the decision waiting inside the role.
A prospective customer wanted an automation feature tied to a valuable contract. Building it would pull the team away from the roadmap. Refusing could cost the deal. The evidence that other customers needed the feature was weak.
Kofi did not choose immediately. He asked what manual process the feature would replace, whether the contract depended on the full build, and what we could learn before committing engineering time. Then he proposed a limited manual test with a clear point at which we would stop.
His answer did not prove he would succeed. Interviews cannot do that. It showed how he reduced uncertainty without pretending it had disappeared.
I returned to each career change and used the same test. He could name the constraint, the trade-off and the evidence available at the time. He could also point to one decision he would reverse.
That last part mattered. Candidates who turn every pivot into a triumph leave me with very little to trust. Real decisions create residue: a relationship strained, a skill discovered late, a cost that looked smaller before it arrived.
Make the next interview about one live decision
When a senior candidate has changed fields, I no longer begin with, “Why so many moves?” That wording asks them to defend the shape of their career.
I choose one transition and reconstruct the decision instead.
What had become impossible in the old role? Which option did they reject? What evidence turned preference into action? What did the move cost? Six months later, which assumption proved wrong?
By the end of Kofi’s Tuesday interview, his three pivots had become the strongest evidence in the room. They showed a person who had repeatedly entered unfamiliar territory, found the constraint that mattered and accepted a real cost to keep moving.
The hiring risk remained. So did the product risk. But I had a better question for the reference call on my calendar that afternoon: when the plan stopped matching reality, what did Kofi do next?
Comments
No comments yet.