Slice (now operating with its North East Small Finance Bank licence) runs a fintech-flavoured SDE loop that mixes DSA with payments and credit domain reasoning.
Expect a coding round that leans on medium DSA (arrays, hashmaps, strings, trees) plus a machine-coding or low-level-design round where you build something like a transaction ledger or rate limiter cleanly. Interviewers probe how you reason about idempotency, retries, and reconciliation because Slice moves real money over UPI rails, so 'it compiles' is never the bar. The panel weights code quality, testability, and clear trade-off talk over raw problem count.
About Slice
Slice is a Bengaluru neo-bank that issued credit cards to young professionals and merged with North East Small Finance Bank (NESFB) in 2024 to become a licensed bank. Transitioning from fintech to regulated bank.
Resume screen: fintech or high-scale backend experience and referrals help visibility
Online or telephonic coding round: medium DSA, roughly 60 minutes
Machine coding or low-level design: build a small clean system in about 90 minutes
Technical deep-dive on past projects and system reasoning
Hiring manager and culture round: ownership, communication, and values fit
Coding Round (60 min)
1 to 2 medium DSA problems on arrays, strings, hashmaps, or trees. This is the primary filter.
Machine Coding or LLD (90 min)
Build a small working system such as a transaction ledger or rate limiter with clean OOP and edge-case handling.
Technical Deep-Dive (45 to 60 min)
Walk through a past project end to end and reason about idempotency, retries, and reconciliation under failure.
Hiring Manager and Culture (45 min)
Ownership stories, collaboration, and alignment with Slice's builder culture.
Sourced from 2+ candidate post-mortems. Hit Practice to answer any one with AI voice feedback.
2 more questions. Sign up to unlock all
Sign up free: unlock all questionsThe typical Slice recruitment process has 5 stages: Resume screen: fintech or high-scale backend experience and referrals help visibility → Online or telephonic coding round: medium DSA, roughly 60 minutes → Machine coding or low-level design: build a small clean system in about 90 minutes → Technical deep-dive on past projects and system reasoning → Hiring manager and culture round: ownership, communication, and values fit.
Slice typically conducts 4 interview rounds: Coding Round (60 min): 1 to 2 medium DSA problems on arrays, strings, hashmaps, or trees. This is the primary filter.; Machine Coding or LLD (90 min): Build a small working system such as a transaction ledger or rate limiter with clean OOP and edge-case handling.; Technical Deep-Dive (45 to 60 min): Walk through a past project end to end and reason about idempotency, retries, and reconciliation under failure.; Hiring Manager and Culture (45 min): Ownership stories, collaboration, and alignment with Slice's builder culture..
HireStepX recommends the Money-safe LLD framework for this type of interview: Model entities first, then idempotency and retry paths, then failure and reconciliation, then tests.
To answer this question well, HireStepX recommends the Money-safe LLD approach: Model entities first, then idempotency and retry paths, then failure and reconciliation, then tests. Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the Money-safe LLD approach: Model entities first, then idempotency and retry paths, then failure and reconciliation, then tests. Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the Money-safe LLD approach: Model entities first, then idempotency and retry paths, then failure and reconciliation, then tests. Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the Money-safe LLD approach: Model entities first, then idempotency and retry paths, then failure and reconciliation, then tests. Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the Money-safe LLD approach: Model entities first, then idempotency and retry paths, then failure and reconciliation, then tests. Ground your answer in a specific real example from your own experience.