COMPLETE INTERVIEW GUIDE

Multimedia Designer: Tricky Interview Questions, Best Answers & Complete Interview Guide

By salarymarkets.io · Original preparation guide · General advice, not employer-verified questions

Multimedia Designer interviews test more than your ability to make polished visuals. Employers want to know whether you can carry a clear idea across a responsive website, an interactive prototype, a video, a digital campaign and a printed piece without losing usability or brand consistency. A strong portfolio opens the conversation; explaining the decisions behind it helps you win the offer.

Expect questions about three things at once: craft across media, judgment about user needs and business goals, and reliable delivery. This guide helps you explain your process, handle difficult trade-offs and show that your work remains effective beyond the presentation screen.

01Understanding the Multimedia Designer role

A Multimedia Designer creates connected visual experiences across web, digital, video, print and interactive formats. Within UX/UI and digital design, the role often bridges interface design, brand communication and motion rather than owning every part of product research or software development.

Typical responsibilities include interpreting briefs, mapping content and user journeys, designing responsive layouts, creating graphics and motion assets, prototyping interactions, adapting campaigns across channels, preparing print files, and handing off implementation-ready assets. Designers also review accessibility, maintain reusable components and check that the finished work matches its intended behavior.

Common tools include Figma for interface design and prototypes, Photoshop and Illustrator for imagery and vector work, After Effects and Premiere Pro for motion and video, and InDesign for print layouts. Some roles also use web authoring tools, basic HTML and CSS, asset libraries and collaboration systems. Interviewers usually care more about your decisions and delivery standards than your software list.

Average versus exceptional performance
Area	Average performer	Exceptional performer
Concept	Creates attractive individual assets	Builds a clear idea that supports a user need across media
Adaptation	Resizes the same layout	Reworks hierarchy and interaction for each context
Usability	Designs the ideal screen	Accounts for accessibility, responsive behavior and edge cases
Workflow	Delivers finished visuals	Provides reusable components, clear specifications and organized files
Evaluation	Defends work through personal taste	Uses task feedback, production checks and relevant outcomes

The balance changes by employer. A small team may need one designer to handle a website, product demo and brochure; a larger organization may assign a narrower specialty within a shared design system. Junior designers are usually assessed on execution and responsiveness to feedback. Senior designers are expected to shape direction, resolve cross-functional trade-offs and improve how the team delivers.

02What AI can and cannot do

AI can support exploration and production, but it does not remove responsibility for usability, accuracy or rights. Interviewers want a practical explanation of where you use it, what you verify and when you choose another method.

What AI already does well

Producing initial concept variations and visual references for discussion
Assisting with image cleanup, masking and repetitive production tasks
Generating draft transcripts and captions that need review
Suggesting placeholder copy and alternative content structures

Where AI helps but needs oversight

Generated imagery, which needs review for rights, representation and visual errors
Interface drafts that may omit error states, keyboard behavior or realistic content
Code suggestions that require developer review and accessibility testing
Translations and summaries that may distort meaning or miss local context

Where human judgment remains especially valuable

Understanding what users are trying to accomplish and which problem matters
Creating hierarchy and interaction patterns that work across contexts
Balancing brand expression with clarity, accessibility and technical constraints
Taking responsibility for consent, factual accuracy and final production quality

Skills to develop now

Documented AI workflows with clear review and approval steps
Privacy and licensing checks before uploading material or using generated assets
Accessible interaction design and usability evaluation
Cross-media systems that connect components, motion and campaign assets
Explaining design decisions without relying on the tool that produced the draft

0316 tricky interview questions and strong answers

1. “Walk me through a portfolio piece that looks strong but did not work as intended.”

Why they ask: They want to know whether you distinguish visual polish from actual effectiveness.
A strong answer shows: Honest reflection, evidence of the problem and a specific next step.
Example answer: I'd choose a real project and explain the intended task before showing the visuals. I'd describe the evidence available, such as usability observations, stakeholder feedback or implementation issues, without inventing results. Then I'd show where the design fell short and the revision I made or would test. If the revision never shipped, I'd say so and explain how I would evaluate it.
Avoid: Disguising a success as a failure, blaming users or claiming improvements you never measured.

2. “How would you adapt one concept across a website, video and printed brochure?”

