Stop hiring for availability; hire for fit

The designer you want may already have a job they like. That changes the hiring problem. You are asking someone to consider a move, understand an unfamiliar company, and take a risk with their time and career. A vacancy and a start date do not explain why that move would make sense.

I wrote about this because founders often describe their ideal candidate as someone excellent who is ready to start immediately. Those things can coincide. But availability is a timing fact, not a measure of ability, and being employed is not proof of quality either. I would rather start with the work the company needs and then build a realistic search around it.

Define the job before the start date

Before I think about names, I want to know what this person must make possible. Does the company need to understand why customers abandon onboarding? Does it need a coherent product experience across a growing team? Is the founder still making every interface decision because nobody else has the context?

Those are different jobs. They may all appear under the title “Product Designer,” but the evidence I would look for changes with the problem. Someone who can operate inside a mature design organization may need support that an early team cannot offer. Someone comfortable creating structure from ambiguity may find a tightly scoped execution role frustrating.

Write down the first meaningful outcome, the decisions the designer will own, and the people they will work with. Then ask which parts of the brief are essential and which are preferences. This gives you a way to assess someone who can start next week and someone who needs a longer transition using the same standard.

Understand the situation you are inviting someone to leave

A designer's current role comes with things your offer may not show: trusted colleagues, a manager who supports them, knowledge of the product, and a schedule that fits their life. Changing jobs can mean giving up all of those at once.

That does not mean the offer has to be extravagant. It means the conversation needs to be specific. What would the designer get to own? Why is the problem interesting? What resources will be available? What does the founder understand about design, and what are they willing to learn?

I would ask what a person wants more of in their next role, and what they want to avoid repeating. Listen before pitching. A candidate who wants deeper craft mentorship is unlikely to be persuaded by the chance to become the only designer in a team that has never hired one. Calling that role an opportunity does not remove the mismatch.

Make uncertainty visible

Founders sometimes feel they need to sell certainty. I think an honest account of uncertainty is more useful. An early company may still be finding its market. A team may be rebuilding its product. A design function may have unclear boundaries with product management.

Describe those conditions and explain how the company handles them. Who resolves a disagreement? How are priorities chosen? What happens when a proposed solution requires more engineering time than expected? These answers help a candidate judge whether the risk is acceptable.

You should also be clear about compensation, working arrangements, and the interview process early enough for them to matter. A compelling product problem cannot compensate for a practical constraint the candidate cannot change. Discovering that constraint in the final round wastes everyone's effort.

Build relationships without turning every conversation into a pitch

The useful relationship often begins before either side needs a transaction. You can notice someone's work, have a thoughtful conversation about a decision they made, and learn what kind of problem interests them without pretending an offer is imminent.

This takes patience. It also requires respecting a clear no. A designer who is happy where they are does not owe you continuing access to their attention. Keep in touch only where there is mutual interest, and make the contact worthwhile rather than repeatedly asking whether they are ready to move.

A simple record helps: what work interested you, what the person said they wanted, and whether they invited a future conversation. The value is the context. A spreadsheet of names without context is just another pile to sort when the hiring pressure returns.

Move promptly once there is a real match

Patience in relationship building should not become indecision during the hiring process. Once a candidate is interested, agree on the steps and keep them moving. Explain who they will meet, what each conversation assesses, and when they can expect a decision.

There is no universal two-week deadline that applies to every designer. Notice periods, other interviews, personal circumstances, and the complexity of the role all vary. Ask about those constraints directly instead of manufacturing urgency.

If you need immediate help, distinguish that temporary need from the permanent hire. A defined project with an independent designer may give the team time to make a better long-term decision. It should have its own scope, expectations, and agreement rather than quietly becoming an audition for employment.

Judge the match, then negotiate the timing

I would finish the assessment by returning to the brief. Can this person solve the problem? Can the team provide the conditions in which they will work well? Do both sides understand the responsibility and the trade-offs?

Only then does the start date become useful information for choosing among real options. An available designer can be an excellent hire. A designer who needs time can be the wrong one. The point is to keep timing from doing the work of judgment.

If your shortlist is defined mainly by who answered fastest, revisit the question. Decide whose work and way of working fit the company, then have a serious conversation about whether a move can work for both of you.