Slice | SSE | Bangalore | Jan 2025 | Reject

slice logo
slice
SDE IIBangalore
April 4, 20255 reads

Summary

I interviewed with Slice for an SSE role in Bangalore, which resulted in a rejection. The interview consisted of two rounds, focusing on concurrency and system design problems.

Full Experience

Round 1 -> Concurrency and multi-threading

Implement a concurrent in meomry feature flag system. where each feature might have a difference refresh interval. there might be diffrent sources for flags (all execlusive).

I followed clean architecture. stored feature flags in hash map. before returning check if the TTL is expired. then reload the flag. one more thing to think about here is performance due to granluar lock. Locking entire hashmap might not be efficient.

Round 2 -> Implement a payment execution platform like razorpay. Your service should not have latency higher than 5 secs.

Interview Questions (2)

Q1
Concurrent In-Memory Feature Flag System
Data Structures & Algorithms

Implement a concurrent in meomry feature flag system. where each feature might have a difference refresh interval. there might be diffrent sources for flags (all execlusive).

Q2
Design Payment Execution Platform (Razorpay-like)
System Design

Implement a payment execution platform like razorpay. Your service should not have latency higher than 5 secs.

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!