Why they ask: Cross-media thinking is central to the role, and adaptation is more than resizing.
A strong answer shows: A consistent message with deliberate changes to hierarchy, pacing and interaction.
Example answer: I'd establish the audience, core message and action first, then identify what must stay recognizable: typography, color, imagery and tone. The website needs responsive hierarchy and a clear path to action. The video needs a sequence that works over time, including captions. The brochure needs readable static information and a practical next step. I'd review them together for consistency, then check each in its actual context.
Avoid: Pasting the same composition into every format or treating print as a website screenshot.

3. “A stakeholder wants an impressive animation that makes a key task harder. What do you do?”

Why they ask: Tests your ability to protect usability without dismissing creative ambition.
A strong answer shows: Respectful challenge, alternatives and a way to evaluate the trade-off.
Example answer: I'd ask what the animation is meant to achieve and show where it interrupts the task. Then I'd prototype a lighter version that preserves the idea without blocking content or input. I'd include reduced-motion behavior and discuss loading implications with engineering. If the trade-off remains unclear, I'd suggest a focused task test rather than arguing from taste.
Avoid: Rejecting animation automatically or accepting it because a senior stakeholder requested it.

4. “How do you start when the brief just says to make the experience more engaging?”

Why they ask: Vague requests reveal whether you can define a useful design problem.
A strong answer shows: Clarifying questions, explicit assumptions and early alignment.
Example answer: I'd ask who the experience serves, what people currently struggle with and what action the business wants to support. I'd also clarify channels, constraints, content ownership and approval. I'd turn that into a short brief with a proposed outcome and a way to evaluate it. If information is missing, I'd label assumptions and share a rough direction before investing in polished assets.
Avoid: Starting with decorative effects or refusing to move until every detail is known.

5. “How do you keep a responsive design from becoming a smaller desktop layout?”

Why they ask: They are checking whether you understand behavior and content priority across screens.
A strong answer shows: Content-led decisions, realistic states and collaboration with developers.
Example answer: I'd identify the primary task and content hierarchy, then explore how navigation, layout and controls should change as space becomes constrained. I'd test long labels, missing imagery and different content lengths rather than designing only an ideal screen. I'd document layout rules and discuss intermediate widths with developers. The handoff should explain behavior, not just provide separate desktop and mobile pictures.
Avoid: Shrinking text, hiding essential content or assuming a few mockups cover every viewport.

6. “How do you build accessibility into multimedia work?”

Why they ask: Accessibility affects interfaces, motion, video and documents, not just one checklist.
A strong answer shows: Format-specific habits and awareness of implementation responsibilities.
Example answer: For interfaces, I plan readable hierarchy, contrast, visible focus and states that do not rely on color alone. I specify keyboard behavior and review the implementation with developers. For video, I review captions and consider audio description when essential information is visual. For motion, I avoid harmful flashing and define reduced-motion alternatives. For documents, I consider reading order, meaningful links and accessible export requirements.
Avoid: Claiming a contrast checker proves accessibility or treating captions as the entire process.

7. “Tell me how you would handle conflicting feedback from marketing, product and engineering.”

Why they ask: The role often sits between teams with different priorities.
A strong answer shows: A decision framework rather than passive compromise.
Example answer: I'd separate the feedback into user needs, business requirements, technical constraints and preferences. I'd bring unresolved conflicts back to the agreed goal and explain the consequences of each option. Engineering constraints may change the implementation without changing the core experience. I'd confirm the decision-maker, document the agreed direction and request consolidated feedback so the next revision does not restart the debate.
Avoid: Following whoever speaks last or presenting stakeholders as obstacles to good design.

8. “How would you deliver a launch package when the deadline suddenly moves forward?”

Why they ask: Tests prioritization and production judgment under pressure.
A strong answer shows: Scope negotiation, dependencies and a clear quality floor.
Example answer: I'd identify what must be ready for launch and which assets depend on approved messaging or technical work. I'd propose a smaller package built from a strong shared direction, with later enhancements scheduled separately. I would protect accuracy, accessibility and essential production checks rather than cutting them silently. I'd confirm the revised scope and review deadlines so everyone understands what will and will not ship.
Avoid: Promising everything, skipping checks without disclosure or relying only on overtime.

9. “What belongs in a developer handoff besides the design file?”

Why they ask: A polished prototype does not explain every implementation requirement.
A strong answer shows: Clear specifications, collaboration and accountability after handoff.
Example answer: I'd include component behavior, responsive rules, interaction states, content guidance and export-ready assets. I'd identify focus behavior, errors, loading and empty states where relevant. Motion needs timing and reduced-motion guidance, while media needs playback and fallback behavior. I'd walk through the design with developers, resolve questions and review the implemented experience rather than treating handoff as the end of my responsibility.
Avoid: Assuming developers can infer everything from a clickable prototype.

