Design & User Experience Topics
User experience design, frontend architecture, and design systems. Includes UX principles, accessibility, and design documentation.
Prototyping and Interaction Design
Creating prototypes across fidelities and designing interactive user flows and states to validate and communicate product behavior. This includes building low fidelity wireframes through high fidelity interactive prototypes that demonstrate navigation, transitions, micro interactions, form behavior, error and loading states, and multiple component states. Candidates should show how they choose fidelity for the audience, use prototyping features to simulate real interactions, test flows with users or stakeholders, and iterate based on feedback. This topic also covers how prototypes integrate with design systems, support handoff, and demonstrate thought processes for interaction design decisions and validation strategies.
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.
Information Architecture and Content Design
Organizing product content and user interfaces for clarity and discoverability. Topics include information hierarchies, navigation and routing, user flows and journey mapping, wireframing and low fidelity exploration, content organization and labeling, progressive disclosure, dashboard layout and KPI placement, filters and drill downs, and ideation and sketching techniques. Evaluates the ability to align structure with user mental models and to iterate designs based on evidence.
Technical Search Engine Optimization
Comprehensive coverage of technical search engine optimization for web products, including diagnosis, auditing, remediation, and ongoing monitoring of issues that affect crawling, indexing, and organic ranking. Core areas include crawlability and indexation, site architecture and URL structure, internal linking and XML sitemap hygiene, robots.txt and meta robots configuration, canonicalization strategies, redirect management including redirect chains and loops, server response codes and error handling, duplicate content detection and remediation, hreflang and internationalization, and crawl budget considerations. Performance and user experience topics include page speed optimization and Core Web Vitals such as Largest Contentful Paint, First Input Delay, and Cumulative Layout Shift, mobile usability and mobile first indexing, HTTPS implementation and mixed content resolution, structured data markup and schema validation, and techniques such as caching, content delivery networks, image optimization, critical CSS, deferred JavaScript, and server side rendering to improve performance. Candidates should be able to perform full technical audits, use and interpret results from industry tools and platforms, triage and prioritize findings by business impact and implementation effort, produce clear audit reports and remediation plans, translate findings into engineering action items, coordinate fixes with product and engineering teams, verify fixes through testing and monitoring, and establish ongoing site health monitoring and automation.
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.
State Management and Data Flow
Comprehensive coverage of strategies and patterns for managing application state and the flow of data in user interfaces and across system boundaries. Topics include local component state, derived state, and decisions about lifting state versus keeping it local; unidirectional data flow and event based updates; context providers and dependency injection for sharing state; and external state containers and libraries. Candidates should be able to explain criteria for selecting a solution based on application complexity, rendering performance, network characteristics, scalability, and team familiarity, and describe trade offs introduced by different libraries and architectures. Core engineering techniques include predictable state updates through immutability and pure update functions, minimizing duplicated and derived state, normalizing state shape, and designing for testability and debuggability. Synchronization concerns cover caching strategies and staleness models, when to refetch versus rely on cached data, optimistic and pessimistic update patterns and reconciliation, conflict resolution, and consistency across distributed front ends and server side systems. Also include considerations for rendering performance, concurrency, server side rendering, instrumentation, and debugging patterns used to reason about state in production.
Responsive and CSS Design
Focuses on building adaptable, maintainable user interfaces across devices and screen sizes using CSS and responsive design principles. Topics include mobile first and adaptive strategies, media queries, fluid and relative units, responsive images and picture sources, layout techniques using Flexbox and CSS Grid, responsive typography and spacing, component breakpoints and adaptive components, writing efficient and maintainable styles with methodologies like BEM or CSS in JS, CSS custom properties for theming, handling interactive states and accessible focus styles, performance considerations for layout and animations, and how responsive work intersects with accessibility (touch targets, readable text, focus management). Candidates should be ready to explain implementation details, trade offs, and examples of responsive patterns they used.
Responsive Design and Device Strategy
Covers designing user interfaces and front end architectures that adapt gracefully across a wide range of screen sizes and device types. Topics include breakpoint strategy, fluid and adaptive layout patterns, component adaptation rules, progressive enhancement, handling single column to multi column transitions, touch and pointer interactions, performance implications for mobile versus tablet and desktop, and accessibility considerations. At senior levels include how to scale responsive approaches across teams and products: design systems and component libraries that enforce responsive behavior, guidelines for consistency, testing strategies across form factors, build and release coordination, and measuring success through metrics such as perceived performance and device specific engagement.
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.