Attryb

Role: Full Stack Web Developer

College: Not Specified

Interview Date: July 5, 2023

Interview Type: Full-Time

Result: Rejected

Difficulty: Hard

Rounds: 1 round

Topics Asked: React, .NET Core, SQL Server, GIT, Data Structures & Algorithms, Virtual DOM, state, Redux, lazy loading, routing in React, middleware in .NET Core, SOLID principles, TAP (Task Asynchronous Programming), return types in .NET Core Web API, attribute routing, Global Assembly Cache (GAC), Garbage Collection (Unmanaged and Managed code)

Experience:

The candidate interviewed for a Full Stack Web Developer position. The interview started with questions on React. The interviewer asked about passing data to components (props, state), Virtual DOM, state management, Redux (candidate had limited experience but explained its purpose), lazy loading, and routing.

The focus then shifted to .NET Core, covering its features (cross-platform, open-source, self-contained applications) and middleware. The interviewer showed disappointment when the candidate couldn't recall all basic middleware components on the spot.

Further 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).

A coding question was given: "Write code for fetching data from a mock URL using React." The candidate used functional components with hooks, `axios`, and `async/await`. However, the interviewer reportedly expected class components and was disappointed by the candidate's approach.

The interviewer also asked a Data Structures and Algorithms (DSA) question, requiring code to be written.

Overall, the interviewer emphasized the need for immediate and spontaneous answers, and expressed disappointment when the candidate took a few seconds (at most 10 seconds) to think before responding to some questions. The experience was described as disheartening due to the interviewer's condescending demeanor and specific expectations regarding coding styles (e.g., class components over functional).