SDE — BookMyShow Interview Experience

Overview

The candidate's interview process for the Software Development Engineer (SDE) - Frontend role at BookMyShow involved a multi-stage assessment designed to evaluate a wide range of skills. The process, sourced through getjobs.today, included initial screening, a coding challenge, technical deep dives, architectural design, product thinking, and a final culture fit assessment. BookMyShow sought a candidate capable of contributing to both existing products and future innovations.

Interview Rounds

Round 1: Initial Chat (30 minutes)

This initial screening, conducted by a talent scout, focused on the candidate's background and frontend development passion. Questions included:

• Optimization of a poorly performing web application: The candidate discussed optimizing a client-heavy web application through code splitting and lazy loading.
• Staying updated with frontend technologies: (No specific answer detailed).
• Isomorphic rendering: (No specific answer detailed).

Round 2: Code Challenge (3 hours)

The candidate completed a take-home coding challenge, building a React.js mini-application simulating event discovery and ticket booking. Requirements included:

• React.js with hooks for UI implementation.
• API integration for fetching event data.
• Search and filter functionality.
• Basic booking flow with seat selection.
• Responsive and accessible design.

Round 3: Technical Deep Dive (90 minutes)

Two senior frontend engineers examined the candidate's code and probed various technical areas. Questions included:

• Infinite scrolling implementation: (No specific answer detailed).
• State management for a complex booking flow: (No specific answer detailed).
• Offline capabilities: The candidate suggested service workers and IndexedDB, discussing the tradeoffs.
• Internationalization and localization: (No specific answer detailed).

Round 4: Architecture Challenge (60 minutes)

A principal engineer challenged the candidate to design the frontend architecture for BookMyShow's ticketing ecosystem. Key questions were:

• Monorepo structure for multiple frontend applications: (No specific answer detailed).
• Authentication and authorization across multiple frontend applications: (No specific answer detailed).
• Design system implementation for white-label partners: The candidate proposed CSS-in-JS with theming capabilities.