Slice Interview Experience | SDE 2
Summary
I interviewed for an SDE-2 role at Slice, passed the machine coding and system design rounds but was rejected during the hiring manager interview.
Full Experience
Slice SDE-2 Interview Experience | 3 Rounds | Rejected at HM Round
Sharing my recent interview experience with Slice for an SDE-2 role. Hopefully this helps someone preparing for similar rounds.
Round 1 - Machine Coding (~90 mins) ✅
Verdict: Positive
The problem was to build a working Wallet System.
Requirements included:
- Credit money to a wallet
- Debit money from a wallet
- Transfer money between users
- API to fetch wallet balance
- API to fetch user transactions
The focus was not just on writing code, but on building something that was reasonably production-ready and handling different scenarios.
Round 2 - HLD (~1 hour) ✅
Verdict: Positive
Designed a Ticket Booking System similar to BookMyShow.
The interviewer went fairly deep into:
- System architecture
- Database design
- API design
- Handling concurrent booking requests
- Preventing double booking
- Concurrency and race conditions
- Scalability and failure scenarios
This was probably the most grilling round of the process.
Round 3 - Hiring Manager (~1 hour) ❌
Verdict: Rejected
This round focused mainly on:
- Past project experience
- Deep dive into projects/responsibilities
- How I would scale/expand one of my projects
- General engineering and behavioral questions
- Situational/HR questions
Thanks to the interviewers for the discussions and the learning experience. Back to preparing and applying.
Hope this helps anyone preparing for Slice or similar SDE-2 interviews.
Interview Questions (2)
Wallet System Implementation
Build a working Wallet System with the following functionalities:
- Credit money to a wallet
- Debit money from a wallet
- Transfer money between users
- API to fetch wallet balance
- API to fetch user transactions
The solution should be production‑ready and handle various edge cases.
Ticket Booking System Design
Design a Ticket Booking System similar to BookMyShow. The design should cover:
- Overall system architecture
- Database schema and design
- API design for ticket booking and queries
- Handling concurrent booking requests and preventing double booking
- Concurrency and race condition handling
- Scalability considerations and failure scenarios