spyneai logo
Spyneai· SDE 2

SpyneAi | SDE 2 | All Rounds | Gurugram

Location
Gurugram
Posted
17 Aug 2026
43 reads

Summary

I completed five interview rounds for an SDE 2 role at SpyneAi in Gurugram, covering behavioral questions, low‑level and high‑level design challenges.

How it went

Round 1: Initial Discussion (30 min)
Focus: Introduction and behavioral.
Details: I discussed my past experience, my current role, and the impact of my recent projects.

Round 2: Low‑Level Design (LLD) (60 min)
Topic: Design a Rate Limiter.
Details: I was asked to implement different rate‑limiting strategies, including a sliding‑window protocol, allowing an exact X number of requests, configuring the rate‑limit window (e.g., X requests allowed within the first 30 ms), and user‑based rate limiting.

Round 3: High‑Level Design (HLD) (60 min)
Topic: Design a Notification Microservice.
Details: I discussed an end‑to‑end architecture for scaling, handling failures, and managing multiple notification channels such as Email, SMS, and Push.

Round 4: Low‑Level Design (LLD) (60 min)
Topic: Design BookMyShow (BMS).
Details: The focus was on database schema and data modeling. I covered tables, indexes, relationships, and mapping between tables, including how to resolve concurrency issues during seat booking.

Round 5: High‑Level Design (HLD) (60 min)
Topic: Design an Image Processing Microservice.
Details: I described the architecture for uploading, processing (resizing, compressing, watermarking), and serving images at scale.

Key Takeaways & Observations
Cloud Focus: Across all rounds, the interviewers emphasized AWS and its ecosystem of services. I would recommend brushing up heavily on AWS architecture patterns.

Questions asked (4)

  1. 01

    Design a Rate Limiter

    System Design

    Design a rate limiter that supports multiple strategies: a sliding‑window protocol, allowing an exact X number of requests, configurable rate‑limit window (e.g., X requests allowed within the first 30 ms), and user‑based rate limiting.

  2. 02

    Design a Notification Microservice

    System Design

    Design a notification microservice capable of sending messages via Email, SMS, and Push. Discuss the end‑to‑end architecture, scaling considerations, failure handling, and integration points.

  3. 03

    Design BookMyShow

    System Design

    Design the core of a ticket‑booking system like BookMyShow, focusing on database schema, tables, indexes, relationships, and handling concurrency issues during seat booking.

  4. 04

    Design an Image Processing Microservice

    System Design

    Design an image‑processing microservice that handles uploading, resizing, compressing, watermarking, and serving images at large scale.

Know someone preparing? Send it to them:WhatsAppLinkedInX

Interviewed at Spyneai recently?

Write up your rounds while you still remember the questions. It helps the next person more than you would think.

Share your experience
Discussion 0

Questions for the author, or how your own interview compared.

Join the discussion

Sign in with Google to comment or ask the author a question.

No comments yet

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