Portfolio ↗

Quiz

2707 questions of the kind that actually get asked — in interviews, in architecture review boards, and by the person who has to run the thing at 3 AM. Every answer states the trade-off rather than the slogan, and says when the obvious choice is the wrong one.

All areas2707 Architecture Fundamentals81 Distributed Systems101 Data Architecture90 Cloud Architecture87 Networking86 API & Integration Architecture78 Reliability & Resilience88 Observability81 Performance & Capacity Engineering90 Security Architecture95 Cost Architecture & FinOps92 Business Architecture93 Architecture Communication91 Enterprise Architecture91 Legacy Modernization92 AI-Era Architecture96 Software Architecture & Engineering84 Architecture Patterns84 Architecture Decision-Making91 The Architect's Meta-Skills92 Delivery & Release Engineering93 Platform Engineering & Developer Experience92 Testing & Quality Architecture90 Data Platform Architecture98 Streaming & Real-Time Data93 Data Governance & Semantics91 Frontend & Experience Architecture91 Edge, Mobile & IoT88 Regulatory & Data Protection Architecture90 Assurance, Audit & Model Risk98
Difficulty Any beginner intermediate advanced

91 questions in Frontend & Experience Architecture.

  1. Client State Architecture advanced

    A front-end team wants to replace their global state library because "state management is unmanageable". How do you evaluate the request?

    2 min answer frontendstatearchitecturerefactoring
  2. Client State Architecture advanced

    An application keeps significant state on the client and synchronises with a server. What are the architectural decisions?

    2 min answer linearlocal-firstsyncconflicts
  3. Client State Architecture advanced

    Design client state for a document application supporting offline editing, real-time collaboration and instant navigation.

    1 min answer client-stateofflinesynccaching
  4. Client State Architecture intermediate Multiple choice

    What is the difference between server state and client state, and why does conflating them cause bugs?

    2 min answer statecachingsynchronisationurl-state
  5. Component Contracts intermediate

    A design system releases 4.3.0. The changelog says no breaking changes. Eleven of forty consuming applications report broken layouts. Review the versioning policy - what is wrong with it?

    3 min answer design-systemscomponent-contractssemverimplicit-coupling
  6. Component Contracts advanced

    A platform team's design system ships connected components - an avatar that fetches the user from its id, a price tag that calls the pricing service from a sku, and a notification bell that opens its own WebSocket. Forty applications consume it. The package is 180 KB compressed and the bell is in the shared header on every page. Review this. What would you remove, what would you keep, and what would you leave alone even though it looks wrong?

    2 min answer design-systemcomponent-contractscouplingwaterfall
  7. Component Contracts intermediate

    A team asks for a new prop on a shared component. When do you say no, and what do you offer instead?

    2 min answer design-systemapi-surfacecompositioncontracts
  8. Component Contracts intermediate

    What makes a shared component's interface stable enough that consumers can upgrade without breakage?

    1 min answer component-apicontractsversioningcomposition
  9. Core Web Vitals intermediate

    A commerce platform's field performance metrics are poor. Which improvements have the largest effect on conversion?

    2 min answer nykaaweb-vitalsfield-dataconversion
  10. Core Web Vitals advanced

    A commerce site's layout shift metric worsens sharply after a release and the team cannot reproduce it locally. How do you find it?

    1 min answer core-web-vitalsclsrumdebugging
  11. Core Web Vitals intermediate

    A single-page application scores well in the lab and users on mid-range Android phones say it is unusable. Diagnose.

    2 min answer performancefrontendmeasurement
  12. Core Web Vitals intermediate

    Mobile conversion is 40% below desktop. Product blames the design; analytics shows users leaving before the page is usable. How do you investigate?

    2 min answer performancefrontendfield-dataconversion