← Back to Directory

Flipster

Small

Screna has 3 Flipster interview write-ups. The most reported round is the system design round (2).

3 interview notes · updated Jun 2026

Flipster·Software Engineer·Technical Phone Screen

May 2026
Flipster coding round, pretty standard stuff. One algorithm question on stock prices and they wanted an optimal solution, not just something that works.
  • Given an array of daily stock prices, find the maximum profit from a single buy-then-sell transaction. Return 0 if no profit is achievable. They wanted O(n) time and O(1) space.

“I knew this one but still fumbled the explanation a bit.”

View Post

Flipster·Software Engineer·Onsite - System Design / Architecture

Apr 2026
Flipster system design round, focused entirely on a parking lot OOP problem that went way deeper than I expected. Thought it'd be a quick class diagram exercise but they kept pushing on concurrency, EVs, and reservations.
  • Design a parking lot system: walk through the class hierarchy (ParkingLot, Level, Spot, Vehicle types, Ticket), how spot types are assigned, and the full entry and exit flow including payment.
  • How would you handle concurrency when multiple entry and exit gates are operating simultaneously on the same parking lot?
  • How would you extend the design to support electric vehicle charging spots, and what changes would that require to your existing class structure?
  • How would you add a reservation system to the parking lot, where users can book a spot in advance?

“I jumped straight into the class diagram which felt right, but I fumbled the spot assignment policy for a few minutes.”

View Post

Flipster·Backend Engineer·Onsite - System Design / Architecture

Apr 2026
Flipster system design round, pretty deep dive into distributed ID generation. The kind of question that sounds straightforward until you're 20 minutes in and someone asks about clock rollback.
  • Design a service that generates unique 64-bit IDs at high throughput across multiple nodes. Cover the bit layout, collision avoidance, clock skew, sharding, sortability, and failure scenarios like clock rollback or duplicate machine IDs.

“I started with the Snowflake-style layout pretty confidently: timestamp in the high bits, machine/shard ID in the middle, sequence counter at the tail.”

View Post