Interview With Syfe(SDE3)

syfe logo
syfe
· SDE III
June 2, 2026 · 1 reads

Summary

I interviewed for an SDE3 role at Syfe, completing three rounds: an LLD design for a multiplayer Ludo game, an HLD for a news aggregator, and a project discussion with a high‑scale notification system design.

Full Experience

I was interviewed with Syfe sometime back. There were total 3 rounds

  1. LLD
  2. HLD
  3. Project Discussion + HLD

1. LLD - Multiplayer Ludo Game Design the core components of a turn‑based multiplayer board game system where:

  1. Players move tokens around a path on the board
  2. Game outcomes are influenced by both chance (dice rolls) and player decisions
  3. Multiple games can run concurrently on the platform
  4. The system needs to handle 2-4 players per game
  5. Players may disconnect and reconnect during gameplay

Expectations:

  1. Define the key entities and their relationships
  2. Design the core services and their responsibilities
  3. Explain how game state will be managed and persisted
  4. Detail the API contracts for critical game operations
  5. Address how concurrent games will be handled
  6. Explain your approach to handling player disconnections
  7. Describe how game events would be implemented
  8. Consider scalability aspects of your design
  9. Discuss how your solution could be extended for future features

2. HLD - News aggregator (Google News)

3. Project Discussion + HLD - Discussed past project and the HLD of that project. + Design a high‑scale notification system where millions of notification can be going at fix intervals

Interview Questions (3)

1.

Multiplayer Ludo Game (LLD)

System Design

Design the core components of a turn‑based multiplayer board game system where:

  • Players move tokens around a path on the board
  • Game outcomes are influenced by both chance (dice rolls) and player decisions
  • Multiple games can run concurrently on the platform
  • The system needs to handle 2-4 players per game
  • Players may disconnect and reconnect during gameplay

Expectations:

  • Define the key entities and their relationships
  • Design the core services and their responsibilities
  • Explain how game state will be managed and persisted
  • Detail the API contracts for critical game operations
  • Address how concurrent games will be handled
  • Explain your approach to handling player disconnections
  • Describe how game events would be implemented
  • Consider scalability aspects of your design
  • Discuss how your solution could be extended for future features
2.

News Aggregator (HLD)

System Design

Design a high‑level architecture for a news aggregation service similar to Google News, covering data collection, processing, storage, and delivery to end users.

3.

High‑Scale Notification System

System Design

Design a high‑scale notification system where millions of notifications can be sent at fixed intervals, addressing throughput, reliability, and scalability.

📣 Found this helpful? Please share it with friends who are preparing for interviews!

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!