Grow

Role: SDE Intern (Web)

College: Not Specified

Interview Date: Not Specified (Interview call received 2-3 days after assignment submission) [cite: 2]

Interview Type: Off-Campus, Internship [cite: 2]

Result: Selected [cite: 2]

Difficulty: Medium to Hard [cite: 2]

Rounds: Initial Screening, Assignment, Technical Interview, HR Round [cite: 2]

Topics Asked: HTML, CSS, JavaScript, ReactJS, APIs, Responsive Design, Error Handling, Local Storage, Debouncing, Throttling, Pagination, Hosting, WebSockets, TypeScript (discussion), Projects. [cite: 2]

Experience:

This off-campus opportunity was secured through an HR contact from a previous hackathon powered by Groww. After an initial resume screening, the candidate's profile was shortlisted by the Web team, leading to an assignment round. [cite: 2]

Assignment Round: The candidate was given 2 days to develop a website with features like API integration, responsive design, error handling, local storage, debouncing, throttling, pagination, and hosting. The assignment involved creating an online bank search application using a provided API. [cite: 2]

Technical Interview: This round was taken by two senior SDEs and lasted approximately 90 minutes. It began with introductions and casual conversation to make the candidate comfortable. The interviewers asked the candidate to rate themselves (on a scale of 5) in HTML, CSS, JS, and ReactJS. A significant portion (20-25 minutes) was spent on CSS, including questions like "Different ways to center a div." Other topics covered included: the difference between debouncing and throttling, the use of `useMemo` and `useCallback` hooks, and recommendations for using React Query for local storage. The interview was highly practical, requiring the candidate to code most of the time to explain concepts. The interviewers provided hints when the candidate was stuck. Towards the end, the candidate asked about Groww's handling of millions of WebSocket connections and their codebase shift from JavaScript to TypeScript. [cite: 2]

HR Round: Not explicitly detailed in the provided snippet, but implied to have occurred after the technical round, leading to selection. [cite: 2]