Company OAsDSA SheetAll ProblemsPlacement DataInterview ExperiencesPremium
OAHelper

Built by students, for students — practice company-specific OAs, DSA sheets, and real interview experiences to land your dream role.

© 2026 OAHelper.in·Terms·Privacy·Refunds·Trust & Safety·Contact·
Ready to crack your next OA?

Practice company-specific questions trusted by thousands of students across India.

Start PracticingGo Premium
OA Practice·DSA·Placements

Disclaimer: OAHelper is an independent educational platform. We (oahelper.in) do not own the images or questions shown. Content is uploaded by users.

D

Databricks

Full Stack Engineer (L4)

Interview Date

—

Result

Rejected

Difficulty

Hard

Rounds

5 rounds

Drive Type

Full-Time

Topics asked

Past experienceproject challengesData StructuresAlgorithms (game-related matrix question)Full-Stack Development (ReactJSNextJSGolangcomponent structurestate managementevent handlersUI renderingform validationroutingAPI request handlingdata structures)High-Level Design (HLD)Behavioral.

Detailed experience

Role: Full Stack Engineer (L4)

College: Not Specified

Interview Date: Not Specified

Interview Type: Full-Time

Result: Rejected

Difficulty: Hard

Rounds: 5 rounds

Topics Asked: Past experience, project challenges, Data Structures, Algorithms (game-related matrix question), Full-Stack Development (ReactJS, NextJS, Golang, component structure, state management, event handlers, UI rendering, form validation, routing, API request handling, data structures), High-Level Design (HLD), Behavioral.

Experience:

This candidate shared a "horrific" interview experience for a Full Stack Engineer L4 role. The process involved five rounds: Hiring Manager, DSA, Pair Programming, HLD, and Behavioral.

The **Hiring Manager** round (30-45 mins) was a typical discussion about past experiences and project challenges, which the candidate cleared.

The **DSA Round** (45 mins) was described as frustrating. The interviewer, based in the U.S., asked a game-related question involving a matrix to check winning conditions. The candidate quickly understood the question and started coding, but the interviewer unexpectedly asked to run the unfinished code. After adjustments for a basic condition, the interviewer insisted on a specific matrix format, and later interrupted the coding process to demand an explanation with only 10 minutes left. Despite finishing the code, a minor bug due to the interruption was pointed out, and the interviewer ended the interview without allowing debugging time.

The recruiter informed the candidate two days later that the DSA round did not go well. The candidate noted that the interviewer was rude and strict, suggesting that older interviewers (10+ years experience) might be less open to conversation.

Submitted anonymously12 NOVEMBER 2025