Tell me about a front-end project you are proud of. What made it challenging?

Note: Choose the project with the most interesting constraint, not the one with the most features. Constraints are what produce good interview stories.

Give it in four parts:

• The problem and who it was for. Keep it to one or two sentences and include scale — users, page views, or how much of the business ran through it.
• The constraint that made it hard. Strong options: a strict performance budget on slow mobile networks, an accessibility requirement, supporting an old browser the customer base still used, or a design system you had to build alongside the feature.
• A decision you made and the alternative you rejected. This is where interviewers judge seniority — say what you traded away.
• The measured outcome. Load time, conversion, bounce rate, support tickets, or Lighthouse score before and after.

Be honest about what you would change. Naming a weakness in your own work reads as confidence, not doubt.