Company size is a weak predictor of role fit

Hiring discussions often treat startup experience and corporate experience as though they describe two coherent, irreducible categories of work. But they are not. A startup may still be searching for a reason to exist, or it may already have a validated product and a functioning system around it. A corporation may be mature as a whole while containing a new venture whose work remains largely pre-validation. Two companies of similar size may also differ radically in what they require from an executive.

This is why the familiar rules about transfer are unreliable. A large-company executive is not necessarily too corporate for the startup. A startup executive is not necessarily incapable of operating at scale. The movement from one organization to another has to be understood through the particular realities of the origin and destination. Three aspects are particularly worth paying attention to - validation, complexity, and taste.

Validation changes the meaning of the organization

A validated company has something sufficiently proven to organize around, it makes something the world has demonstrated that it wants. The company may misunderstand parts of its market, lose its position, or organize itself poorly but its central productive premise has still survived enough contact with reality to support a system. People, processes, capital, and information can be arranged around work that is known to produce something of value. A pre-validation company has no equivalent center. It still requires coordination. People have to decide what to do, how to divide work, and how to use money. It can have titles, reporting lines, processes, and plans, but these structures remain provisional because the object of the organization remains unsettled. When substantial organization is forced onto the company at this stage, there is a legitimate question about whether it is organization at all. The company may have built an orderly system around a hypothesis that reality has not accepted.

For a particular candidate being interviewed, the relevant validation state of a company in their past (or present) should be what it was at the time they were working there. A startup may cross into validation during someone’s tenure. A person inside a large corporation may work entirely within a pre-validation product or venture. The employer’s name and size themselves do not tell you if their work was pre- or post-validation. It is something the interviewer or the hiring manager has to determine, ideally through non-leading, open-ended questions.

Pre-validation experience has to be translated

Words used to describe things and work in a pre-validation environment do not necessarily mean what the same words mean in a post-validation environment. Strategy, operations, growth, scale, leadership, and results may all describe real activity. They describe activity taking place before the company has established what it can reliably produce, for whom, and through what system. But the meaning is not necessarily portable. Once a person’s experience has been identified as pre-validation, the need for interviewer questions aimed at translating language increases. The interviewer, through unapologetic follow-ups, should ask for higher-fidelity descriptions of the situation, the uncertainty within it, what the person did, and what followed. Without these deeper follow-ups, the interviewer and candidate may use the same words while referring to different realities.

Properly translated descriptions of pre-validation work usually reveal some mixture of two tendencies. One person functioned well because the absence of settled organization gave them room to act personally and fluidly. Another found traces of validation and built some legitimate organization around it themselves. Neither tendency can be valued without reference to the destination. A person whose effectiveness depended on fluidity may struggle in an organization with a settled productive system and a developed taste. That same person may be useful in a new venture or disruptive part of the company where the answer is still unknown. It is important to build some basis of understanding which tendency the interviewee is closer to, during the hiring process.

Complexity of past roles must be actively investigated

Once a company is post-validation, it can be viewed as a system. Complexity then becomes one of the main differences between organizational environments. Complexity may come from size, geography, technical demands, interdependence, or the sheer number of variables that must be integrated, with several of these sources often acting together. The complexity of the company the person was at is less important than the complexity that the person could personally handle. A large company may absorb much of its complexity through staff, systems, routines, and narrow role boundaries. Because of that, an executive can occupy a senior role in a complicated corporation while integrating only a defined part of it. A smaller company may ask one person to hold together a wider, less structured field. The company’s total complexity cannot be credited to everyone who worked inside it. The interviewer has to investigate to understand what piece of the organization’s complexity (or the whole) can be attributed to the person being interviewed.

Once you understand that, you are faced with three possible scenarios - the complexity of your role is similar, higher, or lower than what the person managed before. If it is higher, you have to believe that the person possessed additional processing capacity that the former environment did not require. Someone who was already stretched by the lower-complexity role is unlikely to manage a significant increase in variables. Their prior success proves that they handled what they faced but it does not reveal how far above those demands their ceiling might have been.

On the other hand, movement from higher complexity to lower complexity usually presents less risk of overload, provided the person genuinely was able to manage the complexity of the former environment. But if they weren’t able to manage and, as a result, “failed” in the former role, they may still have what it takes to manage the complexity of your role. That said, the fact that the new environment is easier does not establish that it is easy enough. The effectiveness of your read on whether or not they can handle the complexity of your role hinges on how accurately you understand the complexity of their past and the interviewee’s ceiling.

Industry and functional expertise can mask issues with capability

