Senior Frontend Engineer

Why this interview

The plan we propose

Every question comes with the reason it was chosen. The interviewer can swap any of them before sending.

1. 1

   Search results for a query you already deleted

   Multiple choice · Advanced · ~4 min

   Why this question: The job is React-heavy and the résumé claims five years of it. Request races in effects are where that experience shows.

   Try it below
2. 2

   A settings toggle that does not re-render

   Multiple choice · Advanced · ~4 min

   Why this question: Checks the state-update mental model behind most "the UI did not update" bugs.

3. 3

   A product filter that freezes the page while typing

   Multiple choice · Advanced · ~4 min

   Why this question: The job requires frontend performance. Tests reasoning about the main thread instead of reaching for tools.

4. 4

   A modal that shows up behind the header

   Multiple choice · Advanced · ~4 min

   Why this question: Design system work means owning layout and layering. A common CSS bug that needs a real model, not trial and error.

   Try it below
5. 5

   An accessibility audit flags the checkout button

   Select all · Intermediate · ~3 min

   Why this question: The job requires accessibility. Semantic HTML is the most frequent audit finding.

6. 6

   A save test that fails one run in ten

   Multiple choice · Intermediate · ~3 min

   Why this question: The résumé claims Testing Library. Waiting correctly for async UI separates real use from familiarity.

7. 7

   A shared Button with twelve boolean props

   Multiple choice · Senior · ~5 min

   Why this question: A design system claim deserves a component API design question.

Try two of the questions

Answer as the candidate would. The interviewer guide beside each question is what the interviewer sees.

1function SearchResults({ query }: { query: string }) {
2  const [results, setResults] = useState<Result[]>([]);
3 
4  useEffect(() => {
5    fetch(`/api/search?q=${encodeURIComponent(query)}`)
6      .then(res => res.json())
7      .then(setResults);
8  }, [query]);
9 
10  return <ResultList items={results} />;
11}

1.site-header {
2  position: sticky;
3  top: 0;
4  z-index: 10;
5}
6 
7main {
8  position: relative;
9  z-index: 1;
10}
11 
12/* The modal is rendered inside <main>. */
13.modal {
14  position: fixed;
15  inset: 0;
16  z-index: 9999;
17}

See what the interview actually established

Built only from the interviewer's judgment on each question. The job and résumé decide what gets tested; they never count as evidence.