Skip to main content
Guide to Interviewing Designers
Updated over a year ago

Dover recommends tailoring your interview plan to each specific role. For Design roles, you can tailor your Interview Plan in Dover using the suggested interview plan, interview questions, scheduling templates, and feedback forms.


📆 Interview Plan

First Interview ⏰ 30 mins

  • Dover Interviewer or Recruiter Screen

Second Interview - Hiring Manager Interview / Portfolio Review ⏰ 30 mins

Please see take portfolio review examples below.

Onsite ⏰ 2 hrs 30 mins

  1. Intro/Prep - ⏰ 15mins

    1. Overview of what the day will look like

    2. Interviewer: Recruiter / Head of Talent

  2. Behavioral 1 - ⏰ 30mins

    1. Review cultural fit questions

    2. Interviewer: Hiring Manager / Leadership in Business Area

  3. Technical Screen - ⏰ 30mins

    1. Review remaining technical / role-specific skillset content

    2. Interviewer: Full time Employee from Business Area

  4. Social Interview - ⏰ 30mins

    1. Casual non-evaluative opportunity for candidate to meet people from other Business Areas

    2. Interviewers: 2 Full time Employees from different Business Areas

  5. Behavioral 2 - ⏰ 30mins

    1. Review cultural fit questions

    2. Interviewers: Other Hiring Manager / Leadership in Business Area

  6. Wrap-Up - ⏰ 15mins

    1. Close out the day with the candidate, sell company

    2. Interviewers: Chief of Staff / C-Suite / Founder / Executive


👩‍💻 Take home assignment examples

Below are some sample take home assignments

UI/UX Designer Interview

  1. Introduction and Background (5 minutes)

    • Introduce the interviewer and allow the candidate to briefly introduce themselves.

    • Discuss the candidate's background, experience, and motivation for the UI/UX Designer role.

  2. Portfolio Review (15 minutes)

    • Quickly review the candidate's portfolio, focusing on key projects and design skills.

    • Evaluate their design process, user interface design, information architecture, user research, and visual design skills.

    • Ask the candidate to explain their design decisions and problem-solving approach.

  3. Design Exercise (10 minutes)

    • Provide a quick design exercise relevant to the UI/UX Designer role.

    • Assess the candidate's ability to think on their feet, apply design skills, and present a solution within a short timeframe.

  4. Closing (5 minutes)

    • Summarize the interview and thank the candidate for their time.

    • Provide next steps in the hiring process and address any questions the candidate may have.

Product Designer Interview

  1. Introduction and Background (5 minutes)

    • Introduce the interviewer and allow the candidate to briefly introduce themselves.

    • Discuss the candidate's background, experience, and motivation for the Product Designer role.

  2. Portfolio Review (15 minutes)

    • Quickly review the candidate's portfolio, focusing on key projects and design skills.

    • Evaluate their understanding of the product design process, user research, user experience design, and prototyping.

    • Ask the candidate to explain their design decisions and problem-solving approach.

  3. Design Exercise Discussion (10 minutes)

    • Discuss the candidate's approach to a previous design exercise or challenge.

    • Evaluate their critical thinking, creativity, and ability to articulate their design choices.

  4. Closing (5 minutes)

    • Summarize the interview and thank the candidate for their time.

    • Provide next steps in the hiring process and address any questions the candidate may have.

Visual / Graphic Designer Interview

  1. Introduction and Background (5 minutes)

    • Introduce the interviewer and allow the candidate to briefly introduce themselves.

    • Discuss the candidate's background, experience, and motivation for the Visual/Graphic Designer role.

  2. Portfolio Review (15 minutes)

    • Quickly review the candidate's portfolio, focusing on key projects and design skills.

    • Evaluate their design skills, aesthetics, branding, layout, typography, and proficiency in relevant software.

    • Ask the candidate to explain their design decisions and showcase their visual design capabilities.

  3. Design Exercise Discussion (10 minutes)

    • Discuss the candidate's approach to a previous design exercise or challenge.

    • Evaluate their creativity, attention to detail, and ability to adapt to design requirements.

  4. Closing (5 minutes)

    • Summarize the interview and thank the candidate for their time.

    • Provide next steps in the hiring process and address any questions the candidate may have.


