Real, anonymous reports from people who interviewed for Software Engineer at Freshworks, newest first and distilled into what to expect across the loop.
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.
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 a design round, and even a bar-riser-style round that combined coding plus design. I stayed confident through those clears.
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.
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.
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.
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.
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.
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.