10. “How do you know whether your design was successful?”

Why they ask: They need someone who can evaluate more than appearance.
A strong answer shows: Measures tied to purpose and honesty about attribution.
Example answer: I'd define success before production. An interface might be evaluated through task completion, errors and user feedback; a campaign page through relevant actions and traffic quality; a printed guide through comprehension and practical use. I'd compare against a useful baseline where available and account for changes in audience or messaging. I would not attribute a business result entirely to design when other factors changed.
Avoid: Using one metric for every format or presenting subjective praise as proof of business impact.

11. “What would you do if the supplied images are not cleared for every intended channel?”

Why they ask: Cross-media projects can expose licensing gaps that are easy to overlook.
A strong answer shows: A practical rights-checking process and willingness to escalate uncertainty.
Example answer: I'd confirm the source, license, permitted uses and any limits on distribution, editing or duration. I'd also check releases where identifiable people are involved. An asset approved for one use is not automatically cleared for another. I'd document the decision and work with the appropriate owner or legal team when necessary. If clearance cannot be confirmed, I'd replace the asset rather than assume it is safe.
Avoid: Treating online availability as permission or assuming a purchased asset has unlimited rights.

12. “How do you prepare the same visual system for digital and print?”

Why they ask: They are testing production knowledge beyond screen-based composition.
A strong answer shows: Medium-specific preparation and verification with production partners.
Example answer: I'd keep the visual identity consistent while adapting the files to their destination. Digital assets need appropriate dimensions, compression and formats. Print requires checking bleed, safe areas, image resolution, fonts and the printer's color and PDF specifications. I'd request a proof when appropriate and review legibility at the intended size. I would confirm requirements with the printer instead of relying on a generic export preset.
Avoid: Sending a screen export to print or assuming color will match perfectly across media.

13. “When would you create a reusable component rather than a custom asset?”

Why they ask: They want to see how you balance consistency with creative flexibility.
A strong answer shows: Judgment about repetition, maintenance and genuine exceptions.
Example answer: I'd look at how often the pattern appears, how stable its purpose is and who needs to maintain it. Repeated navigation, cards or campaign layouts usually benefit from a reusable structure. A distinctive hero moment may justify custom work, but it should still use shared foundations where possible. I'd avoid building an elaborate system for a one-off need and document exceptions so they do not become accidental standards.
Avoid: Making everything unique or forcing every message into an unsuitable template.

14. “Would you use AI-generated visuals or interface designs in our work?”

Why they ask: Tests current judgment about efficiency, privacy and accountability.
A strong answer shows: A bounded workflow with human review rather than unconditional enthusiasm.
Example answer: I'd first check company policy, data handling and the tool's usage terms. AI can help explore directions or speed up production tasks, but I would review outputs for accuracy, representation, rights and brand fit. For interfaces, I'd validate content, states and accessibility instead of trusting the generated layout. I would not upload confidential materials without approval or present synthetic imagery as evidence of a real customer experience.
Avoid: Claiming generated work is automatically cleared, accessible or ready to publish.

15. “Pitch a cross-media improvement for our organization.”

Why they ask: Tests preparation, communication and whether your ideas fit the employer's needs.
A strong answer shows: A focused opportunity supported by visible evidence and stated assumptions.
Example answer: I'd use a structure: observed friction, target audience, proposed experience, supporting formats and evaluation. For example, if public materials make a service difficult to understand, I'd propose a clearer landing-page journey supported by a captioned explainer and a concise printable guide. I'd label that as a hypothesis based on public information, not a proven diagnosis, and explain what I'd validate before production.
Avoid: Proposing a full rebrand without context or presenting speculative criticism as established fact.

16. “What would your first 90 days look like?”

Why they ask: Shows whether you can learn the environment before changing it.
A strong answer shows: Listening, practical improvements and a sustainable delivery process.
Example answer: I'd begin by understanding audiences, business priorities, existing research, brand assets and production workflows. Next, I'd deliver a focused improvement while learning how approvals and implementation work. Once I had that context, I'd propose a prioritized plan for reusable assets, accessibility gaps and cross-media consistency. I'd agree evaluation methods with the team rather than promising results before seeing the evidence.
Avoid: Promising an immediate redesign or spending the entire period auditing without delivering anything.

Adapt these examples to your real experience — never invent results you can't discuss in detail.

04Practical tests and real-world challenges

Cross-media campaign adaptation