✉️ Scheduling Email Templates

The following are examples of scheduling emails for each interview round.

First Interview

Scheduling Email A (Interview with person sending outreach)

Hi {{first_name}},

Great to hear from you, I'm excited to chat! To make scheduling easier, could you find some time on my calendar here: {{scheduling_link}}

Looking forward to it!

Scheduling Email B (Interview with person who did not send outreach)

Hi {{first_name}},

Great to hear from you! We’d love to schedule a call with a member of our recruiting team to learn further about your experience and share further information on this opportunity.

To make scheduling easier, could you please find a time here: {{scheduling_link}}

Thanks,

{{sender_first_name}}

Rejection

Hi {{first_name}},

Thanks for taking the time to talk with us about the {{job_title}} position. Your background is impressive, and we really enjoyed speaking with you. Unfortunately, at this time we feel it's not the right fit.

We appreciate the time you took to learn more about {{client_name}} and hope you don't mind if we reach back out in the future.

Best,

{{sender_first_name}}

Second Interview / Portfolio Review

Scheduling

Hi {{first_name}},

We enjoyed speaking with you about the {{job_title}} role and would love to move forward! The next step in our process would involve talking to the hiring manager {{interviewer_first_name}}, {{interviewer_role_title_with_article}}. I’ve looped them in here in case you have any questions about the upcoming Portfolio Review Interview to address before connecting live.

Here's {{interviewer_first_name}}'s calendar to find a time: {{scheduling_link}}.

Hope the two of you find a chance to connect soon.

{{sender_first_name}}

Rejection

Hi {{first_name}},

Thanks for taking the time to learn about the {{job_title}} role at {{client_name}}. Our team enjoyed speaking with you, but ultimately we felt that it wasn't a fit at this time.

I hope you don't mind if we keep your information on file and reach out to you in the future! Best of luck in your search.

Thanks,

{{sender_first_name}}

Onsite

Scheduling

Hi {{first_name}},

We would love to move you forward to our next stage, where you would meet more of the team virtually. The onsite will last 2.5 hours and consist of the following rounds:

The virtual onsite should last about 2.5 hours, and below are some more details as to what you can expect from each panel:

  • Prep Session with < Interviewer Name> (Recruiter/HoT) - 15mins

  • Behavioral Interview with < Interviewer Name> (Hiring Manager)- 30mins

  • Take home interview discussion <Interviewer Name> - 30mins

  • Casual Chat with < Interviewer Name> and <Interviewer Name> - 30mins - Casual non-evaluative opportunity to learn more about the company’s culture - 2 FTE from other BAs

  • Behavioral Interview with <Interviewer Name> (Other HM/Leadership in BA) - 30mins

  • Close out the day with < Interview Name> ( CoS/C-Suite) - 15mins

Could you please share some time slots in the coming days that work for you? I'll then send over an invite that works best for everyone.

The team is looking forward to meeting you, please let me know if you have any questions! Congrats on reaching this final stage!

Best,

{{sender_first_name}}

Rejection

Hi {{first_name}},

Thank you for meeting the team for our {{job_title}} role. We really appreciate you taking the time to be part of our interview process over the last few weeks.

At this point, we will not be able to move forward with your candidacy. We'll keep your information on file and hope we can reconnect in the future.

Regards,

{{sender_first_name}}


📓 Feedback Forms / Evaluation criteria

Interview rubrics / feedback form criteria can be an effective tool to assess candidates consistently and objectively during the interview process across various interviewers. Here's an example of a rubric for evaluating candidates for a Product Manager role.

Evaluation

