
Synthesized from 17 candidate submissions for ALL.
The process is designed to evaluate analytical thinking and product-centric problem solving. It utilizes scenario-based questions to assess how a candidate applies technical knowledge to solve customer-facing challenges.
This role involves a comprehensive assessment including a Bar Raiser round and a Director-level interview. Candidates are tested on advanced data structures, scalable system design, and database optimization. Key questions include: 'Design a food delivery system', 'Implement a snapshottable map', 'Find kth highest element in infinite stream', and 'SQL queries for top K elements'.
The process involves an online assessment followed by a practical assignment (e.g., building a file-based key-value store) and two technical interviews focusing on front-end and back-end fundamentals. Key questions include: 'Stock Buy & Sell', 'Delete a node in Linked List without head pointer', and 'Basic JS/HTML/CSS concepts'.
This role focuses on the practical application of testing methodologies and coding skills. The process involves scenario-based testing questions and coding challenges to assess quality assurance mindset.
The hiring process for senior roles is highly technical, focusing on system architecture, concurrency, and production-grade coding. It consists of multiple technical rounds, a deep-dive system design round, and managerial discussions. Key questions include: 'Design an API Rate Limiter', 'Design a File management system', 'Design a distributed logging system', 'Cron expression parsing', and 'Word Ladder'.
The process typically begins with an online assessment (75-90 minutes) featuring 3-4 coding problems of medium to hard difficulty. Subsequent rounds include technical face-to-face interviews covering data structures (trees, linked lists, arrays), OOPs concepts, ACID properties, and database design. Puzzles and C/Java-based coding challenges are common. Key questions include: 'N-Queen problem', 'Design TinyURL', 'Find Kth largest element', 'Least Common Ancestor', and 'Bridge crossing puzzle'.
The interview is specialized and focuses on architectural design for AI-driven systems. Candidates are evaluated on their ability to design automated workflows for customer support operations.
The interview process is streamlined and centers on fundamental software engineering capabilities, specifically focusing on string manipulation and core problem-solving tasks.
The candidate successfully cleared all rounds of FreshWorks' on-campus interview process for the Software Developer role. They demonstrated strong problem-solving skills in coding and data structures, as well as a solid understanding of OOPs concepts and puzzles. All 13 candidates who reached the HR round were selected, indicating a highly positive outcome.
4 coding questions, medium to tough difficulty, 75 minutes duration. All test cases passed. Questions were not the same for all candidates.
4 coding questions of medium to tough difficulty, 75 minutes duration. Candidates could use Google and communicate with friends. 87 out of 350 students were selected for the next round.
Shortlisted students were given a problem statement for frontend or backend (or both) with less than 12-15 hours to complete. 47 out of 87 students were shortlisted for the next round.
First face-to-face technical interview with 15 panels. The interviewer focused on data structures and asked the candidate to introduce themselves and explain their projects. The candidate answered all questions and wrote code for them. 26 out of 47 students were selected for the next round.
Write an algorithm to print the pairs that matches the given sum in a sorted array.
Write an algorithm to find the Kth largest element in an unsorted array.
Write an algorithm for finding the least common ancestor in a binary tree.
Which data structure is used in sudoku and write a code for the same.
What are the different kinds of traversals in trees?
The interviewer asked about OOPs concepts like upcasting, downcasting, inheritance in Java, ways to overcome multiple inheritance, abstract classes, static and final keywords, and polymorphism. The candidate was also asked to explain ACID properties. Later, two puzzles (bridge crossing puzzle and egg dropping puzzle) were asked. The candidate answered the first puzzle and the second after a hint. 13 out of 26 students were shortlisted for the final round.
OOPs concepts like upcasting and downcasting, inheritance in Java, ways to overcome multiple inheritance, abstract classes, static and final keywords, polymorphism.
ACID properties and their definitions.
Bridge crossing puzzle.
Egg dropping puzzle.
The HR interview was friendly and focused on personal and motivational questions. The candidate answered all questions confidently. All 13 candidates who reached this round were selected.
Tell me about yourself.
Why did you choose your University?
Did you get rejected in any of the companies and why?
Why Freshworks?
Are you planning for higher studies?
Are you ready for a 6-month internship?
The candidate faced a phone screening, coding round, and system design round. The system design round went poorly due to unpreparedness, leading to rejection.
Phone screening round involving discussion about the candidate's current role, tools, and tech stacks. The candidate was asked one coding question and one system design question.
Find the intersection of 2 Linked Lists
LLD on building a system like Flipkart
Coding round with three questions focusing on linked lists, mathematical calculations, and time duration overlap.
Find the middle element in a LinkedList
Find the cube root of a perfect cube without using built-in methods
Find the overlapping time duration in two arrays having hours stored
System design round where the candidate was asked about their most challenging task in their experience. The candidate struggled with the question and provided an unsatisfactory answer. An object-oriented design question was also asked, requiring the candidate to write a class and abstract methods for a requirement. The interview went poorly, leading to rejection.
Most challenging task I did in my experience
Object-oriented design question with class and abstract methods