On the phone I was asked about Javascript closure, hoisting, and some problem solving/ algo question. In person I was asked to describe the output of given code, where there were timeouts and promises, how to implement debounce, and an algorithm question - finding LCA of two nodes - the nodes had reference to parent.
Asked about website security and performance improvement
LLD - browser.history implementation (pseudo code) HLD - survey tool (both survey creator and end user)
In the second interview they asked: 1. leet code 121 (Best Time to Buy and Sell Stock) 2. build a class that manages a tennis match score board and player winning.
How do you see your ideal career in the future?
The interview process was well-structured and covered a wide range of frontend topics, including React, TypeScript, performance optimization, testing, and CI/CD. Questions focused on team collaboration, handling complex projects, web performance, React rendering optimizations, and API efficiency. There were also in-depth discussions on JavaScript concepts like async/defer, blocking vs. non-blocking requests, and font loading issues. Additionally, algorithm and data structure questions were included, along with best practices for writing tests, reviewing merge requests, and maintaining code quality in large-scale projects. The process was challenging but insightful, assessing both technical depth and problem-solving skills.
- What is ShouldComponentUpdate? - What is a Fragment - What is HOC - What is a Component and PureComponent - What is Server Rendering - How to Prevent re-render - How to Pass information between child and parent components - How to Conversion steps of Class component to Hooks - How to use styles in components
How do you give bad feedback
Write a HTML rendering app. Find UI/UX/Accessibility/Perf/Security improvements to a given app
Build React app with a list of features
Viewing 651 - 660 interview questions