Product Knowledge: Assesses the interviewee’s understanding of product management principles, industry best practices, and relevant technologies.

  • Exceptional: The exceptional product manager candidate has a deep knowledge of product management principles and industry best practices. They have a passion for effective product design and in-depth understanding of the latest technologies and trends. They are able to apply their knowledge in order to provide strategic and insightful guidance on product development.

  • Good: The good product manager candidate has a basic understanding of product management principles and industry best practices. They demonstrate consistency by learning testing and iterating to optimize product design. They have a working knowledge of relevant technologies, and can apply this knowledge to aid in the development of the product.

  • Average: The average product manager candidate is able to apply some of their knowledge surrounding product management principles and industry best practices, but may lack expertise in specific areas. They may be able to provide basic direction on product development, but are not able to provide real strategies to optimize the product design.

  • Below Average: The below average product manager candidate has difficulty demonstrating their knowledge of product management principles and relevant industry best practices. They lack any real understanding of technology trends and their application in product design. They are unable to provide any insightful guidance to aid in product development.

Problem Solving: Evaluates the interviewee's ability to think through complex problems, create and test hypotheses, and make decisions.

  • Exceptional: The Exceptional Product Manager candidate actively crafts and evaluates hypotheses to solve complex problems. The Exceptional candidate also demonstrates creativity and innovativeness to come up with unexpected solutions and has the ability to make tough decisions quickly and confidently. They can also provide examples of successful decisions or problem resolutions which they initiated and how it affected the project.

  • Good: The Good Product Manager candidate is able to think through complex problems and create hypotheses to test solutions, but they might be more conservative in their approach than an Exceptional candidate. They are comfortable making decisions but might not necessarily be able to demonstrate any unique problem-solving skills.

  • Average: The Average Product Manager candidate is capable of understanding problem-solving situations, but they may be less inclided to come up with creative solutions or make tough decisions. They are capable of understanding and executing tasks but lack advanced problem-solving skills.

  • Below Average: The Below Average Product Manager candidate is not able to identify and address problems or craft and test hypotheses. They may be reticent to make decisions or lack the problem-solving skills necessary to be successful.

Stakeholder Management: Assesses the applicant's ability to lead a team, manage stakeholders, and communicate effectively.

  • Exceptional: The exceptional Product Manager candidate is able to lead a team of diverse stakeholders with clarity and strong communication skills. They can effectively identify the needs of the stakeholders, present solutions, and motivate the team through each product venture. They are proactive with their stakeholder relationships and have a proven history of successful product launches.

  • Good: The good Product Manager candidate is capable of leading a team and maintaining effective communication with stakeholders. They understand the needs of stakeholders and are able to develop and execute reasonable solutions. They are capable of problem solving and managing complexity.

  • Average: The average Product Manager candidate has basic knowledge of product management and a basic understanding of team dynamics. They are able to lead a team and maintain basic communication with stakeholders but may struggle with complex problem solving. They are able to come up with solutions, but the solutions may not be the most effective ones.

  • Below Average: The below average Product Manager candidate may lack the skills needed to effectively lead a team and communicate to stakeholders. They lack an in-depth understanding of product management and have little experience managing complex product projects. They may struggle to develop feasible solutions and communicate lack of clarity with stakeholders.

Cross-Functional Understanding: Evaluates the applicant's ability to collaborate and work with teams from different departments and organizations.

  • Exceptional: Exceptional product manager candidates have the ability to quickly become an expert in all areas related to the product. They understand the complexities and limitations of each team’s environment, tackling cross-functional challenges and finding creative ways to work through them. They are able to anticipate and resolve issues between teams, leveraging their relationships with other departments, stakeholders and the company to get results.

  • Good: Good product manager candidates have a basic understanding of various teams and functions that make up the product life cycle. They are able to recognize the importance of collaboration and can effectively communicate with members of other teams to ensure success. They have strong communication skills and are able to gain consensus across multiple disciplines.

  • Average: Average product manager candidates have an awareness of how different functions work together. They are able to see how their product decisions may impact other teams and processes, but are unable to effectively navigate the complexities. They have the ability to communicate broadly, but struggle to gain buy in from cross-functional partners without instructions or guidance.

  • Below Average: Below average product manager candidates have a limited understanding of the different functions within a product's life cycle. They may be narrowly focused on their specific area of expertise, without any ability to collaborate or interact with other teams. They may not understand the complexity of interdepartmental partnerships, leading to misunderstandings with other team members and slower progress.

Did this answer your question?