Relevant industry or functional expertise gives a person an assist at work. Industry familiarity allows them to recognize recurring patterns, anticipate consequences, and compress information that would otherwise require more active processing. Functional experience may offer a similar benefit, although less reliably. Exceptional motivation and work ethic can also provide such an assist by allowing someone to apply more sustained attention and effort, this increasing the amount of information they collect and the time they have to process it. But these assists have limits. Expertise can give ready pattern recognition for situations that the person already understands but their ability to generalize can still be lower than it needs to be. Motivation can push someone further than they are immediately capable, but it alone cannot indefinitely solve a gap between the number of variables a person can physically manage and the number the role requires.

Expertise can lead a person to oversimplify a situation, sometimes from necessity. When the environment’s complexity exceeds what the person can manage, they may rely more aggressively on what they know and cling to their playbook. What appears to be seasoned conviction may be a response to being overwhelmed. The opposite can be true too in that a person can over-complicate a situation, to make it similar to the higher complexity they are used to. Someone coming from a more complex environment may have ample capacity for the destination and still import processes, systems, and operating machinery that the company does not need. Their capability has transferred but it has not been calibrated. They solve for complexity that existed in the previous organization and create some of it in the new one. Perhaps the most critically important intuition to develop in hiring is the ability to not take industry or functional expertise at face value and instead deconstruct it into details that are specific to the person and their professional past.

Taste determines how much capability is applied

If complexity addresses what the interviewee can technically manage, taste affects how much of that capability they will apply effectively. Every organization has a way of doing things, thinking about things, viewing the world, and expressing itself. This “taste” is not often the same as the company’s stated values or culture. A company may be able to describe itself accurately, but that degree of awareness is usually uncommon. The company’s actual taste appears in what it permits, admires, distrusts, and finds embarrassing. It establishes boundaries around how serious people are expected to behave and what kinds of motivation belong within it. Taste often begins with the founding of the company - a strong founder can give a young organization a great deal of taste very quickly. Time develops and distributes the founder’s taste. In a newer company, each person’s individual personality can still enter the mixture more freely. In an older organization, taste has accumulated through years of decisions, relationships, rewards, and exclusions. It becomes less negotiable even when nobody can explain it clearly.

A person entering another company will almost certainly encounter a different taste to what they previously experienced. It is important to understand whether the destination’s taste will offend the person, motivate them, or produce some mixture of the two. Serious offense can dilute the person’s applied capability. The person may possess the judgment, knowledge, and processing capacity required by the role while becoming unwilling or unable to bring all of it into the work. A motivating taste can draw more from them and lead them to stretch themselves. Most people will find parts of an organization attractive and other parts distasteful. The hiring process has to identify whether any point of offense is fatal: whether it will produce withdrawal, contempt, or an inability to be an engaged part of the company. This question runs in both directions of course. The organization can also be offended by the person’s taste. Their natural way of working, expressing judgment, or treating authority may fall outside what the company experiences as permissible. A person can remain motivated by the organization while the organization gradually rejects the person.

An organization reveals its taste at the edges

Taste is difficult to assess because people inside a company experience it as normal. They may notice another organization’s peculiarities immediately while remaining largely blind to their own. Stated values cannot solve this problem because they are unlikely to be accurate, and ordinary interviews often allow both sides to present controlled versions of themselves. The best available test is to place the person in conditions that resemble the ones in which they will have to work, and see how they align with the taste of the organization. This does not always have to mean that the person is physically made to visit an office but an office-centered company should allow the candidate to encounter the physical nature of the environment. A seasonal business, such as a tax or retail company, should incorporate something of how the company behaves during its peak periods into the interviewing environment.

These edges matter because, at the edge, the organization has less time there to think about how it is presenting itself. It needs to act and so its natural pace, standards, relationships, and assumptions, i.e., its taste, become more visible. Capability should be tested, as far as possible, inside a real or simulated version of those conditions. Doing this gives the hiring manager a better chance of seeing whether the person’s capability actually translates to the company’s environment. Watching a candidate in a well-simulated situation will give an experienced member of the company an intuitive reaction about their fit. That intuition can be trusted if there is confidence in the simulation’s setup.

Transferability has to be judged person by person

There is no canned answer to whether people can move successfully between smaller and bigger companies. Validation, complexity, and taste create separate transfer risks, and company size does not reliably reveal any of them. Good hiring judgment builds a clear account of the organizational reality the person came from and compares it with the one they are entering. Pre-validation experience requires more translation. Differences in complexity require an estimate of what the person personally managed and whether they had anything left. Differences in taste require a realistic encounter between the candidate and the organization. Each part of the process replaces a general assumption about background with a more specific judgment about the person.

Some uncertainty will remain in any hiring process so this is more about smart diligence than endless diligence. The process needs to ask enough follow-up questions, reject enough unsupported abstractions, and create a realistic enough test for an experienced hiring manager’s intuition to become useful. The decision can then be made with a clearer view of which parts of the person are likely to transfer and where the transfer may break down.