How to Hire Your First Designer as a Non-Design Founder: A 5-Step Assignment-Based Process

Last updated: September 2026

Your first designer can either make your startup look and work like a real company, or turn every design request into a 47-message WhatsApp conversation ending with, “Can you make it pop?”

The problem is not that you cannot judge design.

The problem is that most founders judge the wrong things.

A beautiful portfolio does not automatically mean someone can understand your customers, challenge a weak brief, make sensible trade-offs, or work with an engineer when the deadline is tomorrow.

I’m Riten, founder of Fueler, a skills-first portfolio platform building the career infrastructure for 100 million creative professionals. Fueler connects talented individuals with companies through assignments, portfolios, and projects, not just resumes or CVs. Think of it as Dribbble/Behance for work samples combined with AngelList for hiring infrastructure.

In this guide, I’ll show you a five-step process for hiring your first designer without needing to become a design expert yourself. You’ll learn how to define the role, create a useful design assignment, evaluate the work, interview the candidate, and make the final decision.

The goal is simple: see how someone actually thinks before giving them responsibility for your product.

1. Define Exactly What Your First Designer Will Own

“Looking for a designer” is not a job description.

A startup might need someone to design its product interface, landing pages, brand identity, social media creatives, presentations, or all five before lunch.

That is why the first step is defining the actual problem you want this person to solve.

Start with the work, not the title. Professional design hiring guidance also recommends defining the brief, deliverables, decisions, collaborators, constraints, and handoff before getting too focused on titles or qualifications.

• Write down the three most important design problems: Do not begin with “We need a UI/UX designer.” Begin with problems such as “Our onboarding is confusing,” “Our website does not explain the product clearly,” or “Our visual identity is inconsistent.” This gives candidates something concrete to respond to and helps you distinguish product design needs from branding or marketing design needs.

• Decide whether you need a generalist or specialist: Your first design hire usually operates across several areas. You may need someone comfortable with product design, visual design, research, prototyping, and developer handoff. If your company already has strong design leadership, a specialist can make more sense. The right choice depends on the work your startup actually needs.

• Define what the designer will own independently: Write down which decisions belong to the designer and which remain with the founder, product manager, marketer, or engineer. This prevents the classic startup problem where everyone has an opinion about design but nobody actually owns the decision. Clear ownership also gives candidates a realistic picture of the role.

• Describe the expected outcome, not just the responsibilities: “Design screens” is an activity. “Make the onboarding experience easier for first-time users to understand” is an outcome. Your hiring process should focus on whether a candidate can connect design decisions to business and user problems. That connection becomes especially important when you have limited resources and every design decision has consequences.

• Create a simple hiring scorecard before interviewing: Choose four or five things you will evaluate, such as problem-solving, visual hierarchy, product thinking, communication, attention to detail, and response to feedback. Decide what good evidence looks like before meeting candidates. Otherwise, the person with the most impressive portfolio presentation may quietly become your favourite for reasons unrelated to the actual job.

2. Create a Design Assignment That Looks Like the Real Job

The assignment should not be a mysterious puzzle designed to make candidates suffer.

It should be a small window into the work they would actually do after joining.

The best assignment gives the candidate enough context to make decisions while leaving enough ambiguity to reveal how they think. Research from Nielsen Norman Group also notes that design challenges can become stressful when candidates feel pressured to solve an enormous problem, so expectations around time, output, and discussion should be clear.

• Choose a real but contained business problem: Give candidates a problem that resembles the work they would handle after joining. For example, ask them to improve one part of an onboarding experience rather than redesign your entire product. A contained assignment gives you useful evidence without asking someone to donate an entire weekend to your hiring process.

• Give enough context to encourage real thinking: Explain who the users are, what the product does, what problem exists, and what constraints matter. You do not need to provide every answer. In fact, leaving reasonable questions open can be useful because you can observe what the candidate asks before starting the design work.

• Ask candidates to explain their reasoning: Do not only request the final screens. Ask them to briefly explain the problem, assumptions, decisions, alternatives, and trade-offs they considered. This turns the assignment from a beauty contest into an evaluation of design thinking. A polished interface is useful; understanding why it exists is much more revealing.

