Real, anonymous reports from people who interviewed for Software Engineer at Freshworks, newest first and distilled into what to expect across the loop.
Get your personalized Freshworks Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
I got rejected after the very first technical screen for a Senior Software Engineer Backend role, which was entirely focused on data structures and algorithms. The interview felt like a quick, coding-heavy assessment rather than a broader discussion of my background.
They asked me to solve two classic LeetCode-style problems: “Remove Duplicates from Sorted Array II” and “Reverse Linked List II.” The expectation was that I’d write working code in the environment and then walk through my approach clearly.
7 months ago
Average Positive India
My process started with a more DSA-and-coding oriented round, and it quickly shifted into design. I felt the overall bar was moderate, but the structure still demanded solid fundamentals and clear thinking.
In the coding part, I worked through LeetCode-style problems and was also explicitly expected to cover time complexity when solving. The next stage was low-level design, where they mixed in some DSA and pushed me to reason carefully about implementation details. After that, the interview moved into higher-level design; one round in particular focused on designing a log system, with a higher-level engineer leading the conversation.
10 months ago
Average Negative India
I went through a longer sequence where I cleared multiple stages, and then the process fell apart late. Early on, I made it past a coding round, then …
11 months ago
Average Positive Bengaluru
My experience started with a process that was almost entirely senior-level thinking—two system design rounds and three leadership rounds, with VPs or …
11 months ago
Average Negative India
I went into the interview expecting something more robust, but it ended up feeling like a waste of time for me. The process was short—around 80 minute…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Technical Screen Focus
The initial technical screen is heavily focused on data structures and algorithms, often involving classic LeetCode-style problems. Candidates should be prepared to write code in real-time and discuss their thought process clearly.
Data StructuresAlgorithmsLeetCode
Design Rounds
Candidates can expect multiple design rounds that assess both low-level and high-level design skills, often requiring detailed reasoning about implementation and architecture. Be ready to discuss system design concepts and practical applications.
System DesignLow-Level DesignHigh-Level Design
Interview Structure & Flow
The interview process typically involves a structured multi-round format, often conducted in a single day with multiple interviewers. Candidates should be prepared for a fast-paced environment with little downtime between rounds.
Multi-RoundPacingStructured Process
Communication & Clarity
Candidates have noted varying levels of communication from HR and interviewers, with some experiencing confusion about role expectations and interview content. Clear communication about the process and feedback is crucial for a positive experience.
CommunicationRole ClarityFeedback
Behavioral & Cultural Fit
Some candidates experience rounds focused on behavioral questions and cultural fit, often involving discussions about past experiences and team dynamics. Prepare to articulate your values and how they align with the company's culture.
BehavioralCultural FitValues
Outcome & Feedback
Candidates often report a lack of constructive feedback after rejections, which can lead to frustration. It's important to seek clarity on performance and areas for improvement, even if feedback is not readily provided.