How Freshworks fresher interviews usually run, campus and off-campus. Patterns shift by year and role, so treat this as a prep map, not a script.
For fresher tech roles, Freshworks usually runs Online Assessment (90-120 min), Technical Round 1 (45-60 min), Technical Round 2 (45-60 min), Hiring Manager / HR (30-45 min). Campus and off-campus patterns differ slightly, trust the drive college placement email over older PDFs.
Round-wise process
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
Real interview experiences
Stories below mix campus-style four-round loops with a published GeeksforGeeks SE-1 onsite account. Teams, stacks, and round counts change by year - use the table above plus your placement email as source of truth.
Technical interview experience 1
Candidate Profile: Final year CS student from tier-1 college, 8.2 CGPA, strong DSA background
“Describe a time you solved a complex technical problem”
“How do you handle conflicting priorities?”
“Why Freshworks?”
My Approach:
Used STAR format for behavioral questions
Emphasized alignment with Freshworks’ mission
Showed enthusiasm for SaaS technology
Result: Cleared, advanced to HR round
Round 5 - HR Interview (30 minutes)
Interviewer: HR Manager
Topics:
Personal background and education
Compensation discussion (₹24 LPA offered)
Joining date and relocation
Benefits and stock options
Result: Received offer letter within 2 days
Key Takeaways: Strong DSA preparation is essential. System design knowledge helped in round 3. Behavioral preparation using STAR format was crucial. Communication and problem-solving approach matter as much as correct solutions.
Takeaways
What decided it: Clearing medium-hard OA DSA, then progressive technical depth into design, plus STAR behavioural readiness for HR
Common fail: Correct algorithms without edge-case narration, or blanking on system-design basics in round 3
How to practise: Timed 3-problem OAs; tree/DP drills with dry-runs; one URL-shortener style design sketch; 3 STAR stories
Candidate profile: Experienced hire / SE-1 track. Process from public write-up: telephonic role overview, then Saturday onsite with three technical panels plus HR call; offer letter three days after HR.
Telephonic screen
One-on-one on current and previous work plus role expectations
Outcome: invited to onsite the following Saturday
Onsite 1 - DSA (1-2 interviewers)
Maximum-sum square submatrix - candidate used Kadane with optimizations
Linked-list reversal (described as straightforward)
Result: Advanced
Onsite 2 - DSA + OS/DBMS
Thrashing and how OS handles it; memory management techniques
Atomicity and consistency (transaction concepts)
More DSA practice from same day
Result: Advanced
Onsite 3 - Design + coding
Design TinyURL with constraints; follow-ups on distributed deployment, caching, improving DB queries
Rat maze / minimum steps to reach goal (grid BFS/DFS family)
Result: Advanced to HR
HR call
Standard behavioural and background questions
Final result: Offer (~3 days later in the report; compensation not disclosed in the public post - confirm on your letter)
Key takeaways: Author recommends drilling Amazon/Microsoft-style GFG archives for DSA and using structured design prep (Educative-style URL shortener material cited in the post) for the design panel. OS/DBMS fundamentals still appear even when the role is software-heavy.
Takeaways
What decided it: Surviving onsite SE-1 panels that mix DSA with OS/DBMS and a structured design round
Common fail: Treating Freshworks as DSA-only and skipping OS/DBMS fundamentals or design prep
How to practise: GFG Amazon/Microsoft-style archives; Educative-style URL shortener notes; flashcard OS/DBMS
Questions that come up often
Coding / technical
Longest substring without repeating characters. Usually expects sliding window + hashmap
Binary tree level order traversal. Usually expects BFS
Detect cycle in a directed graph. Usually expects DFS colouring / topological sort
Discussion on SaaS multi-tenant and REST APIs, bottlenecks, failure modes, simple APIs
Detailed project discussion, architecture, hardest bug, what you would change
HR / behavioural
Why this company?
A disagreement with a teammate and how you handled it
An ownership example from a project
Relocation preference
Dense prep checklist
OA: Two to three medium/hard problems in ~90 minutes - finish two cleanly before chasing a third partial
Tech 1: One project deep-dive you can defend (architecture, hardest bug, what you would refactor)
Tech 2 / design: Clarify tenants, QPS, and consistency before boxes; tie answers to Freshdesk-style workflows when possible
OS/DBMS: Thrashing, ACID, indexing - still reported on onsite loops alongside DSA
Managerial/HR: Four STAR stories - conflict, failure, ownership, conflicting priorities - each with a number
Relocation: Decide Chennai vs Bengaluru and notice-period answers before the call
Practical tips for Freshworks
Clear the screening round first. Timed practice beats last-minute topic hopping.
For domain questions, explain SaaS multi-tenant in plain language, inputs, outputs, what breaks at scale.
OOPs and SQL still open a lot of Freshworks panels. Do not skip fundamentals.
HR answers should be concrete. One story with a result beats five slogans.
If you do not know something, say so and outline how you would find out.
HR interview
After technical rounds, Freshworks usually closes with a short HR / hiring-manager conversation: motivation, location, notice period, and a couple of behavioural stories. Prepare those answers on the dedicated page rather than cramming them into this hub.
Sample answers for high-frequency questions
Use these as frames, not scripts - interviewers probe follow-ups.
Q. How do you design an LRU cache with O(1) get and put? A. Combine a hash map with a doubly linked list. The hash map stores key to node pointer for O(1) lookup, and the doubly linked list keeps entries in recency order with the most recently used at the head and the least recently used at the tail. On get, find the node through the map and move it to the head. On put, insert at the head, and if capacity is exceeded, evict the tail node and remove its key from the map. A doubly linked list is essential because unlinking a node in O(1) needs its previous pointer, which a singly linked list does not have. Sentinel head and tail nodes eliminate most null checks, and Java’s LinkedHashMap with accessOrder set to true is the built-in equivalent.
Q. How do you find the longest increasing subsequence in an array? A. The classic dynamic-programming solution defines dp[i] as the length of the longest increasing subsequence ending at index i, computed by scanning every earlier index j whose value is smaller and taking the best dp[j] plus one; the answer is the maximum over all dp entries, at O(n^2) time and O(n) space. The optimal solution is O(n log n): maintain an array tails where tails[k] holds the smallest possible tail value of an increasing subsequence of length k plus one, and for each element binary-search for the first tail greater than or equal to it, replacing it, or appending when none exists. The length of tails is the answer - but tails itself is not a valid subsequence, so reconstructing the actual sequence requires storing predecessor indices.
Q. How would you design a customer support ticketing system? A. Start with entities: tickets, customers, agents, teams, comments, attachments and SLA policies, with a ticket carrying status, priority, requester, assignee and timestamps. The core flows are ticket creation from multiple channels such as email, web form and chat, routing to an agent by round robin or skill-based rules, and status transitions modelled as an explicit state machine. Reads dominate writes, so index on assignee and status for agent queues, use a search engine such as Elasticsearch for full-text ticket search rather than a LIKE query, and cache agent dashboards. SLA breach detection is best handled by a scheduled job or delayed queue message rather than polling every ticket, and notifications and attachment processing go through an async queue so ticket creation stays fast.
Q. What is multi-tenant architecture, and what are the isolation options? A. Multi-tenancy means one application instance serves many customer organisations while keeping their data separate. There are three common models. A separate database per tenant gives the strongest isolation and easiest per-tenant backup or restore, but costs the most and makes schema migrations across thousands of tenants painful. A shared database with a schema per tenant is the middle ground. A shared schema with a tenant_id column on every table is cheapest and most scalable and is what most SaaS products use, but every query must filter by tenant_id - one missing filter is a cross-customer data leak, which is why it is enforced at the ORM or row-level-security layer rather than left to individual queries. Large tenants are often moved onto dedicated infrastructure so one noisy customer cannot degrade the rest.
Q. What makes a REST API well designed? A. Model resources as nouns and let HTTP methods carry the verbs, so GET /tickets/123 and POST /tickets rather than GET /getTicket. Respect the semantics: GET is safe and cacheable, PUT is idempotent and replaces the whole resource, PATCH updates part of it, and DELETE is idempotent even though a second call returns 404. Use real status codes - 201 with a Location header on creation, 400 for a malformed request, 401 versus 403 for unauthenticated versus unauthorised, 409 for a conflict, 429 for rate limiting. Version the API in the path or a header so it can evolve without breaking clients, paginate every collection with cursor-based paging rather than offsets on large tables, and return structured error bodies with a stable machine-readable code.
Tips from successful candidates
Assessment tips
Confirm the current Freshworks pattern from the drive mail before practising old papers
Finish one problem or section fully before starting the next
Revise the fundamentals listed in the round table on this page
Interview tips
Narrate trade-offs; expect “why” after every answer
Only list projects you can defend under follow-ups
Prepare 3-4 STAR stories for behavioural prompts
HR tips
Know why Freshworks, not just why the industry
Be clear on location / notice period / higher studies
These links are research inputs used to map Freshworks OA and onsite SE-1 panels - not copied page mirrors. We reorganized reports into process tables, outcome notes, and prep takeaways.