• Keep the time requirement reasonable: If the task should take two hours, say two hours. Do not secretly expect eight hours of work. Candidates should not need to build your next product for free just to prove they can design it. Clear boundaries also make submissions easier to compare because candidates are working within roughly the same constraints.

• Tell candidates exactly how you will evaluate the work: Explain that you will look at problem understanding, design decisions, usability, visual hierarchy, communication, and ability to discuss trade-offs. This makes the process more transparent. It also signals something important about your company: you care about how people think, not just whether the final screen looks impressive.

3. Evaluate the Assignment Without Trying to Become a Designer

This is where many non-design founders get nervous.

You look at two submissions. One looks beautiful. The other looks simpler. Suddenly you are wondering whether you need to spend six months studying typography before making a hiring decision.

You don't.

You need to evaluate evidence. AIGA guidance similarly emphasizes reviewing work through the brief, decisions, contributions, constraints, collaborators, and handoff rather than treating visual polish as the entire evaluation.

• Start by asking whether the candidate understood the problem: Before judging colours, spacing, or typography, return to the original brief. Did the candidate solve the problem you gave them? A visually attractive solution that misunderstands the customer or business objective is still a weak solution. Problem comprehension should come before aesthetic preference during a design assignment review.

• Look for decisions rather than decoration: Ask why the candidate chose a particular layout, flow, hierarchy, or interaction. Strong designers can usually explain the reasoning behind important decisions. You are not looking for complicated design vocabulary. You are looking for a clear chain of thought connecting the user problem, constraints, design decision, and expected outcome.

• Pay attention to what the candidate did not design: Restraint is part of good product thinking. If the assignment asks for a focused onboarding improvement and the candidate redesigns twelve unrelated screens, that tells you something. More work does not automatically mean better work. Look for evidence that the candidate understands scope, priorities, and the difference between solving a problem and decorating a product.

• Check whether the design could survive contact with reality: Ask what happens when the user makes a mistake, has no data, enters too much information, or returns later. Ask how the design would be handed to an engineer. These questions reveal whether the candidate thinks beyond the ideal screenshot. Real products contain edge cases, limitations, deadlines, and engineers who occasionally say, “That will take three weeks.”

• Ask the candidate to critique their own submission: One of the strongest questions you can ask is, “What would you change if you had another day?” Their answer can reveal self-awareness, prioritisation, and understanding of weaknesses. A candidate who thinks their first version is perfect may be harder to work with than someone who can clearly identify what still needs improvement.

4. Turn the Portfolio Interview Into a Conversation About Decisions

A portfolio should help you understand previous work.

It should not become a 40-minute slideshow where someone clicks through screens while everyone politely says, “Nice.”

Ask the candidate to explain the story behind selected projects. Nielsen Norman Group research on UX hiring highlights the value of understanding a designer's process, reasoning, research, collaboration, failures, and connection between design work and business problems.

• Ask what the original problem was: Choose one portfolio project and ask the candidate to explain the situation before the design existed. What was broken? Who experienced the problem? What information did they have? This immediately moves the conversation away from visual presentation and toward product thinking. It also helps you understand whether the candidate actually understands the work shown.

• Ask what they personally contributed: Team projects can be misleading when ownership is unclear. Ask directly, “Which parts did you design?” and “What decisions were yours?” A strong designer should be comfortable separating their contribution from the team's contribution. This is especially important when hiring from agencies, large companies, or collaborative product teams.

• Ask about something that went wrong: Try questions such as, “What did you get wrong initially?” or “What changed after feedback?” You are not trying to catch the candidate out. You are looking for evidence that they can revise their thinking. Design is rarely a straight line from brief to final screen. Someone who understands that will usually be easier to work with.

• Ask how they handle disagreement: Your first designer will probably disagree with you at some point. That is healthy. Ask about a time when a founder, product manager, engineer, or customer disagreed with their design. Listen for how they handled the disagreement, what evidence they used, and whether they could change their mind without becoming defensive.

• Ask them to explain one project to a non-designer: This is an underrated test. Tell them to explain a design decision as if they were explaining it to you on your first day working with designers. Great communication is not about using words like “affordance” every twelve seconds. It is about making complicated decisions understandable to people outside the design function.

5. Make the Final Hiring Decision Based on Working Fit

By this point, you should have three pieces of evidence: the candidate's previous work, their assignment, and the conversation around both.

