Software Engineer
Interview Date
September 2025
Result
Cleared online assessment, overall result not expl
Difficulty
Medium
Rounds
At least 3 rounds (Online Assessment, DSA Round, Design Round, Project Discussion)
Drive Type
Full-Time
Topics asked
Detailed experience
College: Not Specified
Interview Date: September 2025
Interview Type: Full-Time
Result: Cleared online assessment, overall result not explicitly stated.
Difficulty: Medium
Rounds: At least 3 rounds (Online Assessment, DSA Round, Design Round, Project Discussion)
Topics Asked: Data Structures, Algorithms (DFS/BFS, Dynamic Programming), System Design (scalability, extensibility, abstractions), Project Discussion (architecture, trade-offs, challenges).
The interview experience started with an online assessment.
Online Assessment:
The assessment included coding problems. The candidate mentioned feeling nervous but got into a flow. They cleared this round.
DSA Round:
The first question was about connected components in a graph, which the candidate solved using DFS/BFS. The second question was a challenging Dynamic Programming problem involving 'l, r states and overlapping characters in a string'. The interviewer observed the candidate's thought process as they broke down the problem.
Design Round:
This round felt more like a conversation about system design, testing the ability to think in abstractions and design maintainable, scalable, and extensible systems.
Project Discussion Round:
The candidate discussed a personal project, explaining the idea, tech stack, architecture, and challenges faced. The interviewer asked follow-up questions like "Why this approach and not another?", "How would this scale with more users?", and "What trade-offs did you make?". This round was about reflecting on actual work done.
Takeaways:
The candidate advised preparing not just to solve problems but to explain the approach. In design rounds, focus on clean abstractions and real-world considerations like scalability and extensibility. For project discussions, know your work inside out—architecture, trade-offs, and challenges.