10 curated questions
UI Engineering & Machine Coding
Practical interface implementation, machine-coding exercises, forms, and interaction design.
- 01intermediate · 10 min
How should a production form communicate validation errors?
Combine native constraints, server validation, field-level association, focus management, and accessible summaries.
- 02advanced · 12 min
How do you build a resilient file-upload experience?
Cover validation, progress, cancellation, retries, resumability, server verification, and duplicate submission.
- 03advanced · 15 min
How do you build reliable realtime UI over WebSockets or similar?
Connection state, reconnection, ordering, optimistic updates, and the UI contracts users need when the live link is imperfect.
- 04advanced · 13 min
How do you implement optimistic UI without corrupting client state?
Treat optimistic updates as speculative transactions with reconciliation, rollback, and concurrency rules.
- 05advanced · 15 min
How do you keep async UI consistent when requests race?
Debounce, abort, sequence tokens, and latest-wins rules so the UI never shows stale data or fights itself.
- 06advanced · 14 min
How do you manage focus across modals, drawers, and dynamic UI?
Focus traps, restoration, initial focus, and the practical rules that keep keyboard and screen-reader users from getting lost.
- 07advanced · 16 min
How do you model form state beyond controlled vs uncontrolled?
Dirty tracking, validation timing, server errors, progressive enhancement, and the state that actually matters in production forms.
- 08advanced · 14 min
How do you ship frontend features safely with flags?
Flags as a delivery mechanism, not just a boolean — targeting, cleanup, server vs client evaluation, and avoiding a permanent experiment mess.
- 09advanced · 18 min
How would you build an accessible, async autocomplete?
Implement a production-minded autocomplete with async results, keyboard navigation, race protection, and correct combobox semantics.
- 10advanced · 12 min
When is list virtualization worth the complexity?
Balance DOM size, layout/paint cost, scroll behavior, accessibility, and variable row heights.