Design & User Experience Topics
User experience design, frontend architecture, and design systems. Includes UX principles, accessibility, and design documentation.
User Personas and Journey Mapping
Covers the end to end practice of creating research grounded user personas and journey maps that synthesize qualitative and quantitative data into actionable artifacts that guide product and design decisions. Candidates should demonstrate research methods and synthesis techniques such as interviews, surveys, analytics analysis, contextual inquiry, affinity mapping, and empathy mapping, and show how to triangulate evidence to define user segments and persona attributes including goals, motivations, behaviors, pain points, constraints, context of use, and validation evidence. The topic includes structuring personas so they are usable by product and design teams while avoiding stereotyping, documenting use cases, and linking personas to success metrics and validation approaches. For journey mapping, candidates should be able to map flows and scenarios across timelines or stages, identify touchpoints, channels, emotional states, key moments of truth, pain points, opportunities, and barriers to conversion or product use, and link journey artifacts to service blueprints and operational considerations. Also assessed are practices for prioritizing opportunities, iterating and validating artifacts with users, running cross functional workshops, communicating findings to stakeholders, tooling and deliverable formats, storytelling and visualization choices, using artifacts to inform requirements testing and metrics, and examples of how personas and journey maps changed product direction.
Design Iteration and Feedback
Covers the end to end practices of gathering, evaluating, synthesizing, and incorporating feedback into iterative design and research cycles. Candidates should demonstrate how they plan and run user research and usability testing, collect feedback from users, teammates, and stakeholders, and use structured synthesis methods such as affinity mapping and thematic analysis to generate actionable insights. Includes practical iteration techniques such as rapid prototyping, playtesting, split testing and controlled experiments, incremental improvements, and versioning of design artifacts. Assesses how candidates prioritize suggested changes using impact and effort considerations, product vision alignment, and technical constraints, and how they define and measure success through quantitative metrics and qualitative signals. Examines interpersonal skills around openness to critique, responding without defensiveness, communicating trade offs and decisions to stakeholders, defending choices with evidence and rationale, documenting learnings, and establishing processes for continuous improvement and knowledge transfer. Also includes learning from past iterations and mistakes and adapting research methodology or recommendations based on new evidence.
Design Systems and Component Architecture
Comprehensive coverage of principles and practices for designing, building, and maintaining reusable component libraries and design systems that enable consistent and scalable user interfaces across products and teams. Topics include decomposition of interfaces into components, atomic and modular design principles, component hierarchies and responsibilities, composition versus inheritance and composition patterns, and designing component application programming interfaces, properties and variants. Candidates should be able to discuss naming conventions, file structure and organization, strategies for avoiding tight coupling and property drilling, state and variant management for stateful and stateless components, and approaches to tokenization and theming for consistent styling. Also covered are accessibility and responsive behavior, documentation and developer handoff tooling, testing strategies including unit, integration and visual regression testing, governance and versioning practices, system ownership and release strategies, cross team collaboration between design and engineering, and trade offs between flexibility and constraint when scaling a system or applying system thinking to one off designs or prototypes.
Findings Presentation and Impact
Ability to clearly present analytical findings and insights to stakeholders, and explain how those findings shaped a decision, process, or outcome. Covers structuring a findings narrative (context, evidence, recommendation), choosing the right visualization or format for the data, tailoring depth and language for technical versus non-technical audiences, and demonstrating measurable impact and follow-through on recommendations.
Technical Depth & Areas of Specialization
Every strong candidate has one or more areas of technical depth that go beyond generalist knowledge. Discuss the area(s) where you have the most depth: how you identify it (a subsystem, technology, domain, or class of problem you gravitate toward), a concrete project or accomplishment that demonstrates that depth, how you actively keep that expertise current (reading, communities, side projects, postmortems), and how that depth changes the way you make trade-offs or collaborate with generalists on your team. Areas of specialization are highly individual and role-dependent (examples span distributed systems reliability, accessibility and design systems, security architecture, data pipelines, performance optimization, mobile platforms) - the interviewer should probe the candidate's own stated specialization rather than assume a fixed domain.
Problem Solving When Design Meets Technical Reality
Share examples of times when your design vision met technical limitations or constraints. How did you handle it? Did you compromise, find creative solutions, or work with engineers to implement something unexpected? Discuss your mindset: are you flexible when constraints exist, or do you fight for your design? Demonstrate pragmatism and collaborative problem-solving.
Company Specific Documentation Challenges
Prepare to analyze and discuss documentation and role specific technical challenges for a particular company, product, audience, or team. This includes researching the company products and target users, identifying what current documentation does well and where it falls short, diagnosing technical or scale constraints, and articulating a prioritized approach to improvement. Candidates should be able to assess the scope and impact of problems, propose concrete solutions and tradeoffs (for example content strategy, tooling, structure, workflows, automation, or developer experience changes), describe how they would engage stakeholders and measure success, and tie recommendations to similar past work or learning. For entry level candidates, demonstrating thoughtful questions about the documentation context and showing awareness of domain specifics is also valuable.
Instructional Design & Content Creation Basics
Core principles of how people learn and how to structure content effectively. Understand concepts like learning objectives, Bloom's taxonomy, cognitive load, active learning, spaced repetition, and knowledge retention. Know different content formats (video, interactive modules, simulations, case studies) and when each is appropriate. Understand the difference between compliance training and development training.
Learning Objectives and Outcomes
Create clear, measurable learning objectives and define the outcomes that indicate successful learning transfer to the workplace. This covers writing objectives using Specific Measurable Achievable Relevant Time bound principles, mapping objectives to cognitive levels from knowledge to application and behavior change using Bloom taxonomy, defining observable assessment criteria, selecting evaluation methods, and linking learning outcomes to business performance measures. Candidates should be able to specify how to measure success through assessments and performance indicators, design formative and summative evaluation, and iterate on content based on outcome data.