Academic snapshot
Marks: 70% or 7.0+ CGPA throughout 10th, 12th, graduation (candidate-reported)
Degree: B.E./B.Tech/M.E./M.Tech/MCA
Backlogs: None active
Year: Final-year and recent grads (often within 1 year)
Freshworks Placement Papers 2026
Freshworks is a global SaaS company known for products like Freshdesk, Freshservice, and Freshsales that help businesses manage customer support and sales. Founded in 2010 and listed on NASDAQ, it maintains strong engineering roots in Chennai and hires across India for product development roles.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
Freshworks fresher eligibility for campus drives
Freshworks is a product SaaS hirer. The academic floor is higher than mass IT GET; the OA is DSA, not 40 quant MCQs.
Who this hub is for
- For: CS/IT/ECE (and related) students targeting Software Engineer / SE-1 in Chennai or Bengaluru via campus, careers, hackathons, or referral.
- Not the same track: Support-only, sales, or services GET papers. Those bars do not map to this OA → DSA → design-lite loop.
- Experienced hires: Mid-level loops add deeper LLD. Use fresher sections as a base, then read senior notes separately.
On-campus vs off-campus
| Route | What usually changes | What stays the same |
|---|---|---|
| Campus | Batch OA window, college CGPA list | DSA bar, interview depth |
| Careers / referral | Resume screen volume | Still expect 2-3 coding problems |
| Hackathon / contest | Visibility | You still defend code and a project |
Off-campus does not mean easier graphs. It often means more applicants fighting the same 90-minute filter.
Degree, 7.0, and “is 70% enough?”
Is 7.0 CGPA enough? It matches the commonly reported floor across 10th, 12th, and graduation. Selection still hinges on OA correctness and interview narration. A 7.2 with clean timed coding beats a 9.1 that freezes on edge cases.
Branches: CS/IT/ECE dominate. Related streams show up when DSA is solid. If the college lists only certain branches, read the notice.
Gaps and backlogs: Active backlogs are a hard blocker. Max about 1 year gap is the usual table (tighter than many services firms).
What helps the resume screen: One project you can defend end-to-end, any internship with ownership language. See certifications after DSA, not instead of it.
Skills they actually filter
OA: 2-3 medium DSA problems
Interviews: Live coding + project + SaaS-lite design
Languages: Python, Java, JavaScript, Go
Differentiator: Ticket/CRM product sense
Detailed eligibility criteria breakdown
| Item | Typical expectation (candidate-reported) | Reality check |
|---|---|---|
| Graduation | 70% or 7.0 | Mailer wins |
| 10th & 12th | Same throughout rule | Keep scans |
| Branches | CS, IT, ECE and related | Strong DSA can help adjacent branches |
| Backlogs | None live | Clear before joining |
| Coding languages | Python, Java, JS, Go | Stick to one |
Who usually fits and who struggles
Good fit: You already finish two mediums in 90 minutes, you can talk about APIs without a TED script, and you will relocate to Chennai or Bengaluru.
Harder path: You only practiced aptitude dumps; you cannot write a tree problem; you want “no coding, only tools.” Freshworks is a coding company.
Branch myth: ECE is welcome on listed drives. The OA does not care. It cares that your solution passes hidden tests.
Freshworks placement papers - last few years
Download 2026 Freshworks placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
Comments & Suggestions
What Freshworks previous year papers actually train
Freshworks does not publish a permanent official paper set. Papers on this site are pattern trainers for the DSA first filter and early technical themes.
| Round (typical) | What to practice |
|---|---|
| Online assessment | 2-3 timed mediums: arrays, trees, graphs, DP, strings |
| Technical 1 | Live coding narration: brute force → optimize → edges |
| Technical 2 | More DSA and/or SaaS-lite design (tickets, TinyURL, APIs) |
| Managerial / HR | STAR ownership, Why Freshworks, city |
Think of papers as simulators for 90-minute DSA stamina. Themes repeat more than exact clones.
Themes that keep repeating (2024-2026)
- OA cycles: 2-3 DSA, HackerRank-style, medium-hard. Arrays, hashing, trees, graphs, DP keep returning.
- SE-1 onsite (GFG, updated Dec 2025): Telephonic, then onsite Saturday: tree construction and missing-positive DSA, OS/DBMS (thrashing, ACID), TinyURL under distributed constraints, rat-maze coding, then HR. Offer letter 3 days after HR. Prep tip pointed at common Amazon/Microsoft GFG archives plus Educative-style design for TinyURL follow-ups.
- 2026 prep expectation: Keep medium DSA warm. Expect design rounds to stay fresher-depth (actors, APIs, bottlenecks), not staff-level multi-region Kafka. Treat PDF packs as pattern catalogs.
How to use one paper set in a single sitting
- Timed: 90 minutes, 2-3 problems, same language as test day.
- Untimed review: rewrite the cleaner solution; list three edge cases.
- Map each miss to a theme (window / hash / tree / graph / DP) and pull two cousins from coding questions.
- 15 minutes: explain TinyURL or a Freshdesk ticket state machine out loud.
- Log one STAR ownership story the session reminded you of.
Related problems to practice
| Theme you saw | Drill next | Why Freshworks asks it |
|---|---|---|
| Sliding window / unique chars | At-most-K variants | Text / search UX |
| Trees | Construction, traversals, LCA lite | Nested ticket/category intuition |
| Graphs | BFS/DFS, shortest path | Workflow / dependency |
| Hash / missing positive | Frequency, first missing | Classic OA |
| Design lite | TinyURL, rate limit, cache | SaaS APIs |
From application to offer at Freshworks
Freshworks hires freshers through campus cells, freshworks.com/careers, hackathons, and referrals. After resume screen, the shape is product-company style: timed DSA OA, two technicals, managerial, HR.
Application methods
Campus recruitment
Through college placement cells. Batch OA, then interviews. Strong Chennai/Bengaluru story.
Online applications
freshworks.com/careers for early-career SWE. Follow the HackerRank (or similar) invite.
Hackathons / referrals
Improve visibility. You still need passing OA code and clear interviews.
1. Resume / eligibility screen
7.0 / 70% throughout when printed, listed branches, no live backlogs. Projects with ownership language help. This is a gate; coding is the filter.
2. Online Assessment (~90 min, 2-3 DSA)
| Item | Working note |
|---|---|
| Duration | Often ~90 minutes (some invites 90-120) |
| Problems | 2-3 DSA |
| Difficulty | Medium to hard |
| Languages | Python, Java, JavaScript, Go |
| Platform | HackerRank or internal, verify invite |
| Pass feel | Working optimal-enough solutions; older hub estimates ~15-20% advance |
Pass habit: skim all prompts. Bank the solvable medium first. Hidden tests punish off-by-one more than missing a fancy algorithm name.
3. Technical interview 1 (~45-60 min)
Live DSA plus project. Narrate brute force → optimize → edges. Complexity in one sentence each.
4. Technical interview 2 (~45-60 min)
More DSA and/or SaaS-lite design: APIs, multi-tenant intuition, TinyURL, ticket workflows, DB choice. Fresher depth: who the actors are, what breaks, what you cache.
5. Managerial (~45 min)
STAR: conflict, failure, ownership. Impact numbers. Why this product, not “any unicorn.”
6. HR (~30 min)
City (Chennai/Bengaluru), joining date, compensation. Know ₹20-28 LPA as a public band and say you will read base vs stock on the letter. The SE-1 GFG note got the letter 3 days after HR; do not assume every loop is that fast.
Timeline from application to offer
| Phase | Duration | Notes |
|---|---|---|
| OA | 1 day | Timed DSA |
| Technicals | 1-2 weeks | Virtual or onsite Saturday stacks |
| Managerial + HR | Days | Sometimes same week |
| Offer | 2-7 days after HR | 3 days in one SE-1 note |
| End to end | ~2-4 weeks common | Off-campus can stretch |
OA pattern cheat-sheet
| Component | Focus | Prep move this week |
|---|---|---|
| Coding Q1-Q3 | Trees, graphs, DP, strings | Two timed mediums + one hard attempt |
| Design follow-ups | Tickets, TinyURL, APIs | Explain one flow in 3 minutes |
| OS/DBMS lite | ACID, indexes, thrashing | One-liners with an example |
| Managerial / HR | Ownership, city | Four STAR + city answer |
TinyURL / ticket design in 10 minutes
- Functional: create short URL / create ticket, read, update status.
- Non-functional: latency, uniqueness, basic scale.
- API sketch:
POST /urls,GET /{code}. - Data: key-value plus metadata.
- Failure: collision, expired link, hot key.
Stop before you invent Kafka. Interviewers want a talking architecture, not a conference talk.
Weekend mock that matches a real drive
Saturday 10:00: 90-minute 3-problem OA.
Saturday 12:00: one live medium on a call with a friend.
Saturday 16:00: TinyURL + ticket state machine aloud.
Sunday 11:00: project deep-dive + two STAR.
Sunday 12:00: HR including city and CTC language.
Two weekends of that beat twelve nights of random SaaS YouTube.
Documents pack
10th, 12th, all semesters, ID, resume one page with a metric. Throughout 70% means the 12th PDF matters.
Night-before checklist
- Charger, ID, resume
- Language chosen and syntax warm
- One TinyURL sketch on paper
- City yes/no
- Sleep. A 9 a.m. OA after a 3 a.m. contest is how easy arrays go wrong
Why Freshdesk intuition matters more than a generic “SaaS” slogan
Interviewers work on ticketing, ITSM, or CRM products. You do not need to recite the 10-K. You do need one workflow in plain words: a customer opens a ticket, an agent changes state, an SLA clock runs, a comment thread is stored, a search box filters by status. That is the same muscle as a state machine plus an API. Students who only say “I love customer experience” without a ticket lifecycle sound like a brochure.
3-minute drill: draw states (new → open → pending → resolved). Name two APIs. Name one index. Name one failure (agent two-clicks resolve on a duplicate). Stop.
How to split 90 minutes across 2-3 DSA problems
| Minute | Job |
|---|---|
| 0-4 | Read all prompts; pick the solvable medium |
| 4-35 | Finish problem A with tests (empty, one, duplicate) |
| 35-38 | Skim B and C; pick B |
| 38-75 | Problem B; if stuck at 60, write a correct slower solution |
| 75-90 | Start C only if A and B are green; else harden tests on A/B |
A green medium + a partial hard beats three reds. The SE-1 onsite still expected working DSA (trees, missing positive, rat-maze). OA is the same sport, shorter.
OS/DBMS one-liners that showed up onsite
The Dec 2025 SE-1 note mentioned thrashing and ACID. You do not need an OS course replay. You need:
- ACID: Atomicity (all or nothing), Consistency, Isolation, Durability. Example: money transfer.
- Thrashing: too much paging, CPU busy swapping, little useful work. Fix intuition: fewer processes or more RAM, not “buy Kubernetes.”
- Index: speeds lookup, costs writes. When would you not index every column?
Write those four lines once. Do not open a 400-page PDF the night before.
Managerial: ownership, not culture posters
They will ask about a fight on a team, a missed deadline, or a bug you shipped. STAR with a number. “I broke login for 20 users, wrote a regression test, and the next release had zero repeats” is an answer. “I am a team player who thinks outside the box” is not.
Prepare four stories: conflict, failure, leadership-lite (you unblocked someone), and a time you said no to a bad shortcut. Reuse them. Do not invent a fifth on the call.
Chennai vs Bengaluru
Both are real engineering cities for Freshworks. If the form lists one, that is the answer. If HR asks preference, pick one and give a reason that is not “better weather.” Family, current city, or “I will move for the team” are adult reasons. “I will only do remote” is how product HR ends the loop unless the posting says remote.
Where to practise for Freshworks
Online assessment
OA format, timing, and question types.
Coding questions
DSA patterns for OA and technical rounds.
Aptitude / mock quiz
Quant, logic, and timed mock quiz.
Interview experiences
Candidate stories and round notes.
HR interview questions
Common HR questions, sample answers, STAR tips.
Week-by-week prep
Study plan and round-by-round strategy.
Where your Freshworks prep time should go
If a Freshworks invite is 3-8 weeks out, treat this hub as the map and the linked practice pages as the drills. Do not reread eligibility ten times. Check the JD once, then spend hours on the filter that actually rejects people.
Typical fresher CTC chatter for Freshworks sits around ₹20-28 LPA (candidate-reported - confirm the letter). Languages students mention most often: Java, Python, C, Go. Pick one and stay with it in OA and interviews.
Eligibility reminder (from student reports): Candidate-reported campus floors commonly cite 70% or 7.0+ CGPA across 10th, 12th, and graduation; B.E./B.Tech/M.E./M.Tech/MCA in CS, IT, ECE, or related; final-year and recent grads (often within 1 year); no active backlogs; max about 1 year gap. Strong DSA matters after the resume screen. Always verify the drive notice.
What you are training for: Common SWE shape: online assessment (~90 min, 2-3 DSA on HackerRank or similar) → technical 1 (DSA + projects) → technical 2 (more DSA and/or SaaS-lite design) → managerial → HR. Some onsite SE-1 notes stack telephonic + three onsite + HR. End to end is often 2-4 weeks.
Short version of the prep split: Treat Freshworks like product SaaS hiring. Split time roughly: 50% medium DSA under 90 minutes, 20% one SaaS-lite design (tickets, TinyURL, APIs), 20% project depth, 10% behavioural/STAR. Languages: Python, Java, JavaScript, or Go. Full plan: /freshworks/preparation-guide/.
A four-week plan that actually gets used
Week 1 - pattern, not vibes. Language fluency: rewrite 10 old solutions in one language until you stop hunting syntax. Open the Freshworks previous-year sets on this site and mark which sections ate your time. Write the timing on a sticky note. That number is more useful than a 200-problem LeetCode streak you never timed.
Week 2 - the steep filter. Most Freshworks drives fail people on the first timed paper or OA. Do three timed sits this week. After each one, log every miss in a two-column note: topic and why (slow, wrong formula, bad edge case, panic). The next sit should only add problems from that log.
Week 3 - talk tracks. Technical interviews at Freshworks usually want a clean project story, one or two CS fundamentals, and (if the process has it) a behavioral or values round. Write STAR stories on paper, not in your head. Practise “Why Freshworks?” with one concrete product, lab, or business line - not a slogan.
Week 4 - mocks and logistics. Sleep, id photocopies, and a dry run of the oa platform if the invite names one. If you still have energy, redo only the questions you failed in week 2.
Where the hours should go
| Slice | Share of weekly hours | What “done” looks like |
|---|---|---|
| Timed papers / OA | ~40% | You finish a Freshworks-style sit without guessing the clock |
| Coding / role technical | ~30% | You can explain a solution out loud in your chosen language |
| Fundamentals / domain | ~20% | You can teach one OS/DBMS/networks (or domain) topic to a friend |
| Stories + HR | ~10% | Two STAR stories and a specific Why-this-company answer |
If you only have 10 days, keep the same ratios and cut volume, not the timed sits.
Practice pages to open this week
- OA / assessment notes
- aptitude mock quiz
- coding question bank
- interview experiences
- HR question bank
- week-by-week guide
- previous year papers
- 2026 paper page
Use this hub for the Freshworks story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
Common ways students waste a month
- Collecting 12 Freshworks PDFs and never sitting one under a timer.
- Switching languages every weekend because a senior used a different one.
- Memorising HR answers before they can finish the OA.
- Ignoring the company-specific quirk on this page (unique round, exam name, or role band) and preparing like a generic service-company drive.
If you do one thing after reading this: schedule three timed Freshworks papers on three different days, then interview prep on the leftovers.
If you are starting from a service-company prep base
A TCS/Infosys aptitude deck still helps the quant/logic slice of many Freshworks papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in Freshworks-specific coding or domain drills from the nested banks. Shared prep is fine; shared assumptions about rounds are not.
10-day crash version
Days 1-3: one timed Freshworks paper each day plus error log. Days 4-6: only the topics you missed, plus 4-6 coding problems in one language. Days 7-8: project + STAR + Why Freshworks. Day 9: one more full mock. Day 10: light review and sleep. This is worse than four weeks, but it beats rereading notes the night before.
Prep focus for Freshworks SWE
Week-by-week calendars live on the preparation guide. This section is the focus split so you do not spend August on TCS dumps.
Time split that matches how people actually fail
| Bucket | Share | What “done” looks like |
|---|---|---|
| Timed medium DSA | 50% | Two completes in 90 minutes |
| SaaS-lite design | 20% | TinyURL + ticket API in 10 minutes spoken |
| Project depth | 20% | Metrics, bug, rebuild |
| STAR + HR | 10% | Four stories + city |
The biggest miss is aptitude-only prep for a DSA company. Invert that.
What not to do this month
- Do not grind 40 quant MCQs as the main sport.
- Do not walk into design with “microservices” and no API sketch.
- Do not quote 40 LPA on an SE-1 drive.
- Do not skip 12th scans because graduation is 8.5.
One-week focus if the drive is soon
Mon-Tue: two 90-min OA mocks.
Wed: trees + graphs only.
Thu: TinyURL + tickets aloud.
Fri: project + STAR.
Sat: combined mock.
Sun: error log, sleep.
If you have eight weeks, use the nested guide.
Same week as Zoho / Atlassian / a services GET
Do not mix sports. Freshworks wants two mediums in 90 minutes. Zoho may want C output and a long written. HCL wants aptitude MCQs. If all three land, sit Freshworks on the DSA day you already mocked. Do not “quickly revise percentages” the morning of a HackerRank OA.
Error log that actually changes the next mock
After every 90-minute set, write four lines only:
- Problem that stayed red (theme: tree / DP / graph).
- Why (syntax / wrong idea / no time).
- One cousin problem to do untimed today.
- One edge case you skipped (empty, overflow, duplicate).
That log is the prep plan. A notebook of 40 unsolved links is not.
What “SaaS multi-tenant” means at fresher depth
Many customers, one codebase, data must not leak across accounts. In an interview: a org_id on rows, auth checks on every read, no “select * from tickets” without a tenant filter. Stop before you invent a mesh. If they ask how search works, say indexed fields per org, not Elasticsearch cluster gossip. Write that in one box on paper and reuse it if TinyURL already ate the whiteboard. A second design prompt is often a smaller cousin (rate limit, search, comments), not a new product. Reuse the same actors-and-APIs skeleton instead of starting from zero. Interviewers notice when the second sketch still has a clear POST and GET; they notice faster when you panic-draw a new cloud. Keep the first sketch visible and extend it on the same board.
What Freshworks pays freshers (candidate-reported)
Figures below are candidate-reported India bands (as of August 2026). Actual offers depend on level, location (Chennai / Bengaluru), hiring year, and written components (base / bonus / stock).
| Band | Typical CTC (candidate-reported) | Notes |
|---|---|---|
| Software Engineer / SE-1 (fresher) | ₹20-28 LPA | Primary band for this hub |
| Senior SWE (2-4 YOE blogs) | ₹35-45 LPA | Not the fresher default |
| Staff-style | Higher | Outside fresher prep |
Confirm base, joining bonus, and equity language on the written offer. Do not treat blog midpoints as guarantees.
Benefits students actually care about
Health insurance, stock language, hybrid vs office in Chennai/Bengaluru. Public-company SaaS is the PPT story; day-one work is still a squad and a backlog.
How to talk CTC in HR
Know ₹20-28 LPA as a public total band. Ask what is base vs stock. Do not negotiate like you already have three FAANG offers unless you do.
Offer-stage discipline
- Read city
- Match 10th/12th/degree %
- Verbal “selected” is not a PDF
- The SE-1 note’s 3-day letter is one data point, not a promise
Freshworks hiring updates for 2026
DSA OA stays the door
2-3 mediums in ~90 minutes. Aptitude dumps do not transfer.
Onsite stacks still happen
SE-1 GFG: telephonic then Saturday onsite with TinyURL + rat-maze. Read the schedule.
Design stays fresher-depth
APIs and uniqueness, not staff multi-region. Practise talking TinyURL.
Chennai / Bengaluru
Have a city answer. Hybrid talk does not cancel relocation questions.
Net for 2026: Freshworks is still product SaaS. Double down on timed mediums and one spoken design sketch.
FAQs students ask about Freshworks placements
Papers & process
Can I download Freshworks placement papers PDF for free?
Yes. Free Freshworks placement papers PDF and 2024-2026 style DSA practice are on this site. Start with the 2026 PDF or the archive.
What is the Freshworks placement process 2026?
OA (2-3 DSA) → technical 1 → technical 2 → managerial → HR. Some loops add a telephonic screen or onsite stack. Often 2-4 weeks. Details: online assessment.
How many rounds are there in Freshworks interview?
Often 4-5. One SE-1 note: telephonic + 3 onsite + HR call. Count the mailer.
Do Freshworks interviews include system design?
Fresher-depth yes on many loops: TinyURL, tickets, APIs. Not staff-level distributed systems.
OA & languages
What does the Freshworks Online Assessment look like?
~90 minutes, 2-3 DSA, HackerRank-style. Python, Java, JavaScript, or Go. Working solutions beat half-finished cleverness.
What programming languages are allowed in Freshworks?
Python, Java, JavaScript, Go on most invites. Pick one early.
Eligibility & offer
What is Freshworks eligibility criteria for freshers 2026?
Commonly 70% or 7.0 throughout; CS/IT/ECE; no live backlogs; gap ≤ ~1 year. Your mailer wins.
What is Freshworks salary for freshers in India 2026?
SWE ~₹20-28 LPA (candidate-reported, August 2026). Confirm base vs stock on the letter.
Where does Freshworks hire freshers in India?
Chennai and Bengaluru most often. HR will ask relocation.
Are Freshworks placements only for CS/IT?
Primarily CS/IT/ECE with strong DSA. Other branches only if the notice says so and your coding is real.
Prep & comparisons
How to prepare for Freshworks placement?
Timed medium DSA, one SaaS-lite design, project depth, STAR. Guide: preparation guide.
Any pro tip for Freshworks placement preparation?
Clear two mediums in 90 minutes before you polish a design essay. Rehearse TinyURL in plain words. Do not treat this as a GET aptitude paper.
Freshworks vs Zoho vs Salesforce?
Freshworks: public SaaS, DSA + design-lite, ~₹20-28 LPA reported SE. Zoho: different written/C culture. Salesforce: enterprise CRM loop. Prep DSA for Freshworks; do not assume Zoho papers transfer.
Is Freshworks harder than service-company OAs?
Different sport. HCL/Mphasis mix aptitude MCQs. Freshworks wants two working mediums. If you only practised percentages, you are not ready.
Do I need Go?
No. Python or Java is enough if the invite lists them. Do not learn Go the week of the OA.
How fast is the Freshworks offer after HR?
One SE-1 GFG note got the letter in 3 days. Other loops take a week or more. Do not resign another offer until the PDF lands.
Is aptitude part of the Freshworks OA?
The common SWE report is 2-3 DSA, not a 40-question quant paper. If your invite adds aptitude, follow the invite. Default prep is still timed coding.
Freshworks - recent candidate experiences
GFG SE-1 onsite (updated 15 Dec 2025)
“The interview is comprised of telephonic round , 3 onsite interview and 1 hr discussion over call,” with onsite the following Saturday after a role overview. Onsite stacked tree construction and missing-positive DSA, OS/DBMS (thrashing, ACID), then TinyURL design under distributed constraints. After the third onsite (TinyURL + rat-maze coding), HR with standard behavioural questions. “I got the offer letter 3 days after that.” Prep tip: common Amazon/Microsoft GFG archives plus Educative-style design for TinyURL follow-ups. Source: GeeksforGeeks SE-1 onsite.
What to steal: 90-minute DSA stamina; tree + hashing patterns; a TinyURL sketch you can redraw; OS/DBMS one-liners; STAR ready for a fast HR.
What to ignore: Paying for dumps; treating Freshworks as TCS NQT; quoting staff-level design books you cannot explain.
OA composite: Candidates who banked a passing medium and then attempted the harder tree passed. Candidates who started the hardest prompt first and submitted nothing did not. Complete is the bar.
Design composite: A 10-minute TinyURL with collisions and expiry beat a 20-minute microservices monologue. Plain APIs are the bar.
Onsite composite: A Saturday stack (DSA + OS/DBMS + TinyURL + rat-maze + HR later) is a stamina problem. Eat. Carry a charger. Do not schedule a second company’s OA the same morning. The 3-day offer turnaround in that note is luck plus a complete loop, not a promise you can quote in another drive.
Language composite: Candidates who stuck to Python or Java they had used for 50 problems wrote cleaner OA code than candidates who switched to Go “because Freshworks uses it.” Confirm the invite list. Then ignore fashion.
Freshworks is product SaaS with a named SE loop. ₹20-28 LPA is a real reported band. The OA is DSA. Design is fresher-depth. Students who treat this as a services aptitude paper are the ones those notes are about.
Use timed papers on this site. Follow the preparation guide. Read interview experience and the HR page. Finish two mediums. Draw TinyURL once. Print 10th and 12th. Then sit the drive like someone who ships tickets, not like a dump-PDF scavenger.
If Freshworks and Zoho/Salesforce all land the same week, compare city, loop length, and whether you actually like customer-support SaaS. A 22 LPA SE-1 you will join in Chennai beats a rumour 28 LPA with a city you will reject in HR. Classroom “selected” is not a letter. Wait for the PDF.
Day-one work is still a squad and a backlog. “I will only do GenAI research” is a bad HR answer. “I will build APIs on Freshdesk-like workflows and I already write Python/Java” is the SE answer.
Interview day logistics: Laptop charged; quiet room for OA; college ID for onsite Saturday. Do not sit HackerRank on flaky hostel Wi-Fi.
Keep practising until two mediums and a 10-minute TinyURL are automatic. That is Freshworks. Everything else is decoration.
More narratives: Freshworks interview experience.
Related companies to compare
Zoho · Salesforce · ServiceNow · Atlassian · Intuit · BrowserStack
Last updated: August 2026.