Iphipi

Role: Full Stack Web Developer

College: Not Specified

Interview Date: July 5, 2023

Interview Type: Full-Time

Result: Pending/Not Specified

Difficulty: Hard

Rounds: 1 (long session)

Topics Asked: React (Virtual DOM, state, Redux, lazy loading, routing), .NET Core (middleware, SOLID principles, TAP, Web API, GAC, Garbage Collection), HTML5, CSS, System Design, Data Structures, Algorithms (palindrome substrings)

Experience:

This candidate had an interview for a Full Stack Web Developer position. The interviewer extensively covered a wide range of topics, including .NET Core, React, SQL Server, GIT, and Data Structures & Algorithms, all within a single, lengthy session.

The interview began with questions about **React**. The candidate was asked about passing data to components (props or state), the Virtual DOM (explained with an example), state management, Redux (provided a brief explanation despite limited experience), lazy loading, and routing in React.

The focus then shifted to **.NET Core**. The interviewer inquired about its features (cross-platform, open-source, self-contained applications) and middleware (concept and examples like routing, authentication, error handling, and logging). The interviewer expressed disappointment when the candidate couldn't recall all basic middleware components. Other .NET Core topics included SOLID principles, TAP (Task Asynchronous Programming), return types in .NET Core Web API, attribute routing, Global Assembly Cache (GAC), and Garbage Collection (Unmanaged and Managed code).

Brief questions on **HTML5 and CSS** were also part of the discussion.

The interviewer attempted to test **System Design** skills, but the candidate felt overwhelmed and admitted being unsure how to proceed.

For **Coding (Data Structures & Algorithms)**, the candidate was asked to write code for fetching data from a mock URL using React (the interviewer preferred class components, but the candidate used hooks and async, leading to disappointment). A specific coding problem involved finding palindrome substrings of even and odd lengths, counting them, and returning the counts in an array, which the candidate solved in about 15 minutes.

The interview lasted over an hour. Upon requesting feedback, the interviewer noted that most questions were answered correctly but expressed disappointment over slight pauses (up to 10 seconds) before responding to some questions and the inability to recall all basic middleware components.