For most small businesses, a graphic designer is the person who makes everything look like it came from the same company. The Instagram post, the Facebook ad, the menu, the trade show banner, the sales deck and the email header should all share one set of colors, fonts and rules. When nobody owns that, each piece gets made in a rush by whoever is free, and the brand slowly drifts. A good designer for this kind of business is fast, organized and comfortable working inside a brand system rather than reinventing it each week. These graphic designer interview questions are built to find that person.
They are written for owners hiring their first designer, marketing leads who need steady production help, and multi-location groups that want every location's flyers and posts to match. The focus is marketing and brand graphic design. If you need someone to design app screens and user flows, that is a different job, covered on our product designers page.
Start with the portfolio, then the questions. Ask the candidate to walk you through two pieces from their portfolio and explain the brief, the constraints and what they changed after feedback. A portfolio shows taste; the walkthrough shows whether they can work with a real business.
Pick eight to ten questions across the four groups below. If you produce a lot of social and ad content, weight the second group. If you print menus, signs or packaging, spend more time on the third. Ask every finalist the same core set so you can compare them fairly, then close with the paid exercise using your own brand files.
Model answer: I'd collect everything the business has published recently and lay it out side by side so we can see what's consistent and what's drifted. Then I'd write a short working guide: logo versions and clear space, the color values for print and screen, type sizes for headings and body, photo style and a few do's and don'ts. I'd build templates for the pieces you make most often so the rules are baked in.
Strong vs weak: Strong candidates document what exists and build templates. Weak ones want to redesign the logo first.
Model answer: Rarely, and never quietly. If a seasonal campaign or a partner co-brand needs something different, I show the owner the standard version next to the exception and explain why. If an exception keeps coming up, the rule probably needs updating in the guide.
Strong vs weak: Look for respect for the system plus a process for change. Weak answers either never bend or bend whenever they feel like it.
Model answer: I ask what the one thing is that someone must read from across the room, usually the offer or the event date. That gets the most size and contrast. Then the supporting line, then the details like address and hours. I cut anything that doesn't help someone act, and I squint at the draft to check that the order of attention is right.
Strong vs weak: Strong answers start from the reader and the goal. Weak ones talk only about fonts and colors they like.
Model answer: I keep the color but change how it's used: as a background block with dark text, as an accent line, or in a darker shade for text. I show both versions and explain that people with low vision, or anyone reading on a phone in sunlight, may struggle with the original.
Strong vs weak: Strong candidates offer options that keep the owner's intent. Weak ones either ignore readability or just say no.
Model answer: I lock the parts that define the brand, like logo position, margins and type styles, and leave a few clearly marked areas for the image, headline and details. In Canva I use brand kits and locked elements; in Figma, components and styles. I test each template with a long headline and a short one before handing it over.
Strong vs weak: Strong answers mention testing edge cases. Weak ones make templates that only work with the sample text.
Model answer: A good answer names something specific, like a layout that was too crowded or type that was too small on mobile, and says what they learned. It shows they look at their work with a critical eye.
Strong vs weak: Strong candidates are honest and specific. Weak ones say they wouldn't change anything.
Model answer: I look for a consistent style: lighting, color temperature, how people are shown, and whether images are real customers, staff or stock. I'd rather use fewer images that fit than many that clash. Every stock image I use comes from a source the business has a license for, and I keep a note of where it came from.
Strong vs weak: Strong candidates mention style rules and licensing habits. Weak ones grab whatever looks nice from a search.
Model answer: I list each request with its deadline and where it's going, then confirm priorities with the owner or marketing lead in one message. Anything tied to a launch date or an ad going live goes first. Quick fixes get batched into one block so they don't break up longer design work. I post the plan where everyone can see it and update it when things change.
Strong vs weak: Strong candidates confirm priorities and batch small tasks. Weak ones work in the order emails arrive.
Model answer: It depends on the channels, but usually a square and a vertical version for feed posts, a full-screen vertical for stories and reels, and a landscape version for some ads or link previews. I design the main version first, then adapt the layout for each size rather than just stretching it, and I check that text stays out of areas the app covers with buttons.
Strong vs weak: Strong answers adapt layouts and know about safe zones. Weak ones resize one file and hope.
Model answer: An ad has a split second to stop someone who doesn't know us, so the hook, the product and the offer need to read instantly, and text has to stay short. An organic post can be more relaxed because followers already know the brand. For ads I usually make two or three variations so the marketing lead can test them.
Strong vs weak: Strong candidates think about the viewer and offer variations. Weak ones treat both the same.
Model answer: I mock it up as written so they can see the problem, then suggest a shorter version or move the details into the caption or landing page. I don't cut someone else's words without asking. Over time I share rough word limits for each format so copy arrives the right length.
Strong vs weak: Strong answers solve it together and prevent it next time. Weak ones shrink the font until it fits.
Model answer: I follow the business's folder structure if there is one. If not, I propose one: by year, campaign and format, with file names that include the date, channel, size and version. Final files go in a clearly marked folder so nobody posts a draft by mistake. Source files stay in the shared drive, not on my laptop.
Strong vs weak: Strong candidates have a system and keep files where the team can find them. Weak ones say "I just know where things are."
Model answer: I ask what the deck is for and who will present it, then fix the master slides first so fonts, colors and layouts are consistent. I tidy charts so they're readable, cut clutter and make sure the person presenting can still edit it easily in Google Slides or PowerPoint. I don't turn it into something only a designer can update.
Strong vs weak: Strong answers keep the deck editable for its owner. Weak ones rebuild it in a tool nobody else uses.
Model answer: I'll work in whatever the business already uses. Canva is great for templates the team can edit themselves. Figma works well for web graphics, social sets and anything that needs components. Illustrator and InDesign are better for logos, print layouts and packaging, and Photoshop for photo editing. I match the tool to the job and to who needs to edit it later.
Strong vs weak: Strong candidates think about who edits the file next. Weak ones insist on one tool for everything.
Model answer: Size and bleed, safe margins, CMYK color or the printer's requested profile, image resolution at print size, fonts outlined or packaged into the PDF, and spelling one last time. I ask the printer for their spec sheet up front and request a proof for anything large or expensive.
Strong vs weak: Strong answers list specific checks and mention asking for a proof. Weak ones just export a PDF.
Model answer: Vector files are built from shapes and can scale to any size without losing quality, so logos and icons should live as vectors. Raster files are made of pixels, like photos, and get blurry when enlarged. It matters most for logos, signs and anything printed large.
Strong vs weak: Any experienced designer should answer this clearly. Confusion here is a warning sign.
Model answer: I ask whether anyone has the original files from whoever designed it. If not, and it's simple enough, I can rebuild it as a vector, matching the original closely, and I check the result with the owner before using it anywhere.
Strong vs weak: Strong candidates ask first and confirm the rebuild. Weak ones stretch the JPG.
Model answer: I use fonts and images the business has a license for, or ones with clear free licenses, and I note the source in the project folder. If a design needs a new paid asset, I flag the cost to the owner before buying or using it.
Strong vs weak: Strong candidates are careful and transparent about licenses. Weak ones use whatever is installed on their machine.
Model answer: A good answer is honest about their level: simple animated posts, text animations and short edits in Canva, CapCut or After Effects, for example. Many small business roles need a little motion for reels and ads, but not full video production.
Strong vs weak: Strong candidates describe what they've actually done. Weak ones overclaim and can't show examples.
Model answer: I ask a few simple questions: is it the colors, the image, the amount of text, or the overall feel? I might show two quick alternatives that push in different directions and see which one they lean toward. Usually the reason comes out once they can compare.
Strong vs weak: Strong answers guide the owner to specifics. Weak ones get defensive or start over from scratch.
Model answer: I aim to get the brief right up front so revisions are small. I share an early rough version before polishing, collect all feedback in one place, and confirm the list of changes before I make them. If feedback keeps changing direction, I go back to the brief with the owner.
Strong vs weak: Strong candidates share early and consolidate feedback. Weak ones polish for days and then get surprised.
Model answer: I don't pick a side quietly. I put both comments in front of the person who owns the decision and ask them to choose. Then I note the decision so it doesn't come up again.
Strong vs weak: Look for clarity about who decides. Weak answers try to please both and end up with a muddled design.
Model answer: A good answer describes what went wrong, when they raised it, and what they changed afterward, like adding buffer time or asking for copy earlier.
Strong vs weak: Strong candidates warned people early. Weak ones blame others or say it's never happened.
Model answer: A clear brief for each request: what it's for, where it will appear, the deadline, the copy and any examples you like. Access to the brand files and tools. And quick, specific feedback, even if it's just a few words.
Strong vs weak: Strong candidates know what they need and ask for it. Weak ones say they need nothing.
Model answer: I follow trends to stay fresh in campaigns and ads, where trying things is fine, but I keep the core brand stable. A trend can show up in a seasonal post without changing the logo or the main type.
Strong vs weak: Strong answers separate campaign freshness from brand stability. Weak ones chase every trend.
Model answer: I'd keep a simple log of what was made and shipped each week, and work with whoever runs marketing to look at which designs did better in their tests. I'd also point to time saved, like templates the team now uses without waiting for me.
Strong vs weak: Strong candidates connect their work to outcomes the business already tracks. Weak ones only talk about awards or likes.
Pay the candidate for two to three hours of work. Give them your logo, brand colors and fonts (or a sample brand if you'd rather not share yours), plus a short brief: a weekend sale at one location. Ask them to deliver:
Then send one round of feedback by email, the way you normally would, and see how they handle it. Score brand fit, clarity, file quality, how well they followed the brief and how they responded to feedback.
If you would rather meet strong candidates than run this process yourself, Ryz can place a dedicated graphic designer on your team. Your designer works in your Canva, Figma or Adobe accounts and your shared drive, follows your brand guide, keeps your US business hours in your time zone, writes and speaks fluent English, and reports to you, month to month. Ryz recruiters screen every candidate through our vetting process, and you meet a named shortlist before anyone starts. Most people start in under two weeks. Tell us the role and we'll send a plan and a price, or book a call. Writing the role first? Use our graphic designer job description template, and see what the seat costs in-house in our graphic designer cost guide.
Three usually works: a short screen with a portfolio review, a structured interview with these questions and a walkthrough of two past projects, and a paid exercise with one round of feedback. Have the person who will brief the designer join at least one round.
Work that looks like what you need: social posts, ads, flyers, slides or packaging for real businesses. Look for consistency within each brand, clean layouts and readable text. Ask what the brief was and what changed after feedback.
A graphic designer creates marketing and brand materials: posts, ads, print and presentations. A product designer designs how an app or website works, including user flows and screens. For app or UX work, a product designer is the better fit.
Some can post, but planning content, writing captions and managing comments is a separate job. If you need both, consider a designer plus a social media manager. Our social media manager interview questions cover that role.
It can, and it gives you the most useful signal. If you'd rather not share brand files with every candidate, use a sample brand for the exercise and your real one for the finalist.
Questions we didn't answer? Email info@ryzlabs.com.