Microsoft SDE Intern Interview Experience
💼 LTIMindtree Interview Experience (On-Campus) | Fresher | 2026
Salesforce SMTS | Interview Experience | Rejected
JPMC | SDE2 (Associate) - Java Backend - Interview Experience + Compensation
Microsoft - SDE2 - Coding Round
Licious SDE2 Hiring 2025 experience
Summary
I interviewed for an SDE2 role at Licious, which involved an online test with Java MCQs and coding, followed by a machine coding round for Inventory Management APIs, and a system design round for a Coupon Management System.
Full Experience
I reached out to the recruiter directly on Linkedln and they reverted back after couple of weeks, asked for my current compensation and showed interest in proceeding forward with the online test & hence the interviews.
Round 1 Online Test : This round was almost 1 hr long, and was divided into multiple sections.
- Section 1 : 15 Mcq in 10mins on Java, with no navigation in between the questions. Mostly Java & Spring related questions were there.
- Section 2 : 2 questions in 20 mins. Both the questions were on the Easy level. But the caluse was, we had to code in Java and we couldn't select any other language for coding.
- Section 3 to 8 : The next 4/5 rounds were all puzzles. By puzzles, I mean the normal puzzle games that we play on our phone. In some we had to identify the puzzle and then solve it, in some it was all about how many questions you can solve in a 2min window. This was something which was new to me too, but was interesting.
Round 2 Machine Coding Round This round was also scheduled for 1 hour. After a brief introduction I was given a problem over a google doc, and had to write the code for the same. The expectation was clean, modular code, following Design patterns & OOP principles. Make sure you have a running IDE for this round. I was given a problem to implement two APIs for Inventory Management, and handle all necessary edge cases.
Round 3 System Design This was more of a HLD round. I was given a problem statement related to Coupon Management System. Then I was asked to share an overview of the components that will be involved in this system. And then the discussion was around the DB Schema design. There were multiple constraints like each coupon being applied to specific categories, or coupon can be applied to specific product or set of products, coupon could be handled only for a minimum cart value, for specific users etc.
The major expectation was how to design the Coupon or the CouponDetails table to handle all the 1 to 1 or 1 to many relationships in the DB schema.
Interview Questions (2)
Implement two APIs for Inventory Management, and handle all necessary edge cases. The expectation was clean, modular code, following Design patterns & OOP principles. Make sure you have a running IDE for this round.
Design a High-Level Design (HLD) for a Coupon Management System. Share an overview of the components that will be involved in this system. Then, discuss the DB Schema design. There were multiple constraints like each coupon being applied to specific categories, or a coupon can be applied to a specific product or set of products, a coupon could be handled only for a minimum cart value, for specific users etc. The major expectation was how to design the Coupon or the CouponDetails table to handle all the 1 to 1 or 1 to many relationships in the DB schema.