Who actually makes the design hiring decision?

A candidate can meet five people and still not know who will decide whether they get the job. The interviews may feel collaborative, but the final choice may belong to one manager. Or the candidate may focus on the hiring manager while a panel is expected to reach a collective decision.

Neither arrangement is inherently dishonest. The problem is leaving the arrangement unclear. In my writing about design hiring committees, I described the gap between a process that invites input and one that actually shares decision authority. That gap becomes frustrating when people believe they are participating in one system while the company is operating another.

Before scheduling interviews, decide who makes the choice, what other people contribute, and how disagreements will be resolved. Then explain it to candidates and interviewers in ordinary language.

Separate participation from authority

A team member can provide important evidence without holding a veto. A hiring manager can own the final decision while taking the team's assessment seriously. The process becomes confusing when those roles are implied rather than stated.

Write down which questions each interview is intended to answer. One person may assess interaction design, another may explore collaboration with engineering, and the hiring manager may evaluate the role's overall fit. Their observations can inform one decision without pretending that every participant has identical responsibility.

If the team does use a shared decision, explain what that means. Is consensus required? Does a particular concern prevent an offer? Who decides whether the evidence is sufficient? The word “committee” does not answer any of those questions by itself.

Choose a process the company can actually run

A small team may want broad participation because everyone will work closely with the new designer. A larger team may prefer clearly delegated authority. But company size alone does not determine the right model. Leadership habits, role responsibilities, and the people involved matter too.

I would avoid choosing a process simply because it sounds more thoughtful or more efficient. A consensus process that the company cannot sustain may drag on until someone overrides it informally. A manager-led process can fail if the manager ignores the people who understand the work most closely.

Choose the arrangement that reflects how decisions will really be made, then make it accountable. The written process should describe the actual practice, not an ideal version that disappears when someone senior has a strong preference.

Give each interview a distinct job

If every interviewer asks for the same portfolio presentation and then submits an overall feeling, a long process can produce surprisingly little new evidence. Candidates repeat themselves while the company mistakes repetition for depth.

Map each interview to a small number of questions from the hiring brief. Explain those questions to the interviewer and tell the candidate what kind of conversation to expect. A portfolio discussion can explore contribution and decisions; another conversation can examine working relationships and the environment the candidate needs.

Avoid making candidates guess which person cares about which hidden criterion. Transparency does not weaken an assessment. It gives people a fair opportunity to provide the evidence the company says it needs.

Collect observations before the group discussion

Ask interviewers to record their evidence independently before hearing the strongest voice in the room. This creates a clearer view of what each person actually observed and reduces the temptation to rewrite an assessment around a colleague's confidence.

The note should distinguish an observation from an interpretation. “The candidate could not explain who made the research decision” describes a gap in the conversation. “They are not strategic” is a broader conclusion that may or may not follow.

In the discussion, connect concerns back to the role. If the group disagrees, identify whether it is disagreeing about evidence, the importance of a requirement, or the level of uncertainty it can accept. Those are different problems and may need different resolutions.

Make the final decision legible

A manager who owns the choice should be able to explain how the interview evidence informed it. That does not mean every interviewer gets their preferred outcome. It means their contribution is acknowledged and the decision is connected to the stated needs of the job.

A group that decides together should leave with an explicit result and a named person responsible for communicating it. Shared authority should not mean nobody owns the next action. The candidate still needs a timely answer.

If more evidence is required, specify exactly what is missing and whether another step is proportionate. Adding an interview because the team feels uneasy can create work without resolving the uncertainty. Sometimes the right next step is clarifying the brief rather than asking the candidate to perform again.

Tell candidates what to expect

A clear explanation can be short: “The team will assess the work and collaboration, and the hiring manager makes the final decision after reviewing that feedback.” Or: “The panel decides together, and these are the requirements each person will assess.”

Candidates can also ask directly who makes the final choice and how feedback is incorporated. The purpose is not to find the one person to impress at everyone else's expense. It is to understand how the process works and prepare relevant evidence for each conversation.

That clarity helps the company as well. Interviewers know why they are involved. The decision-maker knows what they are accountable for. Candidates understand the steps ahead of them.

A hiring process does not become fair merely by adding people to it. It becomes more useful when participation, evidence, and responsibility are clear enough that everyone can describe the same process.