Tell me about a front-end technology you had to learn and apply to deliver a feature. Explain how you learned enough to make sound decisions, where you used it, how you verified the result, and what you would change after gaining more experience. ### Constraints & Assumptions - Name the technology and the user problem it helped solve. - Distinguish tutorial knowledge from evidence gained in the actual codebase. - Address maintainability and accessibility, not only visual output. ### Clarifying Questions to Ask - Was the technology already approved and supported in the project? - Which browsers, devices, input methods, and network conditions were in scope? - What existing component or design-system constraints applied? ### What a Strong Answer Covers - A focused learning plan using primary documentation, a small prototype, and feedback from experienced teammates. - A reasoned integration that fits existing patterns and controls bundle or dependency cost. - Verification of semantics, keyboard and screen-reader behavior, loading and error states, and automated tests. - Evidence from review, user testing, or production behavior. - Reflection on an early misconception or design choice revised with experience. ### Follow-up Questions - How would you verify the feature across phone, tablet, and desktop layouts? - What changes for touch, keyboard, screen readers, slow networks, and reduced-motion preferences? - When would you avoid adding the new technology?