Evaluated: Concept consistency, hierarchy, format awareness and production discipline.
Approach: Clarify the audience and message, establish a shared visual direction, then adapt it into the requested web, video and print deliverables. State assumptions and check export requirements.
Excellent looks like: A coherent family of assets that uses each medium deliberately, with concise reasoning and organized source files.
Common mistakes: Resizing one layout, ignoring safe areas or submitting attractive files that do not meet the brief.

Responsive interface and interaction prototype

Evaluated: User flow, responsive behavior, accessibility and communication with implementation teams.
Approach: Identify the primary task, map the essential flow and prototype the requested states. Explain layout rules, keyboard considerations and any limitations of the prototype.
Excellent looks like: A clear, usable experience with realistic content, relevant edge cases and practical handoff notes.
Common mistakes: Overdesigning decorative details, omitting errors or treating prototype behavior as proof of accessible implementation.

Portfolio review presentation

Evaluated: Your contribution, reasoning, cross-media range and ability to reflect on outcomes.
Approach: Choose a focused set of projects and explain the brief, audience, your role, constraints, decisions and evidence. Show process only where it clarifies an important choice.
Excellent looks like: Clear ownership, strong craft and honest discussion of results, limitations and lessons.
Common mistakes: Taking credit for others' work, showing only polished mockups or claiming unsupported business impact.

0510 ways to stand out

Bring a short review of the employer's digital experience with specific observations and a clearly labeled hypothesis.
Show how one concept changed across web, motion, print and interactive formats.
Label your exact responsibilities and collaborators on every portfolio project.
Explain a usability or production trade-off, including the option you rejected.
Include reusable components or templates alongside expressive visual work.
Show accessibility decisions in context rather than adding a generic compliance slide.
Prepare a concise handoff example with responsive rules and interaction states.
Explain where AI supports your workflow and where you require human review.
Connect design choices to user tasks and business goals without inventing results.
Follow up with a concise recap and any relevant materials you promised.

0610 questions to ask your interviewer

What would make this hire successful after six months? — Reveals the actual balance of craft, delivery and business expectations.
How is the role divided between UX/UI, motion, digital campaigns and print? — Clarifies whether the title matches the work you want to do.
What research or user feedback informs design decisions here? — Shows how the team validates assumptions and identifies problems.
How does a project move from brief to approval and implementation? — Uncovers ownership, review stages and delivery bottlenecks.
Who resolves disagreements between brand, usability and technical constraints? — Reveals decision-making practices and how trade-offs are handled.
How mature are the design system and shared asset libraries? — Identifies whether you will maintain an established system or build foundations.
Who owns accessibility testing across design, development and content? — Clarifies responsibilities beyond visual checks.
What software, production support and external partners are available? — Helps you assess whether expectations match the resources.
What policies guide AI use, confidential materials and asset rights? — Shows awareness of practical governance and production risks.
How do designers receive feedback and develop their skills here? — Reveals the support available for growth and collaboration.

07Interview expectations by company type

These categories overlap, and every employer is different. Use them as typical patterns, not universal rules.

Startup: Pre-seed to Seed

Priorities: Clear communication, fast learning and versatile execution with limited resources.
How the role differs: You may design the website, product demonstrations, pitch materials and early campaign assets.
Evaluated skills: Prioritization, lightweight prototyping, adaptable visual systems and independent delivery.

Q1. Where would you start if we have no design system?
Identify recurring needs, establish basic typography and color foundations, and create reusable patterns as real work requires them.
Q2. How would you explain a product that is still changing?
Focus on the stable user problem, use modular layouts and keep changeable interface details easy to update.
Q3. What would you outsource first?
Assess the team's skills and risks, then outsource specialist work where quality or production requirements exceed internal capacity.

Prepare: Review the product story and bring a lean plan for the most urgent design needs.
Avoid: Proposing a large design-system program before understanding immediate priorities.
Smart question: “Which design deliverables are currently blocking the team?”

Startup: Series A to C

Priorities: Scaling quality while supporting product adoption and growth.
How the role differs: You may connect product interfaces, launch campaigns and reusable marketing assets.
Evaluated skills: Systems thinking, cross-functional collaboration and outcome-based evaluation.

Q1. How would you scale design output?
Identify repeatable work, build maintained templates and components, and reserve custom effort for meaningful differences.
Q2. How would you support a product launch?
Align on the user problem and message early, then coordinate interface imagery, landing pages, motion and sales materials.
Q3. How would you evaluate campaign variations?
Agree the goal and comparison method with the growth team, isolate meaningful differences and interpret results in context.

