In design team building, the first hire sets the tone for the organization’s culture from that point on. The stretch of handling every project solo is over, and the moment you post that first job listing, it’s hard to know what to actually screen for. The new person’s way of working quickly becomes the team’s default, which is exactly why this hire shouldn’t be rushed.
1. How to Define What the First Hire Needs
Screen for craft skill alone, and most applicants already clear some baseline. The real differentiator shows up in how someone collaborates and their working style. Someone who’s comfortable deciding things alone versus someone who enjoys seeking other opinions and syncing up will shape the team in completely different ways.
This principle matters more for a first hire precisely because there’s no one to compare against yet. The second or third hire can be judged against how well they’ll mesh with the existing team, but the first hire is the sole benchmark for how well someone’s working style fits a founder’s. Whatever working style gets set here becomes the implicit norm for everyone who joins afterward.
The working habits built during a studio’s early days make finding someone who fits matter more, in the long run, than screening for skill alone.
Craft skill
Most applicants already clear a baseline level, so it rarely differentiates.
Collaboration style
Deciding alone versus syncing with others shapes the team in very different ways.
2. The Most Skilled Person Isn’t the Right Answer
A common mistake in a first hire is assuming the best move is picking whoever has the flashiest portfolio. But what an early team actually needs isn’t necessarily the most senior talent — it’s someone who can judge priorities and act independently, even in an uncertain environment. Early-stage studios are often short on operating manuals and defined processes, so someone who only moves when given explicit direction ends up becoming a burden on the organization instead.
The opposite extreme is risky too: someone who insists on working entirely independently. Early teams need to adjust direction constantly, so a person who checks in and confirms before locking in their own judgment ends up being the more stable partner.
3. Look Past the Portfolio, Into the Interview
Asking about the judgment behind the work matters more in an interview than the portfolio images themselves. The principle that a portfolio should surface process and reasoning, not just outcomes, applies just as much from the interviewer’s chair.
Asking specifically why a particular direction was chosen, what the alternatives were, and how disagreements got resolved during collaboration makes it much easier to predict how someone will actually behave on the job.
💡 Pro tip — Asking specifically “why did you choose this direction” and “what were the alternatives” in an interview surfaces the practical judgment a portfolio image alone never shows.
4. The First Three Months of Onboarding
Hiring is the start, not the finish. What role the new designer plays on which project during those first few weeks heavily shapes whether they stick around long-term. Hand them tasks that are too small and they never feel a sense of growth; drop them straight into a major project and they carry the weight of the job before they’ve learned how the team actually works.
In the first few weeks, weight observation heavily so they absorb how the team works
Gradually increase the weight of delegated responsibility, widening their scope step by step
Hold regular, short feedback sessions to check in on how they’re settling in
The First Design Hire Checklist
Did you prepare questions to assess collaboration style, not just craft skill?
Did you ask specifically about the reasoning behind portfolio projects?
Did you map out an onboarding plan and scope of responsibility in advance?
Did you design a regular feedback cadence before the hire even started?
5. Your Own Role as Founder Changes Too
A first hire means adjusting a new person to the organization — but it’s also the process by which a founder shifts from doing the work to managing people who do it. Keep the same solo-decision habits you’ve always had, and the new designer never gets a chance to exercise their own judgment, and eventually settles into a passive posture of just waiting for instructions.
Delegation isn’t completed in one step. It’s safer to start by handing off small decisions, review the results together, and gradually widen what gets delegated. There’s no need to feel awkward about this shift — a practitioner and a manager are simply asked for different skills, and the transition takes time for anyone.
One common mistake is not being able to let go of the habit of touching every detail of the work yourself, even after becoming a manager. Rewrite a new designer’s output to match your own style every single time, and that person starts to feel their judgment is never going to be reflected, and gradually becomes more passive. As long as the overall direction of the output doesn’t stray far from the intended course, the team benefits more from treating small stylistic differences as part of someone’s growth.
Closing thoughts
Practical material on hiring and onboarding is also worth checking on Google re:Work. Keep in mind that the bar you set for your first hire becomes the bar for every hire after it, and approach it with care.
Design Daily Life · Notes on design, daily