
Freshdesk software engineer interviews, as five candidates describe them, center on DSA coding, with system design, test automation and manager or culture rounds for some roles. Reports range from 4 to 6 rounds.
$143K
Avg. Base Comp
$175K
Avg. Total Comp
4-6 rounds
Typical Rounds
Not reported
Process Length
Freshdesk software engineer interviews, as five candidates describe them, are built around data structures and algorithms, and the rest of the loop depends on the role. All five reports are for senior, SDET or lead SDET roles, so treat them as a guide to experienced engineering and test-engineering hiring.
The coding problems range from LeetCode medium to hard. Candidates mention arrays and strings, binary search (including binary search with backtracking), sliding window, trees, dynamic programming and permutations. Two candidates describe writing code on paper, and one was asked how long each problem would take. One candidate who received an offer describes a single full onsite day with five rounds: DSA, system design (a URL shortener), a bar raiser, a hiring manager and a culture round. That candidate found the interviewers friendly and willing to give hints.
SDET and lead candidates describe a different mix. They report Selenium waits, frames, XPath optimization, negative test cases for REST APIs and OTP generators, and OOP questions. Several candidates say interviewers seemed to expect one particular answer and did not engage much with alternative approaches. So practice stating the reason for your approach briefly, and be ready to match the expected pattern if the interviewer pushes back.
Outcomes were mixed. One candidate received an offer, one received an offer and declined it, and two got no offer. One cleared four rounds and was told they were selected, but was then scheduled for an extra VP round. Ask the recruiter to confirm each stage in writing. Candidates did not report a consistent end-to-end timeline.
Synthesized from 5 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Freshdesk process.
I applied through a recruiter connection at Freshdesk and was invited for an onsite interview that spanned the entire day. The process consisted of five rounds, and I walked in not knowing exactly what to expect, but the interviewers were genuinely friendly and helpful throughout, offering hints when I got stuck.
The first round was a DSA coding session where I tackled LeetCode-style problems, some of which were variations on questions Freshdesk actually uses in their own systems. This set the tone — technical, but not trying to trick me. The second round moved into system design. I was asked to design a URL shortener, which tested my ability to think about scalability, database design, and trade-offs. That round really separated candidates who could think architecturally from those who only know algorithms.
Round three was the bar raiser round, which felt like the most intense technical evaluation. Round four was with the hiring manager, where the conversation shifted toward my background, how I'd approach their codebase, and whether I'd actually fit into the team. By that point, I'd already been through enough technical gauntlet that this felt like a natural check-in. The final round was cultural fit, which was the most relaxed part of the day — they wanted to see if I'd mesh with the team's values.
What surprised me most was how well-calibrated the whole thing felt. There was no gotcha moment or ambush question. The difficulty ramped appropriately, and every interviewer seemed to know my background and what they were specifically testing for. By the end of the day, I had a clear sense of what the job would actually involve. I received an offer shortly after.
Prep tip from this candidate
Prepare for both algorithmic DSA problems and system design — practice designing scalable systems like URL shorteners and ride-sharing apps with emphasis on database design. Come ready to discuss trade-offs and architectural decisions, not just code syntax.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Freshdesk
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Top Three Salaries | |
| Empty Neighborhoods | |
| Merge Sorted Lists | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Top 3 Users | |
| Random SQL Sample | |
| Consecutive Day Orders | |
| Find the Missing Number | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Largest Salary by Department | |
| Size of Joins | |
| Scrambled Tickets | |
| Prime to N | |
| String Shift | |
| Duplicate Rows | |
| Find Bigrams | |
| Comments Histogram | |
| Last Transaction | |
| Longest Streak Users | |
| Raining in Seattle | |
| Minimum Change | |
| Customer Orders | |
| Bagging vs Boosting | |
| Payments Received | |
| Paired Products | |
| Get Top N Frequent Words | |
| Find the First Non-Repeating Character in a String |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report starting with data structures and algorithms. Topics named include arrays, strings, binary search with backtracking, sliding window, trees, dynamic programming and permutations. Some report writing on paper or pasting problems into a shared meeting link, with little discussion. Expect to start coding quickly and explain your logic as you go.
One senior candidate describes a system design round asking for a URL shortener, covering scalability, database design and trade-offs. Another senior candidate was asked to design a Netflix-like system. This round may not appear in every loop, but senior applicants should be ready to discuss architecture and trade-offs.
Candidates for SDET, lead SDET and one senior role report Selenium questions on waits, frames, versions and XPath optimization. They also report writing test cases, including negative API cases and scenarios like OTP generators or chatbots. Candidates typically describe these as separate from the pure coding round.
Two candidates report a bar raiser round. One senior candidate calls it the most intense technical evaluation of the day. One lead SDET candidate says it combined manual and automation questions, XPath optimization for large suites and harder programming challenges such as converting integers to Excel column letters.
The candidate who received an offer describes a hiring manager conversation about background, approach to the codebase and team fit, followed by a more relaxed cultural round. Another candidate describes a managerial round focused on role details and responsibilities. A behavioral discussion of experience was also reported elsewhere.
Outcomes differed by candidate: one offer, one declined offer, and two rejections. One rejection email arrived within a week of the interview. One candidate was told they were selected, then asked to do an extra VP round. Feedback was often limited, so confirm next steps with the recruiter.