Prepare: Bring evidence of reusable systems and collaboration across product and marketing.
Avoid: Showing only isolated hero pieces without explaining delivery at scale.
Smart question: “Where do product and marketing design currently lose consistency?”

Startup: Pre-IPO

Priorities: Credibility, brand consistency and careful management of public-facing claims.
How the role differs: Design work may involve communications, legal, executives and formal approval stages.
Evaluated skills: Discretion, version control, polished execution and documented decisions.

Q1. How would you handle sensitive launch materials?
Use approved storage and access controls, confirm sharing rules and avoid unapproved external tools.
Q2. How do you prevent unsupported claims in visuals?
Confirm data sources and wording with the responsible owners, including chart labels and motion callouts.
Q3. How do you keep reviews from derailing delivery?
Identify required reviewers early, separate concept approval from production checks and track changes against the approved direction.

Prepare: Review public messaging and prepare examples of disciplined approval workflows.
Avoid: Treating governance as unnecessary bureaucracy or uploading confidential work into AI tools.
Smart question: “Which materials require legal or executive review?”

Large Business: Global

Priorities: Consistency across markets, localization readiness and scalable asset production.
How the role differs: You may create master experiences and assets that regional teams adapt.
Evaluated skills: Localization planning, flexible layouts, asset governance and asynchronous communication.

Q1. How do you design for multiple languages?
Allow for text expansion, avoid unnecessary text inside imagery and review script and layout needs with regional specialists.
Q2. How would you localize motion assets?
Separate text and voice tracks, plan timing flexibility and provide editable source files with clear instructions.
Q3. How do you preserve consistency across regions?
Define shared foundations and approved flexibility, then maintain a clear source of truth for assets.

Prepare: Compare the employer's experiences across markets and note localization challenges.
Avoid: Assuming translation alone makes an experience suitable for another audience.
Smart question: “Which decisions belong to global teams and which belong to regional teams?”

Large Business: Regional

Priorities: Regional relevance within a broader brand and product framework.
How the role differs: You may adapt shared campaigns and digital experiences for regional audiences.
Evaluated skills: Audience insight, localization, stakeholder communication and practical adaptation.

Q1. How would you adapt a global campaign?
Keep the core proposition while reviewing language, imagery, content priority and calls to action for regional relevance.
Q2. What if a global template does not fit local content?
Document the problem, propose a reusable variation and seek approval rather than creating an unexplained exception.
Q3. How would you evaluate regional work?
Use regional goals and baselines, accounting for audience, channel and market differences.

Prepare: Research regional customer needs and compare local and global materials.
Avoid: Changing brand elements casually or ignoring legitimate local requirements.
Smart question: “Where do regional teams have the most freedom to adapt design?”

Large Business: Local

Priorities: Useful local experiences and reliable execution within established standards.
How the role differs: Work may include local web pages, event materials, displays and service information.
Evaluated skills: Clear hierarchy, local collaboration and efficient multi-format production.

Q1. How would you improve a local service page?
Prioritize the information people need to act, such as availability, location, accessibility and contact options.
Q2. How do you connect printed materials with digital services?
Provide a clear destination and useful context, with an accessible alternative to any QR-only path.
Q3. How do you handle recurring local requests?
Build practical templates with guardrails and clarify which changes require design review.

Prepare: Review local customer journeys and the materials used at physical locations.
Avoid: Creating generic campaign visuals that overlook practical local tasks.
Smart question: “Which local interactions generate the most customer confusion?”

Nonprofit Organization

Priorities: Mission clarity, ethical representation, accessibility and careful resource use.
How the role differs: You may support service information, fundraising, reports and volunteer experiences.
Evaluated skills: Empathy, inclusive design, consent awareness and reusable production systems.

Q1. How do you represent the people we serve ethically?
Use informed consent, respect privacy and agency, and avoid imagery or editing that distorts their experience.
Q2. How would you improve a donation journey?
Review clarity, trust, accessibility and form friction while keeping claims and use-of-funds information accurate.
Q3. How do you make limited resources go further?
Prioritize essential journeys and build maintainable templates staff can use confidently.

Prepare: Understand the mission, service audiences and existing donation or volunteer journeys.
Avoid: Using exploitative imagery or prioritizing donor aesthetics over service-user needs.
Smart question: “How are the people you serve involved in reviewing communications?”

Government

Priorities: Public access, accuracy, neutrality and compliance with applicable requirements.
How the role differs: You may design public-service interfaces, explanatory media and printed information.
Evaluated skills: Plain-language hierarchy, accessible design, documentation and structured review.

