Fab.com Recruitment Process
Question Details
This article will give you information about the company, its recruitment process,
sample questions that have been asked previously, lots of experiences shared by other as...
Full Details
This article will give you information about the company, its recruitment process,
sample questions that have been asked previously, lots of experiences shared by other aspirants, and the portal where you can apply. Table of Content About Company : Recruitment Process : Academic Criteria : Telephonic Rounds : Technical Rounds :
HR Round CTO Round About Company : Fab is an e-commerce company founded in 2010. In March 2015, the digital and ecommerce assets of Fab were acquired by PCH International for an undisclosed sum and has since been relaunched as a new entity with no interaction from the original founders. Fab was originally headquartered in Manhattan and operated a warehouse in Keasbey, New Jersey. The company once had office locations in Pune (India), and Berlin. Fab made its first acquisition in January 2012 when it purchased independent fashion retailer FashionStake.In February 2012, Fab purchased German flash sales website Casacanda. Four months later they acquired UK company Llustre Recruitment Process : Fab.com conducts 6-7 rounds to select freshers as Software Engineer in their organisation. Telephonic Round 1 Telephonic Round 2 Technical Round 1 Technical Round 2 Technical Round 3 Technical Round 4 HR Round CTO Round Academic Criteria : 70 percent or above in B.Tech, Class X and XII. No backlogs at the time of interview Telephonic Rounds : Telephonic consists of discussion around resume- your previous projects, prior experience etc. To clear this round you must be well prepared with data structures and algorithms along with your resume. Tips : Mention only that you know thoroughly, in resume. Listen the question carefully. Find a good location with no noise. It may also be a skype round, check your system sounds prior to the call. Technical Rounds : The students who clear the written round are called for Technical Interview. To clear this round you should be clear with your basics. You should be prepared with Data structures and Algorithms, and DBMS. You should be well prepared with system design problems. Students will be expected to write codes in the interview. They also ask questions from resume. They frequently ask questions about your previous projects. You may be asked puzzles in this round. Tips: Project a Positive Attitude. Understand the question completely and thoroughly Try to be as interactive with interviewers as possible. Be clear how you will proceed before you start writing your code. Check your code for errors and bugs before you present it to the interviewer. .
HR Round You can expect general HR questions like : Tell me about Yourself History of Fab.com Things you have that you really proud of What is the ultimate aim of your life? Questions form resume CTO Round In this round you can expect questions related to Fab.com, related to your life such as : Inclination towards Fab and why do you want to join Describe your life in a true Bollywood Style. Mistakes you have done. Interview Experiences It is always beneficial if you know what it is to be there at that moment. So, to give you an advantage, we provide you Interview Experiences of candidates who have been in your situation earlier. Make the most of it. Fab.com Interview Experiences Questions Asked in Fab.com : Segregate 0s and 1s Two numbers with sum closest to zero The Celebrity Problem When should be indexes used in Database? Where to Apply ? Fab.com careers Fab.com Official Website
About This Question
This is a reported interview question from a fabcom interview for a swe role during the recruiter round reported in 2025.
It covers the following topics: Sql, System Design .
Topics
More Fabcom Interview Questions
About Fabcom Interview Reports
This question was reported by a candidate who interviewed at Fabcom. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Fabcom are the higher-signal extractions to take from this report.
For broader preparation context, the Fabcom interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Fabcom reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Fabcom Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Fabcom reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.