Why Senior Pharmaceutical Hires Often Fail

The failure is almost never the person. It is almost always something that was decided weeks before anyone was interviewed, or in the months after they started.


Author: Karen Chapman | Life Sciences Search Partner, Executive Recruit Posted: 28 August 2026
Table Of Content

    A meaningful proportion of the searches we are asked to run in this sector are second attempts. Either the first appointment did not last, or the first process never produced one.

    That gives us an unusually clear view of what goes wrong, because we are frequently reading the post mortem before we start. The pattern repeats to a degree that is difficult to ignore.

    Independent research puts the senior hire failure rate somewhere between a third and a half, with the variation coming from how failure is defined and over what period it is measured. Leadership IQ, working from a sample of more than twenty thousand new hires, put the figure at forty six percent inside eighteen months and found fewer than one in five judged an unequivocal success. Work published by the Corporate Executive Board, now part of Gartner, has reported comparable numbers for externally hired senior leaders.

    The more useful finding sits underneath the headline. Technical capability is rarely the cause. The overwhelming majority of these failures are attributed to factors other than skill deficiency. People are not failing because they cannot do the work. They are failing because the role they were hired into was not the role that existed, because nobody tested the things that actually mattered, or because they were left to find their own way through an organization that had not prepared for them.

    In pharmaceuticals and life sciences the cost of getting this wrong runs higher than in most sectors. A failed leadership hire in a regulated business is not only a replacement cost. It is a delayed submission, a slipped launch date, an inspection handled by someone who has been in post for nine weeks. Warning letters from the Food and Drug Administration are public documents. Investors read them, competitors read them and partners read them, which is why boards increasingly treat quality and technical operations leaders as risk controls rather than as senior operational managers.

    What follows is organized around the three stages where these failures are actually created. Almost none of them are created in the interview, which is where hiring teams concentrate the overwhelming majority of their attention.

    STAGE ONE, BEFORE YOU GO TO MARKET

    Does the job title reflect the true content of the role, and where the organization is going

    Job titles in this sector carry a great deal of assumed meaning, and most of it is unexamined. Vice President of Regulatory Affairs describes a strategic function in one company and a submissions management function in another. Head of Quality means running a site in one business and holding named regulatory accountability across three in the next.

    The problem is not that titles vary. It is that a title sets a candidate’s expectations about scope, authority and reporting line before they have read a single line of the specification. If the title is inflated, the best candidates arrive expecting a seat they will not get. If it is understated, they never apply at all.

    The second half of the question matters more and gets asked less. A title should describe the role as it will need to be in three years, not as it is today. A company approaching its first commercial launch, or moving from a single site to several, or preparing for a transaction, is hiring someone who has to grow into a materially different job. If the title and the specification describe only the current state, the search will find someone who fits the business as it is and who will be out of their depth by the time it changes.

    Write the specification against where the business is going. Then check that the title matches it.

    Is the required scientific credibility and regulatory experience actually written down

    Most person specifications in this sector describe scientific credibility in terms so general that they cannot be assessed. Strong scientific background. Deep regulatory knowledge. Neither of those means anything at an interview panel, and neither can be evidenced by a candidate or tested by an interviewer.

    The question worth asking is what specifically this person will need to do that requires credibility, and in front of whom. Presenting to a regulator is a different capability from presenting to a scientific advisory board, which is different again from earning the confidence of a research group that will decide within a month whether it respects the new arrival.

    The same applies to regulatory experience. Experience with the Food and Drug Administration is not a single thing. Having supported submissions is different from having owned them. Having owned a submission in an established therapeutic area is different from having taken an advanced therapy through approval, and the pool of leaders who have done the latter is genuinely small. A specification that asks for regulatory experience without naming the modality, the phase and the level of ownership will produce a shortlist of people who all technically qualify and who are not remotely interchangeable.

    Name the specific experience. If the pool that has it is too small to be viable, that is a decision to take deliberately at the briefing stage, not something to discover at the third round.

    Does the role need someone from a specific sector, and have the trade offs been thought through

    The most common version of this question is whether the hire should come from a large pharmaceutical business or from a contract development and manufacturing organization. It is a real distinction and it produces genuinely different leaders.

    Someone from a large pharmaceutical business will typically bring depth, process discipline and experience of operating inside mature quality systems with substantial functional support around them. They are used to specialist teams, established governance and long planning horizons. Dropped into a smaller organization, some of them thrive and some spend a year looking for the support functions that do not exist.

    Someone from a contract development and manufacturing background typically brings breadth, client facing commercial awareness and comfort operating with less infrastructure. They tend to be faster and more pragmatic. Moving the other way, into a large organization, some find the governance load and the pace of decision making genuinely difficult.

    Neither profile is better. The failure comes from not deciding, or from deciding implicitly by defaulting to whichever background the last successful hire happened to have. Take the decision explicitly, write down what you are trading away, and brief the interview panel on what to probe. If you are hiring for breadth, do not then run a process that rewards depth.

    Does the role actually carry the authority it needs

    This is one of the most reliable predictors of failure and one of the least examined. A specification describes what the person is accountable for. It rarely describes what they can decide without asking, what budget they control, who reports to them and who they report to.

    The gap between accountability and authority is a particular problem in regulated environments, where certain functions are supposed to be able to say no. A quality leader who is accountable for release decisions but sits three levels below the person under commercial pressure to ship has been placed in a structurally impossible position. So has a regulatory leader expected to hold a submission timeline who is not in the room when the timeline is announced to investors.

    Capable people take these roles because the title and the accountability look right. They leave when they discover the authority is not there, and they usually leave quietly, describing it as a personal decision. The post mortem then records a hiring problem when what actually happened was an organizational design problem.

    Map the decision rights before the specification is written. If the authority does not match the accountability, fix that first, because no candidate will fix it for you.

    Is it clear who owns the decision

    Senior processes in this sector routinely involve a chief executive, a board member or two, the function head, a human resources lead and several peer stakeholders. That breadth of input is usually a good thing. The absence of a single decision owner is not.

    Where nobody owns the decision, two things happen. The process drifts, because no one person is accountable for concluding it. And the group converges on the least objectionable candidate rather than the strongest one, because consensus rewards the absence of reservations rather than the presence of conviction. The candidate who excites three people and worries two loses to the candidate nobody has an opinion about.

    Name the decision maker at the outset and tell everyone else what their input is for. Some panel members are there to assess, some to advise, some to be consulted so that they are invested in the outcome. Those are different jobs and confusing them is what produces a shortlist of compromises.

    STAGE TWO, DURING THE PROCESS

    Are there robust assessments, and will due diligence actually be done

    Most senior processes in this sector consist of a series of conversations. Conversations are good at establishing whether people find each other credible and articulate. They are poor at establishing how someone behaves under regulatory pressure, how they handle a disagreement with a scientific lead, or what they do when the data does not support the timeline the board has already announced.

    Build in something that produces evidence rather than impression. A structured case study drawn from a real situation the business has faced. A presentation to the people who will actually have to work with the person. Psychometric or leadership assessment where the stakes justify it. The specific instrument matters less than the principle, which is that at least one stage of the process should generate something you can compare between candidates rather than something you can only feel.

    Due diligence is the second half and it is the one more often skipped. Formal references confirm dates. They rarely surface anything else. In a regulated environment there are specific things worth establishing, including whether the candidate held named regulatory accountability during any period in which a site received significant findings, how any such situation was handled, and whether there are restrictive covenants or notice arrangements that will affect what they can do in their first six months.

    None of this is about distrust. It is about knowing what you are taking on before the offer goes out rather than afterward.

    Was the candidate told the truth about the situation

    Expectation mismatch is one of the most consistently cited causes of senior hire failure, and it is almost always created during the process rather than after it. A business with a difficult inspection history, a strained relationship between research and commercial, a board that has changed direction twice in two years, or a predecessor who left in circumstances nobody wants to discuss, will tend to present the role rather than the situation.

    The logic is understandable. Nobody wants to talk a strong candidate out of a job. But the candidate finds out in week three regardless, and the damage is worse then, because they now know the organization was not straight with them and they are making judgments about everything else they were told.

    Senior people are not deterred by difficulty. Many of them are attracted to it, since a business with obvious problems is a business where they can visibly make a difference. What they will not forgive is being surprised. Describe the situation honestly, including the parts that are unresolved, and treat any candidate who withdraws as a process working correctly rather than a candidate lost.

    How long is the process going to take, and who is holding it together

    A senior search in this sector already carries structural delay. Notice periods run long, restrictive covenants need checking and the strongest candidates are rarely looking. Added to that baseline, internal drift is what loses people. Three weeks between the second and third stage is enough for a passive candidate to conclude the role is not real.

    The failures this produces are not always visible as failures. The strongest candidate withdraws quietly and the process concludes with someone acceptable, which nobody records as a problem until eighteen months later.

    Agree the full timetable before going to market, including who is responsible for keeping it moving when the chief executive is traveling and the function head is preparing for an inspection. A process with a named owner and fixed dates is not just faster. It signals to candidates that the organization is serious, which is itself a factor in whether the best ones stay engaged.

    STAGE THREE, AFTER THE OFFER

    Is there a real onboarding plan for the first hundred days

    This is the point at which the largest number of otherwise sound hires come apart, and it is the cheapest to fix.

    A senior person joining a regulated business has to build credibility with a scientific or technical population that will form a view of them quickly, learn a quality system that is specific to the site, and establish working relationships with people who may have wanted the job themselves. Very few organizations plan for any of this. The new arrival is given a laptop, a calendar full of introductory meetings and a general expectation that they will work it out.

    A first hundred days plan does not need to be elaborate. It needs to state what the person is expected to have achieved by day thirty, day sixty and day one hundred, who they need to have built relationships with, what they should not attempt to change in the first quarter, and who is accountable for making sure it happens. That last point matters most. Onboarding that belongs to everyone belongs to nobody.

    Agree the plan before the offer is made, and share it with the final candidates. It tells them something about the organization that no amount of interviewing will, and it is one of the few things that materially improves an acceptance rate at no cost.

    Has the internal candidate been dealt with properly

    Most senior searches in this sector run alongside at least one internal candidate who believes, sometimes correctly, that they should have had the job. How that person is handled determines a great deal about whether the external hire succeeds.

    Handled badly, and the pattern is predictable. The internal candidate is told late, told vaguely, or told by someone other than the person who made the decision. They stay, because they have equity or a mortgage or nowhere obvious to go, and they become a quiet source of resistance that the new leader spends a year working around without ever being told it exists.

    Tell them early, tell them specifically why, and be honest about whether there is a route for them. If there is, put it in writing with a timeframe. If there is not, say so and help them, because a clean exit is far less damaging than a resentful stayer. Then brief the incoming hire on the situation before day one rather than letting them discover it.

    What happens at month twelve

    Two things routinely undo a hire that has gone well for a year, and neither sits inside anybody’s recruitment process.

    The first is the compensation structure. An offer built to win the candidate is not necessarily built to keep them. If the package front loads a sign on payment to buy out a forfeited bonus, and the long term element is thin or vests on a horizon the candidate does not believe in, then month twelve is when the arithmetic changes and the market becomes interesting again. Build the retention case into the offer, not just the acceptance case.

    The second is continuity of the person who hired them. A senior leader recruited by a chief executive who departs eight months later is now working for somebody who did not choose them, may have preferred a different profile and owns none of the original decision. This is not always avoidable, but it is worth knowing that a hire made during a period of leadership change carries additional risk that has nothing to do with the individual, and worth making sure the case for the appointment is documented somewhere other than in one person’s head.

    The common thread

    Almost every question above is answered before the interviews or after the start date. Very few are answered in the interview itself, which is where hiring teams concentrate almost all of their attention.

    That is why senior hires fail at the rate they do. The process is heavily weighted toward the stage that determines the least. Move the effort to the briefing, to the honesty of the process and to the first hundred days, and the interview stage becomes what it should have been all along, which is a way of choosing between candidates you have already established are capable of doing the job.

    Email: [email protected]

    Tel: 1-888-651-6155

    Author: Karen Chapman | Life Sciences Search Partner, Executive Recruit View all posts by Karen
    Karen Chapman

    Karen Chapman is a Search Partner at Executive Recruit and leads the Life Sciences practice. She partners with organizations across R&D and manufacturing to help them secure the leadership talent needed to drive scientific progress and operational excellence. Her experience in this sector brings a deep understanding of how critical strong, execution focused leaders are in bringing therapies, technologies, and complex manufacturing capabilities to life.

    Follow Karen:
    Share