In the detailed review of my code I spoke a lot about how I balanced using React and Next.js best practices against less conventional and even old-fashioned low level coding techniques. I was asked how I might balance my "old school" ways of doing some things against the "new school" ways done by the dev team.
How do you handle performance with recurring network requests and results?
One question that stood out to me during the process was, “Are you satisfied?”
Went through a list of other es5 js questions
Why is a manhole circular in shape?
Implement a function `Car` that will result in the following output: var a = new Car(); var b = new Car(); console.log(a.id); // logs 1 console.log(b.id); // logs 2 b.id = 3; console.log(a.id); // still logs 1
Given an array of integers and a target integer, return two integers in the array that sum up to the target value.
First round : A problem with page structure was given. It was kind of a recursive problem and the idea was to show it the same way on the front end (Eg directory structure). The expectation here is to tell the interviewer your approach, ask clarifying questions before hand and keep the interviewer engaged in conversation. Try to list down error-handling scenarios. If you follow TDD you might get bonus point here. Round 2 : I was asked to implement a production-level feature toggle utility kind of function. I tried to did it in TDD way to some extent and show a working solution in react. Unfortunately, I clear this round. I am not clear on what was the expectation here, was it more of a library function like a package and not a solution demonstrated in a working project?
Take-home exercise related to front-end engineering
Write CSS/HTML to match provided design.
Viewing 361 - 370 interview questions