Gamesberry Labs | SDE - II

gamesberry labs logo
gamesberry labs
SDE - II3.5 yearsRejected
December 8, 202415 reads

Summary

I applied to Gamesberry Labs for an SDE - II role, successfully clearing the initial Coderpad round. However, I was ultimately rejected after a challenging Low-Level Design round focused on designing a SQL Database Engine, despite feeling confident in my performance.

Full Experience

I applied to Gamesberry Labs via Instahyre, and a recruiter reached out for a resume screening. My background includes 3.5 years of experience, a B.Tech from a Tier 1 IIT, and I'm currently working at a top product-based company, which led to my resume being shortlisted.

Round 1: Coderpad Round
This was an hour-long coding session on Coderpad, approximately 1 hour and 20 minutes, featuring problems that felt like a mix of LeetCode Medium to Hard difficulty. It was more challenging than I anticipated, but I managed to clear this round.

Round 2: Low-Level Design (LLD) Coding Round
This round lasted 1 hour and 30 minutes. The primary question involved designing a SQL Database Engine. Functional requirements were already provided, and my task was to develop an ER diagram and then implement the specified functionalities to create a working solution. I successfully drew the ER diagram using draw.io and implemented the code solution exactly as per my design. I also confidently answered all the questions asked by the interviewer regarding my implementation, and he appeared satisfied with my approach and solution.

I felt very positive about my performance in this round and was hopeful for the next stages, but unfortunately, I later received a rejection email. To be honest, I'm still unsure about the exact reason for the rejection, as I believed I performed quite well. Based on other interview experiences I've read about Gamesberry Labs, it seems there might be a pattern of the company not respecting candidates' time. I would advise caution when considering interviews with this company.

Interview Questions (1)

Q1
Design a SQL Database Engine
System Design

Design a SQL Database Engine. Functional requirements were provided, and I needed to create an Entity-Relationship (ER) diagram and then implement the specified functionalities to deliver a working solution.

Discussion (0)

Share your thoughts and ask questions

Join the Discussion

Sign in with Google to share your thoughts and ask questions

No comments yet

Be the first to share your thoughts and start the discussion!