Licious Interview

This post details my recent experience interviewing for the Licious SDE-3 backend position.

Round 1: PS/DS

However, the question was based on low-level design.

Question: Let's assume you have a product and the product has some details like(name, brand, price, color, etc.). When the product is onboarded into the platform, it should go through a specific pipeline (creator, verifier, and approver),

Responsibilities

Creator: Create a product
Verifier: Can verify the product attribute or change the attribute.
Approver: The Approver can only approve or decline the product. They can't change any attribute of products.

And send a notification once the approver changes the verification state of the product.

Note: There might be more than one verifier and approver.

Hint: You can apply observer design patterns based on the product object verification state or you can apply a chain of responsibility design patterns to solve the problem.

Round 2: High and low-level design.

Question: Design Rate Limiter

Round 3: Hiring Manager Round
This round is all about technical knowledge. Deep dive into project high-level design and we discussed infra bottlenecks and one system design question.

How do you design a message broker system like Kafka?

Verdict: Hold due to recent layoff at Licious

Hope you enjoyed it! Your support matters. Feel free to like and share if you find it valuable.
Thanks for your time! 🙏