ixigo logo
ixigo· SDE 2 - Backend

Ixigo Inerview Experience | Round 1 | SDE 2 | Rejected

Posted
8 Apr 2026
228 reads

Summary

I interviewed for an SDE 2 backend role at Ixigo; the round covered system‑design and data‑migration questions and I was ultimately rejected.

How it went

Hi Leetcoders, you can read my interview experience with Ixigo for the role of SDE 2 - Backend.

One thing to note: HR has explicitly mentioned the first round would be DSA, but interviewer asked Redis and Kafka related production scenarios only.

Q1. Design a race-condition-safe user signup system

You need to design a signup flow where:

  • Phone number is mandatory and must be unique
  • Multiple concurrent requests for the same phone number can hit different servers/pods
  • System should not create duplicate users

Interviewer agreed solution: Redis atomic lock

Q2. Efficient Redis access with prefix

You have:

  • Millions of keys in Redis
  • Only a prefix of keys is known (e.g., lock_phone_xxxxxxxx)
  • Need to fetch ~5000 matching keys efficiently

Note: Avoid expensive operations like full scans or regex

Interviewer agreed solution: Redis Sorted Set

Q3. Data migration

System B uses multiple MySQL tables. System A uses a single Mongo collection. Migrate System B's data to System A

You need to:

  • Migrate existing (historical) data
  • Handle incoming live traffic simultaneously
  • Ensure no data loss or duplication
  • Maintain backward compatibility during migration

Interviewer agreed solution: Event stream DB logs using Debezium to Kafka topics, use Kafka idempotency to avoid duplicates.

Although I answered all the questions but not exactly what interviewer was looking for.

Result: Rejected

~Anonymous

Questions asked (3)

  1. 01

    Design a race-condition-safe user signup system

    System Design

    You need to design a signup flow where:

    • Phone number is mandatory and must be unique
    • Multiple concurrent requests for the same phone number can hit different servers/pods
    • System should not create duplicate users
  2. 02

    Efficient Redis access with prefix

    System Design

    You have millions of keys in Redis. Only a prefix of keys is known (e.g., lock_phone_xxxxxxxx). Need to fetch roughly 5,000 matching keys efficiently while avoiding expensive operations like full scans or regex.

  3. 03

    Data migration from MySQL tables to Mongo collection

    System Design

    System B uses multiple MySQL tables; System A uses a single Mongo collection. Migrate System B's data to System A while:

    • Migrating existing historical data
    • Handling incoming live traffic simultaneously
    • Ensuring no data loss or duplication
    • Maintaining backward compatibility during migration

Know someone preparing? Send it to them:WhatsAppLinkedInX

Interviewed at ixigo 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!