Q1. How would you simplify a complex public service?
Organize information around the resident's task, clarify eligibility and next steps, and validate wording with service owners.
Q2. How do you approach accessibility requirements?
Confirm applicable standards, document design requirements and coordinate implementation testing with responsible specialists.
Q3. How would you handle an urgent information update?
Use an approved pattern, verify the content owner and preserve accuracy and accessibility while following the escalation process.

Prepare: Review public service journeys, published design guidance and accessibility obligations.
Avoid: Favoring visual novelty over clarity or implying design review alone proves compliance.
Smart question: “How are accessibility issues tested, prioritized and resolved?”

Fortune 500

Priorities: Brand protection, scalable quality and coordination across complex teams.
How the role differs: You may specialize within an internal studio while working with product teams and agencies.
Evaluated skills: Stakeholder management, design-system fluency, production rigor and clear reporting.

Q1. How do you work with external agencies?
Align on objectives, deliverable standards, source-file ownership and review responsibilities before production begins.
Q2. How do you manage many reviewers?
Confirm decision rights, gather consolidated feedback and document approvals and outstanding risks.
Q3. How do you show the value of your work?
Connect outcomes to agreed goals and include evidence of usability, delivery quality or reduced rework where available.

Prepare: Study the brand system and bring examples of structured cross-team collaboration.
Avoid: Underestimating governance or presenting individual craft as a substitute for teamwork.
Smart question: “How does this role collaborate with product design, brand teams and agencies?”

Small Business

Priorities: Practical customer outcomes, versatility and manageable ongoing costs.
How the role differs: You may own the website, promotional graphics, short videos and printed materials.
Evaluated skills: Prioritization, customer understanding, broad production skills and maintainability.

Q1. What would you improve first?
Find the most important customer task and address clear barriers before proposing a broad visual overhaul.
Q2. How would we maintain the work without a large team?
Use accessible tools, straightforward templates and clear guidance suited to the staff who will update them.
Q3. How would you know whether it helped?
Agree relevant signals such as qualified inquiries, completed bookings or fewer repeated customer questions.

Prepare: Bring realistic examples of useful, maintainable design with clear scope.
Avoid: Proposing expensive production or complex systems without an operational need.
Smart question: “Which customer actions matter most, and who maintains materials today?”

08Compensation and salary negotiation

Multimedia Designer compensation varies by location, seniority, industry and the balance of responsibilities. A role focused on campaign production may differ substantially from one requiring advanced motion, interactive prototyping, UX/UI ownership or creative leadership. Employment type and expectations around travel or after-hours delivery also matter.

Research current market information for the actual scope and location before discussing expectations. Compare related titles such as Digital Designer, Visual Designer, Motion Designer and UX/UI Designer carefully. Similar titles may hide very different levels of responsibility, so read the duties rather than relying on the label.

When asked for expectations, explain that your target should reflect the role's scope and comparable market opportunities. Clarify whether you would own strategy, production, implementation review or team leadership before committing to a range. Support your position with relevant experience and credible research rather than your current pay alone.

Evaluate the complete package, including base pay, bonus, equity, benefits, software, equipment, training and flexibility. For contract work, also clarify revision limits, usage rights, source-file delivery and payment terms. Negotiate respectfully and make sure expanded responsibilities are reflected in the agreement.

09Final interview preparation checklist

One week before

Review the employer's web, video, interactive and print materials
Select portfolio projects with clear ownership, decisions and evidence
Prepare examples of feedback, failure and cross-media adaptation
Research compensation for the location and actual responsibilities

One day before

Test portfolio links, prototypes, video playback and offline backups
Prepare a focused observation and a clearly labeled design hypothesis
Confirm the interview format, presentation length and any practical task
Check screen sharing, audio and readable presentation settings

During the interview

Explain the user need and constraints before presenting the solution
Distinguish your contribution from the team's work
Ask clarifying questions and acknowledge missing evidence
Discuss accessibility, implementation and production checks

Immediately afterward

Send a concise thank-you note
Share promised materials without exposing confidential work
Record questions that need stronger examples
Reflect on the role's scope, resources and fit

Five essential takeaways

Show how your design supports a user task, not just a visual style.
Demonstrate thoughtful adaptation across web, digital, video, print and interactive media.
Explain trade-offs with evidence and be honest about unmeasured outcomes.
Treat accessibility, rights and production reliability as part of design craft.
Tailor your portfolio and questions to the employer's real scope and constraints.

All interview guides