Application / Frontend Engineer

Tell us how you build.

Short, specific answers beat long ones. Your draft is kept in this browser until you submit.

01 About you

Full name

Location and timezone

Hours per week you can give

GitHub or portfolio

LinkedIn optional

This is a paid role, but the budget is still being negotiated, so we cannot give you a number yet. Does that work for you?

Yes, I can start before the budget is set I need the number before I start Contact me once the budget is set

02 Your experience

What is your stack?

Languages, frameworks, state and data fetching, styling, testing, build tooling, accessibility tools. Mark what you have used in production.

How do you test the UI you ship?

Describe one frontend you shipped that people used every day.

What did it do, how did you know it worked for users, and what broke first?

03 How you would work here

A pull request produces 240 findings. The dashboard loads the full 8 MB JSON and freezes for four seconds on a mid-range laptop. How do you fix it?

Say what you measure before and after.

Finding explanations come from a language model. A resource tag in the plan contains <img src=x onerror=alert(1)>, and the explanation quotes it. How do you render explanations safely, and what may Markdown in them still do?

Name what you sanitize, where, and how you test it.

Findings load with useEffect(() => { fetch(url).then(r => r.json()).then(setFindings) }, [pr]). A user switches quickly from PR #12 to PR #13 and sometimes sees the findings of #12 under #13. Why?

React batches the state updates The #12 request resolves after #13 and overwrites it, so stale responses must be ignored or aborted The browser serves #12 from its cache The effect runs twice in development mode

04 Design problem

For most users the pull-request comment is the product. One change can produce findings of different severities, each with a grounded explanation, the affected resources and the plan diff.

The same data has to work as a GitHub Markdown comment (no scripts, at most 65,536 characters) and as a dashboard page. Text from plans and from the model is untrusted.

How would you build the review view?

Cover these points. If you think the brief is wrong in part, say so and explain why.

What a reviewer sees in the first five seconds
One data model for the comment and the dashboard
What happens when the comment would exceed the size limit
States: no findings, incomplete analysis, explanation withheld after failed validation
Accessibility and keyboard use
Rendering untrusted text from plans and from the model
What you would build in the first two weeks

0 words. Most good answers run 300 to 800.

Your answers are used only to review this application.

Tell us how you build.

Thank you.