Freshworks.
Customer and employee service software (Freshdesk, Freshservice, Freshchat, Freshsales) sold as multi-tenant SaaS.
its questions lean on
- class-level design on paper
- database choice and indexing
- caching
- multi-tenant SaaS
- chat and real-time messaging
- logging
The rounds, as candidates describe them
- DSA and design basicsIn-person hiring drive; DSA plus fundamentals such as database indexing and consistent hashing.source ↗
- LLDClass design on pen and paper (an on-call roster system), after a walk through the candidate's own work.source ↗
- Mixed DSA, LLD and fundamentalsTrie question, a file-management LLD with threading, CAP theorem and choosing between SQL, MongoDB and Cassandra.source ↗
- Hiring manager and HLDSketch your current system, then extend it with a distributed logging system.source ↗
- HR and culture fitFreshworks values and expectations; one candidate warns people are rejected at this stage.source ↗
Reported by candidates
From public interview write-ups; each links its source.- Design a URL ShortenerSystem designIP-01 · Design a URL Shortener →W01 · BOSS · Design a URL Shortener at Scale →reported in:GeeksforGeeks · Freshworks Interview Experience Onsite SE-1 (updated 2025) ↗
- Design a Chat SystemSystem designIP-08 · Design a Chat System →SQ-02 · WhatsApp Messaging →reported in:LeetCode Discuss · Freshworks SDE-2 Interview, Virtual (2025) ↗LeetCode Discuss · Freshworks SSE, Bangalore, Dec 2021 ↗
- Design a Logging SystemSystem designW10 · DAY 02 · Observability →W08 · DAY 01 · Event Ingestion at Scale →reported in:LeetCode Discuss · Freshworks Lead Software Engineer, Hyderabad (2024) ↗
- Design an Employee On-Call Roster System like PagerDuty (LLD)Low-level designno lesson for this one yetreported in:LeetCode Discuss · Freshworks Lead Software Engineer, Hyderabad (2024) ↗
- Design a File Management System (LLD)Low-level designW00 · PART 5 · Operating System Concepts for System Design →reported in:LeetCode Discuss · Freshworks Lead Software Engineer, Hyderabad (2024) ↗
- Design a Web CrawlerSystem designIP-05 · Design a Web Crawler →W03 · DAY 01 · Queue vs Stream →reported in:LeetCode Discuss · Freshworks SDE-2 Interview, Virtual (2025) ↗
- Design a Rate LimiterSystem designIP-02 · Design a Rate Limiter →W01 · DAY 03 · Rate Limiting at Scale →reported in:LeetCode Discuss · Freshworks Lead Engineer (2024) ↗
- Design a Ride-Hailing ServiceSystem designSQ-09 · Uber →IP-13 · Design a Proximity Service →reported in:LeetCode Discuss · Freshworks Lead Engineer (2024) ↗
- Design a Food Delivery SystemSystem designSQ-17 · Swiggy Food Delivery →W06 · BOSS · Food Delivery Order System →reported in:LeetCode Discuss · Freshworks SSE, Bangalore, July 2021 ↗
- Design a Parking LotLow-level designLLD-01 · Design a Parking Lot →reported in:GeeksforGeeks · Freshworks Interview Experience for Senior Software Developer (2019) ↗
- Design a Social Network like Instagram or FacebookSystem designIP-07 · Design a News Feed →SQ-21 · Instagram Feed and Stories →W04 · DAY 04 · Feed Caching →reported in:LeetCode Discuss · Freshworks Lead Software Engineer, Backend (2024) ↗GeeksforGeeks · Freshworks Interview Experience for Senior Software Developer (2019) ↗
- Design a Document-Sharing ApplicationSystem designIP-10 · Design a File Sync Service (Dropbox / Google Drive) →SQ-08 · AWS S3 →W09 · DAY 05 · Security Architecture →reported in:LeetCode Discuss · Freshworks Lead Software Engineer, Hyderabad, June 2024 ↗
- How does consistent hashing work?ConceptW01 · DAY 01 · Partitioning Deep-Dive →IP-03 · Design a Distributed Key-Value Store →reported in:LeetCode Discuss · Freshworks Lead Software Engineer, Hyderabad (2024) ↗
Likely, from what they build
Our pick, not a report: questions that fit Freshworks's products.- Design a Multi-Tenant Helpdesk Ticketing SystemSystem designW09 · BOSS · Design a Multi-Tenant Enterprise SaaS Platform →W09 · DAY 01 · Tenant Isolation Strategies →W09 · DAY 02 · Noisy Neighbor Prevention →
Study path
Every lesson the questions above point to, once, in order.
- 01IP-01Design a URL Shortener
- 02W01 · BOSSDesign a URL Shortener at Scale
- 03IP-08Design a Chat System
- 04SQ-02WhatsApp Messaging
- 05W10 · DAY 02Observability
- 06W08 · DAY 01Event Ingestion at Scale
- 07W00 · PART 5Operating System Concepts for System Design
- 08IP-05Design a Web Crawler
- 09W03 · DAY 01Queue vs Stream
- 10IP-02Design a Rate Limiter
- 11W01 · DAY 03Rate Limiting at Scale
- 12SQ-09Uber
- 13IP-13Design a Proximity Service
- 14SQ-17Swiggy Food Delivery
- 15W06 · BOSSFood Delivery Order System
- 16LLD-01Design a Parking Lot
- 17IP-07Design a News Feed
- 18SQ-21Instagram Feed and Stories
- 19W04 · DAY 04Feed Caching
- 20IP-10Design a File Sync Service (Dropbox / Google Drive)
- 21SQ-08AWS S3
- 22W09 · DAY 05Security Architecture
- 23W01 · DAY 01Partitioning Deep-Dive
- 24IP-03Design a Distributed Key-Value Store
- 25W09 · BOSSDesign a Multi-Tenant Enterprise SaaS Platform
- 26W09 · DAY 01Tenant Isolation Strategies
- 27W09 · DAY 02Noisy Neighbor Prevention
Company names and logos are trademarks of their owners, shown only to identify each company. This course isn't affiliated with or endorsed by any of them.