Got the offerSoftware Development Engineer (SDE) at Livspace
- Difficulty
- Process took
- 2-3 Weeks
- Rounds
- 6
- Format
- Hybrid
- Applied via
How it went
- Align your answers to the company’s domain and values,research Livspace’s business model and tech stack so you can tailor your responses.
- Be genuine in behavioral rounds. Share honest experiences about your growth, teamwork, and challenges, authenticity resonates more than rehearsed answers.
What they would tell you
- Align your answers to the company’s domain and values,research Livspace’s business model and tech stack so you can tailor your responses.
- Be genuine in behavioral rounds. Share honest experiences about your growth, teamwork, and challenges, authenticity resonates more than rehearsed answers.
How to prepare
- Revise key backend concepts like APIs, databases (especially NoSQL), and real-time communication protocols like WebSockets.
- Practice real-world DSA problems (not just basic DSA questions) that simulate actual business problems.
- Be ready to explain the “why” behind your decisions in every round, they value understanding and clarity.
Round by round
- 1
Initial Screening45 min
The first round was a conversation with a recruiter. We discussed my previous full-stack development experience, including backend knowledge and how I collaborate within teams. The recruiter also talked about the company’s tech stack and how teams work together. Key Questions
- “How would you design a real-time notification system for project updates?”
- “What experience do you have with microservices architecture?”
- “How do you handle conflicts within a team?” The discussion was light but focused on my past experience and how I would approach technical and collaborative challenges.
- 2
Technical Challenge120 min
For this round, I was tasked with building a simplified system that matches designers with customers based on their needs. The focus was on real-time features, scalability, and clean, documented code. It wasn’t just about the solution but also how well it was documented, the quality of error handling, and testing. Key Features:
- Matching logic based on designer expertise and customer needs
- API design with proper documentation and error handling
- Writing unit tests for critical components
- Implementing real-time updates via WebSocket (this wasn’t required but I added it to show initiative) I used Node.js for backend development and MongoDB for data storage. The extra effort on real-time updates showed that I went above and beyond.
- 3
System Design60 min
This round was focused on designing a platform that could track consultant performance across various client engagements. We discussed a lot of system-related topics, including scaling, performance, and how to handle large amounts of data efficiently. Discussion Points:
- CDN setup for fast data rendering
- Caching strategies like Redis/memcached
- Storage options for large assets (in this case, 3D designs)
- Load balancing to handle large volumes of requests
- Handling system failures and edge cases At one point, my internet connection dropped, turning it into an unplanned challenge that gave the interviewer a chance to test my ability to adapt under pressure. We discussed how to ensure system stability during such failures.
- 4
DSA + Problem Solving120 min
This round was really interesting because it focused on real-world coding challenges tied directly to Livspace’s platform. Instead of just textbook problems, the interviewer presented scenarios that could actually impact their business. Some key problems I worked on included optimizing a room-matching algorithm using dynamic programming, designing a price calculation system that had to handle multiple dependencies, efficiently retrieving reusable design templates, and detecting overlapping furniture placements in a room. The time was tight, but the problems were engaging and felt very relevant to the kind of work Livspace does, which made the round both challenging and exciting.
- 5
Cultural Fit45 min
In this round, I was given a scenario where I had to help design an internal cost tracking tool for a global consulting team. The product manager wanted real-time dashboards, and the CTO wanted the system to be lightweight without fancy infrastructure. Key Points Discussed:
- How to prioritize between real-time updates and accurate data
- Proposing a simple MVP roadmap to get started without over-engineering
- Navigating working with PMs who may frequently shift scope The interviewer was less interested in the technical details and more focused on my thought process, product collaboration skills, and how I would balance technical trade-offs.
- 6
Engineering Discussion30 min
This round was more relaxed and informal. The interviewer asked about my career goals, thoughts on the future of tech in design, and how I approach user experience. It was a good chance for me to connect my technical experience with future aspirations. Key Topics:
- Career aspirations and growth in tech
- Views on upcoming trends in commerce and design tech
- How I approach user experience and building intuitive products
- Work-life balance and remote work philosophies
What came up
A candidate-reported account, lightly edited. Interview processes change by team and date.