super.money logo
Super.money· SDE 3

SDE 3 @ Super.money

Posted
3 Apr 2025
341 reads

Summary

I interviewed for an SDE 3 role at Super.money, which included rounds on machine coding, PSDS, LLD, and a hiring manager discussion, including a system design problem. I was ultimately rejected.

How it went

Round 1

Machine coding:

Design a logger library with different configurable destination options along with sync and async ways to write logs to the destination. It should support different log levels, buffer size for the async option, and formatting options. SOLID and OOD was expected, code should be running and testable. Handle everything in a multi-threaded environment.

Round 2

PSDS:

Discussion on reducing API latency using caching techniques. Discussion of general approach to take to address API latency issues.

Round 3

Supposed to be an LLD:

Design the leaderboard side of IPL fantasy league. T teams, 10M+ users, every user can build any team with 11 players, calculate per ball leaderboard based on fantasy points earned. Can assume we have a black box method to calculate per ball points, and we can query it to design our leaderboard.

Expectations: DB design, optimised queries, API flow, expected async handling of updating huge number of users’ score calc and updates.

Round 4

Hiring manager: Discussions on previous experiences.

Design a price drop alert system for a travel website. Users can select data range and the threshold price for a location, notify them when the price drops below the value. The website depends on the data from external sources like agoda, mmt, expedia etc.

Verdict

Rejected.

Questions asked (4)

  1. 01

    Design a Logger Library

    Other

    Design a logger library with different configurable destination options along with sync and async ways to write logs to the destination. It should support different log levels, buffer size for the async option, and formatting options. SOLID and OOD was expected, code should be running and testable. Handle everything in a multi-threaded environment.

  2. 02

    Reducing API Latency using Caching

    System Design

    Discussion on reducing API latency using caching techniques. Discussion of general approach to take to address API latency issues.

  3. 03

    Design IPL Fantasy League Leaderboard

    System Design · Hard

    Design the leaderboard side of IPL fantasy league. T teams, 10M+ users, every user can build any team with 11 players, calculate per ball leaderboard based on fantasy points earned. Can assume we have a black box method to calculate per ball points, and we can query it to design our leaderboard. Expectations: DB design, optimised queries, API flow, expected async handling of updating huge number of users’ score calc and updates.

  4. 04

    Design a Price Drop Alert System

    System Design

    Design a price drop alert system for a travel website. Users can select data range and the threshold price for a location, notify them when the price drops below the value. The website depends on the data from external sources like agoda, mmt, expedia etc.

Know someone preparing? Send it to them:WhatsAppLinkedInX

Interviewed at Super.money 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!