After speaking with a recruiter, the next step was a technical assessment that ended up being pair programming. I was surprised by how supportive the interviewer was; they didn’t just sit back and evaluate me from a distance. They helped me work through what I was doing while still making me think through the problem, and that made the round feel far less intimidating than I expected.
The broader process I experienced still followed a fairly standard multi-round arc—screening with recruiting, then conversations with leadership-style interviewers alongside open-ended technical discussion. The technical parts leaned on problem-solving rather than one-liners, and at times it felt more like a guided conversation with a senior employee than a rigid interrogation. By the end, I didn’t get an offer, but I came away feeling like the process was fair and that the team was willing to keep things constructive when I needed clarity.
> 1 year
Average Positive United States
I started with an HR informational interview, then moved into a phone screen and finally a virtual on-site. Before things kicked off, the recruiter sent me a study guide that broke down what to expect for each module, which made the process feel organized rather than vague. I also remember how quickly the recruiter responded to questions and how promptly they scheduled each interview, along with updates on where I stood.
Most of the modules centered on data-sci work that mapped back to the job, and I felt like the topics were more relevant than generic “interview practice.” A few parts felt a little repetitive, but overall the structure still landed well because it was clear what they were testing and how it related to Quora’s product work. The process felt smooth and respectful end to end, and I left the experience with a positive impression even though I didn’t end up getting an offer.
> 1 year
Difficult Neutral Mountain View, CA
My process kicked off with an online assessment that quickly set the tone. I worked through a Codesignal-style coding check where I saw questions span…
> 1 year
Average Negative United States
The process began with a recruiter call where we dug into my background and also talked in detail about the role. After that, I had a technical round …
> 1 year
Average Positive United States
After a recruiter conversation, my first real technical step was a structured discussion of A/B testing. The round started with me walking through how…
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 call, followed by a technical assessment and multiple rounds, often including live coding and discussions on A/B testing. The overall timeline is around three weeks, with a structured approach that helps candidates understand what to expect.
Recruiter callTechnical assessmentMulti-round
Technical Assessment & Coding Rounds
Candidates can expect a mix of coding assessments, including live coding and pair programming, with a focus on problem-solving rather than rote memorization. The difficulty level is generally high, with questions that test both breadth and depth of knowledge.
Live codingPair programmingProblem-solving
Focus on A/B Testing & Metrics
A/B testing is a central theme in the interviews, with candidates expected to discuss experimental design, metrics for success, and how these concepts apply to Quora's products. This round often feels more like a case conversation than a quiz.
A/B testingMetricsExperimental design
Interviewer Dynamics & Communication
The interaction style of interviewers can vary significantly, with some candidates experiencing supportive and constructive conversations, while others report combative or disengaged interviewers, impacting their overall experience.
Candidates often receive study guides or resources from recruiters, which help clarify expectations and relevant topics, particularly around data science applications and A/B testing. However, some candidates feel the need for more clarity on specific expectations.
Study guidePreparationExpectations
Feedback & Outcome
While many candidates leave the process with a positive impression of the organization and its professionalism, there are common frustrations regarding the lack of feedback after rejections, which can make it difficult to understand areas for improvement.