Interview experience
Freshworks Interview Questions
Overview
Section titled “Overview”Freshworks runs a compact 4-stage loop, but it leans closer to a product-company bar than a typical services-firm interview - medium-to-hard DSA, a real system-design round, and SaaS-specific scenario questions.
Freshworks interview process at a glance
Section titled “Freshworks interview process at a glance”| Round | Duration | What they test |
|---|---|---|
| Online Assessment | 90-120 min | 2-3 coding problems (DSA) |
| Technical Round 1 | 45-60 min | DSA + detailed project discussion |
| Technical Round 2 | 45-60 min | DSA / system design basics |
| Hiring Manager / HR | 30-45 min | Behavioural + team fit |
Online Assessment
Section titled “Online Assessment”A timed coding test with 2-3 DSA problems that run medium to hard rather than easy warm-ups - candidates report questions spanning array manipulation, tree traversal, and dynamic programming, usually on a proctored platform like HackerRank.
Common questions
- Array manipulation problems requiring an optimal (not brute-force) solution
- Tree traversal problems (level order, path-sum variants)
- A dynamic-programming problem under time pressure
- Edge-case handling is scored, not just the happy path
Technical Round 1
Section titled “Technical Round 1”A DSA round paired with a detailed walkthrough of your strongest project - interviewers expect you to justify data-structure choices and explain time/space complexity out loud, not just arrive at a working answer.
Common questions
- Find the longest increasing subsequence in an array
- Design a data structure for an LRU cache (HashMap + doubly linked list)
- Explain the time and space complexity of your solution
- Walk through the architecture and hardest bug in your most complex project
Technical Round 2
Section titled “Technical Round 2”DSA continues, but this round is where Freshworks’ SaaS product angle shows up most - expect a lightweight system-design prompt scoped to what a strong fresher can reason through, not enterprise-scale distributed systems.
Common questions
- Design a customer support ticketing system
- How would you design REST APIs for a SaaS product?
- Discuss database schema design and a caching strategy (e.g. Redis) for it
- Trade-offs between scalability, availability, and consistency for the scenario given
Hiring Manager / HR
Section titled “Hiring Manager / HR”A closing 30-45 minute conversation blending a managerial-style discussion (problem-solving, ambiguity, “why Freshworks”) with standard HR topics - compensation, joining date, relocation, and benefits.
Common questions
- Describe a time you solved a complex technical problem
- How do you handle conflicting priorities?
- Why Freshworks, and why a SaaS product company over a services firm?
- Tell me about a time you took ownership of a feature or problem beyond your assigned scope
Sample answer frameworks for each of these are on the Freshworks HR interview questions page.
Freshworks is a SaaS product company, not a staffing firm
Section titled “Freshworks is a SaaS product company, not a staffing firm”Unlike most large Indian IT employers, Freshworks builds and sells its own SaaS products (Freshdesk, Freshsales, Freshservice, Freshchat) rather than staffing engineers onto client projects. That shapes the interview in two ways: system-design prompts are framed around Freshworks’ own product domains (support ticketing, CRM workflows, multi-tenant SaaS architecture), and the HR round explicitly probes why you want a product company over a services firm - a generic “good brand name” answer lands worse than one tied to Freshworks’ actual products.
Frequently asked questions about Freshworks interviews
Section titled “Frequently asked questions about Freshworks interviews”What is the Freshworks interview process for freshers?
Freshworks interview process for SDE / Software Engineer typically includes: 1. Online Assessment (90-120 min): 2-3 coding problems (DSA), medium to hard difficulty. 2. Technical Round 1 (45-60 min): DSA plus a detailed project discussion. 3. Technical Round 2 (45-60 min): DSA and system design basics, often a SaaS-flavoured scenario like a ticketing system or multi-tenant API. 4. Hiring Manager / HR (30-45 min): Behavioural, team fit, and offer discussion. Timeline is usually 2-4 weeks from application to offer for campus drives.
What questions are asked in Freshworks interviews?
Freshworks interviews commonly cover medium-to-hard DSA (arrays, trees, dynamic programming, LRU cache design), core CS (OOPs, SQL), a deep project walkthrough, and SaaS-specific system design - multi-tenant architecture, REST API design, and CRM/support-ticketing workflows. Behavioural rounds check ownership, teamwork, and why Freshworks over a services company.
How many rounds are there in the Freshworks interview?
Freshworks typically has 4 stages: Online Assessment (90-120 min), Technical Round 1 (45-60 min), Technical Round 2 (45-60 min), Hiring Manager / HR (30-45 min). Some drives split the managerial and HR conversations into two separate short rounds instead of one. Check that cycle’s college placement email for the exact count.
Does Freshworks ask system design questions to freshers?
Yes, in Technical Round 2. It’s not full-blown distributed-systems design - expect SaaS-shaped prompts like designing a customer support ticketing system or REST APIs for a SaaS product, with follow-ups on database schema, caching, and scalability trade-offs at a level a strong fresher can reason through out loud.
How should I prepare for Freshworks interviews?
Practise timed medium-to-hard DSA (not just easy problems), revise OOPs and SQL, prepare one crisp project narrative you can defend in depth, and read up on SaaS multi-tenant architecture and REST API design since Freshworks builds and sells its own SaaS products rather than staffing client projects. Use STAR for behavioural answers.
Is Freshworks’ interview harder than a typical IT-services company interview?
Generally yes. Freshworks is a product company (Freshdesk, Freshsales, Freshservice) rather than a staffing/services firm, so its bar leans closer to a product-company loop: harder DSA, a real system-design round, and interviewers who probe project depth and design trade-offs rather than just checking syntax knowledge.