Sefism is free for learners. We are here to help you grow, one step at a time.Join for free
Sefism.
Product engineeringProduct company

Freshworks

Software company building customer service, IT service management and CRM products for businesses, with large engineering teams in India.

Not known5 stage process documentedFounded 2010
Headquarters

San Mateo, California, United States

Headcount

1,000 to 5,000

1,000 to 4,999 people
Work model

Not known

Hiring

Not known

Not enough signal to say. Check the careers page directly.
Where to apply

No careers page on file yet. Try their LinkedIn or the job boards below.

Website

Ask for a referral to Freshworks

A referral only means something if the person giving it can actually speak to your work. I will refer you where I know someone on the inside and your profile genuinely fits the role, and I will tell you plainly when I cannot. Either way you get an answer, and a straight one.

  • I read every request. A reply takes a few days, sometimes longer.
  • I will not refer someone for a role their profile does not fit. It wastes your time and costs me the contact.
  • Where I cannot refer you, I will say why, and point you at the way in that does work.
  • Nothing you send here is shared with anyone without you agreeing to it first.

If you found the opening, paste it. It tells me which team you mean.

A Drive, Dropbox or personal-site link is fine. Make sure it opens without a request for access, or I cannot read it.

At least a short paragraph. This is what I would be putting my name behind, so specifics beat adjectives.

Comma separated, up to six. Things you would be happy to be tested on.

How they hire

Campus drives and experienced hiring differ. Most accounts are from the Chennai office. Freshworks does not publish its engineering interview steps.

  1. 1

    Online coding test

    Reported +2
    Online test1.3 hoursRemote

    Campus and trainee candidates describe a HackerRank test of about four problems rising from easy to hard. Experienced candidates may start with a phone screen with shared code instead.

  2. 2

    Technical interviews

    Reported +2
    Technical interview

    One or two face to face rounds on data structures, SQL and database design, and the candidate’s projects.

    DSASQLProjects
  3. 3

    Design round (experienced hires)

    Unverified
    System design

    System design problems such as a photo sharing app with focus on database design and caching, plus an object oriented design like a parking lot.

    System designCaching
  4. 4

    Senior manager conversation

    Unverified
    Hiring manager

    A walk through of the most interesting project you have built and how you would improve its architecture.

  5. 5

    HR round

    Reported +1
    Final HR round

    Fit and location discussion. In some campus drives the HR questions are folded into the technical interview.

What comes up

Recurring themes from candidate accounts, not a question bank. Nobody is served by leaked question lists, least of all you in the interview.

  • Practical coding problems

    Reported +1

    Test problems are described as real world scenarios rather than puzzles, with a spread of difficulty.

  • Databases and SQL

    Reported

    Table design and SQL queries come up alongside linked lists and arrays in the technical rounds.

Worth reading before you apply

From the Sefism resource library, matched to the rounds above.

Roadmap
Coding Interview Playbook

A structured learning path through coding interview preparation that brings together data structures and algorithms fundamentals, recursion and the pattern-based approach to coding questions in one order. It totals 77 chapters and 1,054 lessons, with quizzes, flashcards and a certificate. Use it when you have plenty of material but no clear plan for what to study first.

  • Job search
  • DSA
  • Career
Design Gurus · Interview Prep · 3 to 6 months
SubscriptionDetails
Roadmap
FAANG Coding Interview Roadmap

A bundle of five company-specific question courses covering the problems most often reported from Meta, Microsoft, Amazon, Google and Oracle coding rounds, each split into easy, medium and hard sets with worked solutions. It suits candidates who already know the core patterns and have a loop booked at one of these companies, and want to rehearse on the questions those interviewers are known to ask.

  • Job search
  • DSA
  • Career
Design Gurus · Interview Prep · 3 to 4 months · Advanced
SubscriptionDetails
Roadmap
System Design Interview Playbook

A learning path that bundles five courses into one sequence for system design preparation: System Design Fundamentals, Grokking the System Design Interview, Advanced System Design Interview Volume II, Grokking Microservices Design Patterns and Grokking Design Patterns for Engineers and Managers. Together they add up to 76 chapters and 666 lessons. It suits engineers who want a complete, ordered curriculum instead of assembling one from scattered posts.

  • System design
  • Job search
  • Career
Design Gurus · System Design · 2 to 4 months
SubscriptionDetails
Guide
Design Gurus Newsletter

A free newsletter of short, focused posts on system design and problem solving, from the team behind the Grokking courses. Recent posts cover company interview processes (such as OpenAI and Anthropic roles), the most asked mobile system design questions and preparation plans, each linking to a fuller article on the blog. It suits engineers who want a steady, low-effort way to keep system design and interview topics fresh between deeper study sessions.

  • System design
  • DSA
