Search
Find a bite, explore a topic or look for a role.
Results for “React”
Bites 747
Accessibility pitfalls in SPAs and programmatic fixes
Cover route-change focus reset, ARIA live regions, semantic landmarks in dynamic markup, and keyboard trap prevention.
Describe the technical steps for displaying and enforcing a cookie consent banner.
Tests privacy-first frontend architecture. Outline: check consent record, render banner if absent, classify scripts as essential or non-essential, persist choice, and inject tracking only after explicit opt-in.
Design a CI/CD step to auto-lint application content
Rule types (terminology, placeholders, i18n), tools (TextLint, Vale, AST), and failure mode (block vs warn).
Describe how you'd implement an A/B test for a landing page headline
Mention deterministic bucketing, anti-flicker rendering, tracking with variant IDs, and sample-size planning.
Design architecture for multi-channel article distribution from a single source of truth
Tests separation of content and presentation via headless CMS. Strong answers cite a central structured CMS, content API, channel-specific rendering layers, and webhook push. Red flag: manual duplication or direct database sharing without API abstraction.
How would you automate forbidden-word checks in CI/CD?
This tests embedding brand governance into engineering workflows. A strong answer covers AST-aware string extraction, CI gating with severity levels, and allowlisting to cut false positives.
How would you design a centralized copy service for consistent UI text?
This tests separation of UI and content. A strong answer uses a key-value map with semantic IDs, a lookup hook, and context injection so components call copy.button.save. Red flag: raw strings in JSX or a database for static English-only copy.
CloudEvents: The Event Data Standard
CloudEvents provides a common envelope for event data, enabling routing without custom parsers. Use it when events cross clouds, SaaS tools, or internal services. It standardizes wrappers, not payloads, so producers and consumers still need aligned schemas.
Backstage: The Developer Portal Framework
Backstage is a framework for building a developer portal, not a ready-made dashboard. It centralizes ownership, docs, and tooling when microservice sprawl hides context. The footgun is treating it as a product you deploy without upkeep; the catalog rots.
End-to-End Testing: Simulate Real User Paths
End-to-end testing exercises the full stack through user flows, catching integration fractures unit tests miss. Run it in staging before releases to verify behavior. The trap is using it for fast feedback; it is slow, brittle, so never abandon unit tests.
Describe state hoisting and its benefits in Compose
Move state to the caller, pass value and event lambda down, keep them stateless.
Describe tracking a user event end-to-end from frontend to BI tool
Mention frontend instrumentation, routing, ingestion, warehouse transforms, and BI querying.
How do you track page views in a Single Page Application?
This tests SPA analytics beyond classic page loads. A strong answer covers History API pushState and popstate events, framework router hooks like useEffect or afterEach, and beaconing views. A red flag is relying only on window.load or polling URL changes.
What is your responsibility when frontend developers are overloaded?
Tests cross-functional accountability and shared Sprint Goal ownership. Strong answer: own the goal collectively; pair, test, or learn simpler frontend tasks; raise the blocker at the Daily Scrum.
How do you share a ViewModel between Fragments?
Tests your understanding of ViewModel lifecycle scoping beyond a single screen. To share, scope the ViewModel to the parent Activity or a navigation graph using activityViewModels() or navGraphViewModels().
Describe tracking a user event from frontend to BI tool
Tests your grasp of the modern data stack. A great answer outlines the five stages: frontend emission, ingestion, loading into a warehouse, transformation, and BI visualization. A red flag is describing only the frontend code and ignoring the data pipeline.
How do you track page views in a Single Page Application?
Tests your grasp of SPA navigation vs. traditional page loads. A great answer explains how SPA routers use the History API (pushState) and how to listen for changes to send analytics events. A red flag is suggesting polling the URL.
Explain the North Star Metric and propose one for a product
Tests your ability to connect user value to business outcomes. A great answer defines the NSM, proposes one for a product (e.g., Spotify), and justifies how it links customer value to business success. A red flag is picking a vanity metric like DAU or revenue.
How do you handle a PO adding work mid-sprint?
Tests your ability to protect the Sprint Goal via collaboration, not conflict. A good answer uses the Retrospective to discuss impact, proposes a 'one-in, one-out' policy for the Sprint Backlog, and involves the Scrum Master.
What's your responsibility when only frontend work remains?
This tests your commitment to collective ownership over individual tasks. A great answer prioritizes the Sprint Goal, offers to help overloaded frontend devs directly (e.g., testing, pairing), and avoids the red flag of starting future work before helping the…