Real, anonymous reports from people who interviewed for Software Engineer at Quora, newest first and distilled into what to expect across the loop.
I started with an online CodeSignal-style assessment after applying. The format was a set of coding questions with a strict time cap—about 60 to 70 minutes—with four problems. The questions skewed toward core programming fundamentals: array traversal and sorting-style tasks, plus a mix of easy/medium algorithm prompts that felt like LeetCode-style practice.
My process began with recruiter outreach and a short call. In my case, the recruiter conversation was pretty standard and set expectations; I was even sent a packet explaining the interview steps and what would happen next. The interview format they described sounded manageable, with individual question rounds typically running around 30 to 45 minutes, focused on the job’s listed topics.
Candidates typically start with a timed online coding assessment, often lasting around 60 to 120 minutes, featuring algorithmic questions that resemble LeetCode-style problems. The pressure of time and the scoring criteria can significantly impact candidates' experiences and outcomes.
Initial interactions with recruiters can vary widely, from organized and professional to uncomfortable and unprepared. Candidates noted that the recruiter’s engagement level and clarity about the process significantly influenced their overall impression of the hiring experience.
The technical interview rounds often include a mix of coding challenges and system design questions, with a strong emphasis on algorithm efficiency and optimization. Candidates reported that the difficulty level is high, and interviewers expect quick, precise solutions under pressure.
Behavioral interviews are included in the process, sometimes alongside technical discussions, and can play a crucial role in the overall evaluation. Candidates felt that their communication skills and fit with the company culture were assessed alongside their technical abilities.
For those who reach the onsite phase, interviews are typically back-to-back and can be exhausting, mixing coding, debugging, and discussions about algorithms. The pace is fast, and candidates noted that one poor performance can overshadow otherwise solid work.
Candidates expressed frustration over the lack of feedback after assessments and interviews, often leaving them unclear about their performance and the reasons for rejection. Clearer communication regarding evaluation criteria could enhance the overall experience.