Design Gurus · System Design
Cheat sheet
Sefism University to Job-Ready Cheat Sheet

The quick-revision companion to the University to job-ready roadmap: OOP, Git and engineering practice, data structures, DBMS, operating systems and networks, then projects, choosing a direction, getting experience and the hiring process. It has editions for first or second year, third year, and final year. Revise a chapter a week alongside your courses and before assessments.

  • Career
  • Job search
  • CS fundamentals
  • DSA
Sefism · Career Growth · Reference · Beginner
Guide
GeeksforGeeks

A very large site of articles on data structures, algorithms and core CS subjects such as operating systems, DBMS, computer networks and OOP, usually with code in several languages, plus practice problems and paid courses. It is handy for revising a university topic or finding a worked example of a specific algorithm. Quality varies because much is community written, so cross-check anything surprising against a textbook or official documentation.

  • DSA
  • CS fundamentals
  • Databases
GeeksforGeeks · Other · Ongoing reference
Browse the whole library

What it pays

Nothing collected for this company yet, and nothing worth guessing at. A made-up range is worse than no range because people negotiate against it.

Add to the Freshworks page

This library is only as good as what people who have been through it are willing to share. Most of these companies have no hiring process documented anywhere, and one account of what the rounds actually were is worth more than anything I can research from the outside.

What are you adding?

This decides how the claim is labelled on the page. Only someone representing the company can produce an “official” label, and I check that separately.

Year and month.

Comma separated topics, not the questions themselves.

Round by round is ideal: what each one was, how long, remote or in person, and what it covered.


Credit

Anonymous is the default. If you keep it anonymous, nothing identifying you reaches the page: it is published as a candidate account and your name stays with me. Never send anything covered by an NDA, and never send a take-home or a question paper.

Universities they recruit from

No sourced university links yet. A campus drive, a career fair appearance or an internship partnership is what puts a university here.

Add to the Freshworks page

This library is only as good as what people who have been through it are willing to share. Most of these companies have no hiring process documented anywhere, and one account of what the rounds actually were is worth more than anything I can research from the outside.

What are you adding?

This decides how the claim is labelled on the page. Only someone representing the company can produce an “official” label, and I check that separately.

Year and month.

Comma separated topics, not the questions themselves.

Round by round is ideal: what each one was, how long, remote or in person, and what it covered.


Credit

Anonymous is the default. If you keep it anonymous, nothing identifying you reaches the page: it is published as a candidate account and your name stays with me. Never send anything covered by an NDA, and never send a take-home or a question paper.

How to actually get seen

Freshers should be comfortable writing working code quickly and answering SQL and schema design questions. Experienced candidates should prepare one project to discuss in architectural depth.

Sources

Whole profile last checked 2026-09-22.

Interviewed at Freshworks? Fill in what changed.

Processes change, rounds get added, tests get replaced. If what you went through was different from what is on this page, tell me and I will update it.

Want me to refer you here?

Send me the role, your CV and a few honest paragraphs on why you fit it. Where I know someone inside and your profile matches, I will make the introduction. Where I cannot, I will tell you why and point you at the route that does work. You get an answer either way.

Ask for a referral to Freshworks

A referral only means something if the person giving it can actually speak to your work. I will refer you where I know someone on the inside and your profile genuinely fits the role, and I will tell you plainly when I cannot. Either way you get an answer, and a straight one.

  • I read every request. A reply takes a few days, sometimes longer.
  • I will not refer someone for a role their profile does not fit. It wastes your time and costs me the contact.
  • Where I cannot refer you, I will say why, and point you at the way in that does work.
  • Nothing you send here is shared with anyone without you agreeing to it first.

If you found the opening, paste it. It tells me which team you mean.

A Drive, Dropbox or personal-site link is fine. Make sure it opens without a request for access, or I cannot read it.

At least a short paragraph. This is what I would be putting my name behind, so specifics beat adjectives.

Comma separated, up to six. Things you would be happy to be tested on.

Add to the Freshworks page

This library is only as good as what people who have been through it are willing to share. Most of these companies have no hiring process documented anywhere, and one account of what the rounds actually were is worth more than anything I can research from the outside.

What are you adding?

This decides how the claim is labelled on the page. Only someone representing the company can produce an “official” label, and I check that separately.

Year and month.

Comma separated topics, not the questions themselves.

Round by round is ideal: what each one was, how long, remote or in person, and what it covered.


Credit

Anonymous is the default. If you keep it anonymous, nothing identifying you reaches the page: it is published as a candidate account and your name stays with me. Never send anything covered by an NDA, and never send a take-home or a question paper.

Work with me

Stuck on something specific?

Writing only gets you so far. If you want an answer to your situation rather than the general case, book a session and we will work through it together. Sessions are free for approved Sefism members, and a few slots open each week.