Coaching a senior technical contributor into a VP role
The situation
The client was a senior technical contributor, one of the people an organization keeps close because the problems nobody else can close end up on that desk, and the position they had arrived at is the one that particular kind of strength tends to produce: consulted constantly, promoted rarely, and no nearer to running anything than they had been several years earlier.
What they wanted was not the next rung. It was a step change into an executive seat, and into a different field from the one the technical career had been built inside, which is a materially harder thing to ask a hiring committee for, because the evidence a technical contributor accumulates is evidence of technical judgment, while an executive hire is an argument about a different kind of judgment altogether, decided by people who will not do the translating on the candidate’s behalf.
Sivad ran the engagement for them as executive coaching, résumé review, and interview preparation, scoped to that gap and nothing wider.
Why a technical record does not read as an executive one
A technical record answers one question well, which is whether this person can solve the problem in front of them. An executive hire asks something else — whether this person can decide which problems are worth solving, put people against them, and carry the consequence when the call turns out to be wrong — and the evidence for that is not produced by doing excellent technical work, so it does not appear on its own in a document written the way technical résumés are written, as an inventory of systems touched and tools known.
The gap widens when the target role sits in another field, because the reader on the other side of the table has no shortcuts available: the employers mean nothing to them, the programs cannot be ranked, the acronyms do not read as credentials, and what is left is whatever the candidate can say plainly about scope carried, decisions owned, and what followed from them.
The common response is to add material — more history, more detail, more proof of the technical depth that was never the obstacle — which makes the document longer and the argument weaker. The work is subtraction and translation, and it is uncomfortable, because a good deal of what gets cut is the part the candidate is proudest of.
What we did
1. Separated the record from the résumé. Sivad’s consultants went through the client’s working history line by line and sorted it by what each item demonstrated rather than by what it had been called, which is how scope, budget ownership, authority exercised across functions, and decisions made under real consequence get pulled out of jobs whose titles never mentioned any of them.
2. Rebuilt the résumé as an argument rather than an inventory. Every entry rewritten to state the situation, the decision, and what followed, in terms a reader outside the field can weigh without a translator, with the technical detail cut back to the level a general executive audience can still credit and the length held down deliberately.
3. Coached the change of field until it stopped being a defense. Worked through how the move would be explained to someone entitled to be skeptical of it — why leave a position of acknowledged technical strength, why this field, why this person rather than an insider who already knows the industry — until the answer was the most convincing passage in the conversation rather than the part being survived.
4. Ran interview preparation as rehearsal under pressure. Mock interviews with the hard questions asked in the form they actually arrive in, including the ones about titles, gaps, and the absence of industry experience, with feedback given immediately and bluntly, on the principle that mistakes are best spent somewhere they cost nothing.
5. Prepared for the executive conversation specifically. An interview for a VP seat tests different things than a technical interview does — what the person would do first, how they would handle a team they inherited rather than built, what they would stop doing and who they would tell — and each of those had a considered answer ready rather than an improvised one.
How it ran
The three pieces ran as one engagement rather than three services bought separately, because the résumé, the interview, and the account a candidate gives of their own career are the same argument written for three audiences, and a version that is strong in one place and weak in another fails at whichever gate it is weakest.
Coaching came first and stayed open throughout, since the questions that surface while rewriting a work history are rarely questions about wording. The résumé was rebuilt once, properly, rather than tuned again for every new posting. Interview preparation ran against live openings, which is the only honest test of whether the argument holds when the person applying the pressure has other candidates in the pipeline.
The client moved into a VP role, in a field other than the one the technical career had been built in. That is the outcome, and the part of it worth reporting is that it did not stay a single good result for the client, because the argument they left the engagement holding was portable, which is what a career change looks like when the underlying case is sound rather than when one interview happens to go well.
If this is the position you are in
The pattern repeats. A senior technical contributor is valued precisely where they are, is not on the list for the roles they actually want, and has been told — often kindly, sometimes by people who mean it — that the next move is a matter of patience. It usually is not.
What is missing is an argument, stated in terms an executive audience can weigh, about scope carried and judgment exercised, and that argument does not assemble itself out of a technical work history without deliberate work. Where the target role also sits in a different field, the case has to be built explicitly rather than implied, because nobody on the far side of the table is going to build it on your behalf. It is the same diagnostic habit the firm applies to a supply chain, pointed at a career instead: establish what the record actually shows, sort it by what it proves, and put the strongest of it where the decision gets made.
What Sivad delivered
- —A record sorted by what it proves. We went through the client’s whole working history and reorganized it around demonstrated scope, ownership, and consequence rather than job titles, which is where the material for an executive case was already sitting, unlabeled.
- —A résumé written for the reader who decides. We rebuilt the document as a short, plain argument a general executive audience can evaluate without technical translation, and cut the material that only impressed people already inside the field.
- —An account of the change of field that holds up. We built and rehearsed the explanation for moving fields until it was the strongest passage in the interview rather than the one the candidate braced for.
- —Interview preparation run as rehearsal, not encouragement. We put the hard questions in the form they actually arrive in, gave the feedback immediately, and kept going until the answers were steady under pressure.
- —A transition that kept paying. The move landed the client a VP role in a different field, and because the case had been built rather than improvised, it went on working for them in the moves that followed.
If you are the strongest technical person in the room and still not on the list
A first conversation is scoped as a working session, so bring the résumé in whatever condition it is in, the kind of role you are actually after, and the part you already know is going to be hard to explain, and we will tell you what the case looks like from the other side of the table and whether it is worth building.