The first person I hired was a 23-year-old fresh graduate named Rani.

She had no marketing experience. She had no enterprise sales experience. She had no experience working for a foreign-headquartered technology company, which, in Jakarta at the time, was a vanishingly small category of employer. She had, in the language of every job description we had been sent from the regional headquarters, almost none of the requirements for the role we were hiring for.

She had, instead, two qualities that no job description had asked for. She listened better than anyone I had ever interviewed. And she closed.

I did not know she was going to be the best closer on the team when I hired her. I knew, in the way you sometimes know in a first conversation, that she was going to be the person who made the rest of the team better. I made her the first hire. She stayed for two years. She is, to this day, one of the most effective sales operators I have ever worked with.

The last person I hired in those first six months was a senior marketing director with twenty years of experience at multinationals. He quit in his second week.

I want to tell you about the difference between those two hires, because the difference is the lesson I have been trying to teach — and learn — in every leadership role since.

The Hiring Problem That Was Not in the Brief

The brief from the regional headquarters, when I took the role, was clear. Build the marketing function. Build the sales function. Hit the regional revenue target. The brief did not say: build a 25-person team from scratch, in two languages, in a market you do not know, in a category that does not yet exist, under a parent-company timezone that does not understand why Indonesian university students need to be approached differently from students in the home market.

The brief also did not say: the people you hire will be the only institutional memory the regional operation has. Every person you bring in will be a decision about what kind of company this is going to be. Every person you bring in will either reinforce the values you are trying to build or contradict them. There is no neutral hire. There is no hire that does not send a signal.

I had been a senior leader for less than a year. I had hired teams before, in larger organizations, where the institutional context was already established and the new hire was being inserted into an existing culture. I had never built a team from nothing. I had never been Employee #1.

I was, in the precise language of the situation, about to learn the difference between hiring and building.

The Difference Between Hiring and Building

Hiring is a transaction. The organization has a need. The candidate has a skill. The transaction matches the need to the skill. The onboarding is the integration. The performance review is the calibration. The promotion is the retention. The whole system is designed to be repeatable, scalable, and auditable.

Building is a relationship. The organization does not yet exist in any meaningful sense. The candidate is not being matched to a role; the candidate is being matched to a possibility. The onboarding is not the integration; the onboarding is the first draft of the culture. The performance review is not the calibration; the performance review is the first test of whether the values you said you had are the values you actually have.

In a hiring context, the question is: does this person have the skills we need?

In a building context, the question is: is this person going to make the team better, and is the team going to make this person better, in a way that produces something neither of us could produce alone?

I have come to believe that most leadership mistakes, in the first year of building a team, come from confusing the two questions. The leader asks the hiring question in a building context. The leader optimizes for the wrong signal. The leader builds a team of skilled individuals who do not, collectively, constitute an institution.

Rani was the building hire. The senior marketing director was the hiring hire.

What Rani Had

Rani did not have experience. She had three things that experience could not substitute for.

She had curiosity about the customer’s actual problem. In our first conversation, I asked her why she wanted to work in education marketing. She said, in Bahasa Indonesia, with the slight hesitation of someone who has been thinking about this for a long time: I want to understand why my friends cannot find jobs even though they have degrees, and I want to help fix that. It was not a polished answer. It was not a value proposition. It was a real answer, from a real person, about a real problem. I knew, in the way you sometimes know, that the answer was going to be the foundation of the work.

She had the discipline to learn what she did not know. Rani had never run an enterprise sales motion. She had never used a CRM. She had never facilitated a workshop with C-level executives. She learned all of these things in the first three months, with the quiet focus of someone who understands that the work is the teacher. I did not have to manage her. I had to clear obstacles out of her way.

She had the kind of emotional intelligence that turns a team into a community. Within two months, Rani knew the names of every team member’s parents, the cities they came from, the reasons they had joined, the parts of the work they loved and the parts they dreaded. She knew, in the precise language of organizational behavior, the human context of every professional interaction. By the end of the first year, she was the de facto culture carrier of the team. The values I had written on the wall were the values she enacted in the room.

Rani did not have the requirements in the brief. She had, instead, the foundations that no brief can specify.

What the Senior Marketing Director Did Not Have

The senior marketing director had everything in the brief. Twenty years of experience. P&L responsibility at three multinationals. A network of C-level contacts in Jakarta. A track record of building teams at scale. He had, in the language of the job description, every box ticked.

He quit in his second week. The reason he gave, in the exit conversation, was: I do not think this is the right fit.

The reason he did not give, in the conversation we had three months later over coffee, was different. He said: I came in expecting to be executing a strategy. I found that there was no strategy. There was a vision, and a whiteboard, and a 23-year-old closing deals I would have spent three months preparing for. I did not know how to be useful in that.

He was, in the precise language of organizational behavior, a hiring-context operator in a building-context environment. The brief was right. The context was wrong. The mismatch was not his fault. It was, in the precise language of the situation, a failure of the hiring process. I had asked the hiring question. I had not asked the building question.

The lesson, which I have been trying to teach myself since, is this: the building-context question is harder, slower, more expensive, and almost impossible to systematize. It is also the only question that produces teams that scale.

What I Now Look For

In the years since that first six months, I have built or helped build four more teams — at a Taiwanese technology multinational, at an Indonesian pre-Series A startup, at a Singapore-based higher education venture, and at a globally-ranked university’s regional joint program. I have hired somewhere between eighty and one hundred people in those teams. I have made every mistake in the leadership literature, and a few that are not yet in the literature.

The pattern I now look for, in a building-context hire, is the same pattern Rani had. It is a pattern of three signals.

The first signal is the answer to a question no one taught them to answer. When I ask a candidate why they want to do this work, I am not listening for a value proposition. I am listening for the texture of the answer. Is it a sentence they have rehearsed, or a sentence they have thought about for a long time? Is it about the company, or is it about the problem? Does the answer reveal a person who has been paying attention to their own life, or a person who has been optimizing their career?

The second signal is what they do with the parts of the work they have not done before. Building is, by definition, full of work that has not been done before. The candidate who is energized by the unknown is the candidate who is going to make the team better in the months that matter. The candidate who is threatened by the unknown is the candidate who is going to spend their energy building a facsimile of the role they had at their previous employer.

The third signal is how they treat the people around them in the interview. I have come to believe that the most reliable predictor of future team behavior is the behavior the candidate exhibits when they think no one is evaluating it. How do they treat the receptionist? How do they treat the person whose job they are being hired to lead? How do they treat the questions they do not know how to answer? The signals are small. They are also, in the precise language of building-context hiring, the only signals that matter.

The Lasting Difference

Rani is still in the industry. She is now a regional sales director at a different company. She has built teams of her own. She has, by every available measure, become the leader I hoped she would become.

The senior marketing director is also still in the industry. He is, by every available measure, doing the work he was always going to do. He is doing it well. He is doing it at organizations that are hiring-context environments, where the strategy is in place and the role is to execute it. He is, in the precise language of the situation, exactly where he should have been all along. The mismatch was not in his capability. It was in the question I had asked.

Twenty-five people in six months. Five years of learning compressed into half a year. The most important lesson was not how to hire. It was how to recognize that hiring and building are different verbs.

The first person taught me what to look for. The last person taught me what to look at.

I have been looking, in every team I have built since, for people like the first. I have been trying, with imperfect success, to be the kind of leader who can recognize the difference.