Noon Frontend Engineer Interview Experience
Noon · Mid level
Illustrative example written by Top Tech Transition from typical interview processes, not a candidate's own account.
A practical loop: build a component live, then talk about performance on slow phones.
Interview process
Applied online. Recruiter call, live coding in React, frontend system design and a culture round.
Interview rounds · 4
- 1
Recruiter screen
Background and React experience.
- 2
Technical round
CodingLive React coding.
Q1. Build a product listing with infinite scroll and filters.
How they answeredUsed an intersection observer for loading more and kept filters in the URL.
Follow-up questions- How would you avoid re-rendering the whole list?
- 3
Final / onsite round
System DesignFrontend system design.
Q1. Design the product page so it loads fast on a slow 3G connection.
How they answeredServer rendering for the first view, image sizes per device, and lazy loading below the fold.
- 4
Final / onsite round
BehavioralCulture round.
Q1. Tell me about a time you disagreed with a technical decision.
How they answeredI used a migration where I pushed back on a big-bang cutover, proposed a dual-write phase with a kill switch, and showed the rollback plan. They cared most about how I brought the team along, not who was right.
Follow-up questions- What would you do differently now?
Tips from the candidate
Know web performance basics well: Core Web Vitals, image loading and server rendering.
Company culture
Product-focused frontend team.