Now ask the most important question: Can this person solve our actual problems with us?

You are not looking for the person who produces the prettiest screen. You are looking for someone whose judgment, working style, communication, and level of ownership match the role you defined at the beginning.

• Compare the candidate against the role, not against your personal taste: Founders naturally have aesthetic preferences. Maybe you love minimal interfaces. Maybe you hate rounded buttons. Neither preference tells you whether someone will perform well. Return to your scorecard and compare candidates against the problems, responsibilities, and capabilities the role actually requires.

• Look for evidence of independent thinking: Your first designer may not have another designer sitting beside them every morning. They need to be able to take an unclear problem, ask useful questions, explore options, and move a project forward. During the assignment and interview, look for moments where the candidate created clarity rather than waiting for someone else to provide it.

• Evaluate collaboration as seriously as design skill: A designer who produces excellent work but cannot work with founders, engineers, marketers, or customers can create expensive friction. Building a dedicated design team becomes easier when you hire people who combine strong design skills with clear communication, cross-functional collaboration, and a shared understanding of your startup's goals. Ask how they communicate feedback, handle constraints, explain decisions, and respond when their preferred solution cannot be shipped. Product design is collaborative work, not a solo art project.

• Check whether their strengths match your startup stage: A designer who thrives inside a large design organisation may not enjoy being the only designer at a five-person startup. Likewise, a startup generalist may not be the right choice for a company that needs deep expertise in one narrow area. Match the person's preferred working environment with what your company can realistically provide.

• Make the decision using evidence you already collected: Do not suddenly add a new criterion because one candidate feels more impressive during the final conversation. Review the portfolio, assignment, interview answers, communication, and references if you use them. Then ask one final question: “Would I trust this person with the design problem I described at the beginning?” If the evidence says yes, you have a decision.

How does this connect to Building a Strong Career or Portfolio?

Good hiring is increasingly about making someone's actual ability visible. For designers, that means showing the problem behind the work, the decisions made, the constraints faced, and the outcome produced rather than displaying polished screens alone. A strong portfolio becomes much more useful when it documents real thinking and execution. Platforms such as Fueler are built around this broader proof-of-work approach, where projects and assignments can demonstrate capability beyond a resume.

Final Thoughts

Hiring your first designer does not require you to become a design expert.

It requires you to become better at asking questions about the work.

Define the problem clearly, give candidates a realistic assignment, evaluate their reasoning, discuss their previous decisions, and compare the evidence against the role.

The right designer should not simply make your startup look better.

They should help you make better decisions about what you are building.

Frequently Asked Questions About Hiring Your First Designer

How should a non-design founder evaluate a designer?

Start with problem-solving rather than visual taste. Review whether the candidate understands the brief, explains design decisions clearly, considers users and constraints, responds well to feedback, and can collaborate with non-designers. The assignment and portfolio should provide evidence for these areas.

What should I include in a design hiring assignment?

Include a realistic business problem, user context, relevant constraints, expected deliverables, approximate time limit, and evaluation criteria. Keep the assignment focused enough to complete within a reasonable period. Ask candidates to explain their decisions instead of requesting only polished final designs.

Should I hire a generalist as my first designer?

It depends on your needs. If your first designer will work across product, branding, marketing, research, prototyping, and handoff, broad capability can be useful. If your company already has design coverage elsewhere, a specialist may make more sense.

How important is a designer's portfolio when hiring?

A portfolio is useful because it provides evidence of previous work and thinking, but it should not be the only evaluation method. A strong review looks at the candidate's role, decisions, process, constraints, collaboration, and outcomes rather than judging only the final visual presentation.

What is the biggest mistake founders make when hiring their first designer?

A common mistake is hiring based primarily on visual taste. Founders see an attractive portfolio and assume the designer will automatically understand their product. A better process tests problem-solving, communication, ownership, collaboration, and decision-making through relevant work.

Why 100,000+ professionals use Fueler

Fueler helps professionals showcase proof of work through projects, assignments, case studies, and achievements.

• Thousands of professionals use Fueler to create their digital portfolio

• Thousands of projects are published on Fueler. Check here

• Startups and Companies hire through proof of work on Fueler

• Used by freelancers, creators, marketers, video editors, writers, designers, and product managers

Our mission is to help the next 100 million professionals build a verified professional identity through proof of work