Interview scorecard templates

Frontend Engineer interview scorecard template

Frontend interviews often test trivia and miss the work. This scorecard covers what shows up in the job: building interfaces, JavaScript fundamentals, accessibility, performance and working with designers, each with questions to ask and examples of a weak, solid and strong answer.

Customize this scorecard

Free to use. Nothing you type on the scorecard is saved.

Interview scorecard

Frontend Engineer

Score each skill from 1 to 5. A 1 is below the bar for this role, a 3 meets it, and a 5 is above it. The examples show what each sounds like. Use 2 and 4 for answers that fall in between.

UI implementation

Turns a design into working, responsive interface code that matches the intent and handles real-world states.

Score for UI implementation

Questions

  • Tell me about a UI you built from a design. How did you start?
  • Tell me about a time a design didn't fit real content or screen sizes. What did you do?
  • How do you structure and reuse interface pieces so they stay easy to change?

1: Below the bar

Describes copying a design pixel by pixel for one screen size. Ignores empty, loading or error states and reuse.

3: Meets the bar

Builds the main design with sensible structure and handles common screen sizes. Mentions some states, but reuse is partial or ad hoc.

5: Above the bar

Plans layout, states and reuse before coding, and tests on varied content and screens. Explains choices that kept the code easy to change.

JavaScript fundamentals

Explains how core JavaScript behaves and uses it to find and fix bugs in everyday code.

Score for JavaScript fundamentals

Questions

  • Tell me about a bug caused by how JavaScript works, such as scope or async. How did you find it?
  • How would you explain what happens when a promise is awaited inside a loop?
  • Tell me about a time you chose between callbacks, promises or async functions. Why that one?

1: Below the bar

Fixes bugs by trial and error. Can't explain scope, this, or async order without guessing.

3: Meets the bar

Explains scope, async and common gotchas correctly in their own words. Finds the cause of a bug with some trial and error.

5: Above the bar

Explains the underlying behavior precisely, such as the event loop, and predicts the bug's cause before testing. Names edge cases unprompted.

Accessibility

Builds interfaces that people using keyboards, screen readers or other assistive tools can use.

Score for Accessibility

Questions

  • Tell me about a time you found an accessibility problem in your own work. What did you do?
  • How do you check that a page works without a mouse?
  • Tell me about a time accessibility conflicted with a design or deadline. What happened?

1: Below the bar

Treats accessibility as an extra for later. Can't name a specific barrier or how they would test for it.

3: Meets the bar

Names common basics like alt text, labels and keyboard use. Tests with a keyboard or tool and fixes problems found.

5: Above the bar

Builds accessibility in from the start, tests with a screen reader, and persuades others to fix issues with clear user impact.

Performance

Finds and fixes what makes a web page slow, using measurements rather than guesses.

Score for Performance

Questions

  • Tell me about a time you made a page load or respond faster.
  • How do you find out what is slowing a page down?
  • Tell me about a time a fix did not help. What did you do next?

1: Below the bar

Guesses at causes or lists general tips. Cannot describe measuring before or after a change.

3: Meets the bar

Uses browser tools to find a cause and checks the fix worked. Explains one result in plain terms.

5: Above the bar

Measures first, picks the biggest cause, and checks the result. Weighs cost against gain and guards against it slowing again.

Working with designers

Turns design intent into working UI through early, honest conversation with designers about what is feasible.

Score for Working with designers

Questions

  • Tell me about a time a design was hard to build as drawn. What did you do?
  • Describe how you give designers feedback on work before and after you build it.
  • Tell me about a time you and a designer disagreed. How did it end?

1: Below the bar

Builds exactly what is drawn or quietly changes it. Blames the designer when things go wrong and raises concerns late.

3: Meets the bar

Raises build problems with the designer and suggests an alternative. Reaches an agreed outcome, though usually after the work has started.

5: Above the bar

Reviews designs early, explains trade-offs in the designer's terms, and agrees changes before building. Describes a better result for users.

Overall recommendation

Decide on your own, before you compare notes with the rest of the panel.

Overall recommendation

Use this scorecard in PontaHR

With PontaHR, your team fills out scorecards on the candidate's profile. Compare ratings and feedback side by side when it's time to decide.

See how scorecards work in PontaHR, then try it with a guided free trial.

More interview scorecard templates

Hiring for a different role? Make your own scorecard