After a recruiter touchpoint, I ended up with a technical assessment that was essentially pair programming. The interviewer was genuinely supportive the whole time, prompting me as I went and helping me keep my footing instead of making it feel like a gotcha. Overall it felt like a friendly working session more than a grilling, and I left with the impression they were willing to help during the process rather than intimidate you.
I didn’t end up with an offer, but the experience itself felt strong and well-intentioned. The biggest thing I remember was how comfortable the tone was while I was solving, which made the assessment feel much more approachable than I expected.
> 1 year
Average Positive United States
My process kicked off with an HR informational conversation, then moved into a phone screen and eventually a virtual on-site. Before the on-site, I was sent a DS interview study guide that outlined modules to work through. I liked that it was concrete—especially since I also noticed how quickly the recruiter responded to questions, scheduled the interviews, and followed up with outcomes.
Once the technical side started, I dealt with A/B testing throughout. In one DS round, the interview began with questions about my background, then shifted into an A/B testing scenario where I had to walk through the full workflow at a fairly structured level—starting from the main steps and then drilling into each one. I ended up tracking my reasoning in a shared document while I talked through decisions, metrics, and the logic behind the experiment. The technical rounds felt open-ended rather than purely “rote stats,” and that made the format feel more like real product thinking than memorization.
> 1 year
Difficult Neutral Mountain View, CA
My path felt very technical from the start and leaned on coding and math-heavy assessments. I encountered a phone screen plus an online coding step, a…
> 1 year
Average Negative United States
I went through a fairly standard multi-round sequence: recruiter outreach and scheduling, then several DS-focused interviews leading into tougher fina…
> 1 year
Average Neutral United States
I applied and waited a few weeks before the interview happened. When the meeting finally came, the schedule email said it would run for an hour, but i…
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Structure & Timeline
The interview process typically begins with a recruiter touchpoint, followed by a series of phone screens and potentially an onsite interview, which can last several hours and involve multiple interviewers. Candidates should expect a mix of technical and non-technical discussions throughout the stages.
Candidates will face a variety of technical assessments, including coding challenges, A/B testing scenarios, and machine learning concepts. The difficulty level can be high, with expectations for problem-solving under pressure and practical application of data science skills.
Coding challengesA/B testingMachine learning
Behavioral & Values Assessment
Interviews often include behavioral questions that assess fit and alignment with Quora's values, focusing on candidates' past experiences and how they approach problem-solving and product thinking. Candidates should prepare to discuss their motivations for joining Quora and their thoughts on the product.
The level of engagement from interviewers can vary significantly, with some candidates experiencing supportive interactions while others report feeling rushed or criticized. Candidates should be prepared for differing dynamics and maintain composure throughout.
Interviewer engagementSupportive vs. criticalDynamic interactions
Preparation Materials & Expectations
Candidates may receive study materials or guides before interviews, which can help set expectations for the technical content. However, some candidates noted discrepancies between what was communicated and the actual interview content, particularly regarding the technical focus.
Study materialsExpectation managementTechnical focus
Overall Difficulty & Outcomes
The interview process is generally perceived as challenging, with many candidates reporting high difficulty levels in technical rounds. Despite thorough preparation, some candidates do not receive offers, often due to performance in high-stakes coding or technical assessments.