Dev Rev

Role: Software Developer: University Hire

College: Not Specified

Interview Date: Not Specified (Application was direct, published experience covers the entire process)

Interview Type: Off-Campus (Applied through company career page)

Result: Offer

Difficulty: Easy/Moderate (Overall)

Rounds: 8 rounds (Test, Screening, Technical #1, you.io, Cultural #1, Technical #2, Cultural #2, Founder Interview)

Topics Asked: Basic algorithms and data structures (MCQs), programming questions, behavioral questions, coding problems, debugging problems, math questions, logic puzzles, Linked Lists, System Design, Projects.

Experience:

The candidate applied for the "Software Developer: University Hire" role directly through DevRev's "Join Us" page.

Test: An automated mail for a test on the CodeSignal platform was received. The test included MCQs on basic algorithms and data structures, and programming questions. The programming questions were algorithmically simple but had slightly complex implementations.

Screening: This round was described as a fun mix of behavioral questions, coding problems, debugging problems, math questions, and logic puzzles. The coding and debugging problems were new and interesting but easy. The interviewer was helpful, especially when the candidate was stuck trying to prove an intuitive answer to a math problem.

Technical Interview #1: Questions were easy/moderate. The candidate struggled with a simple linked list problem, requiring hints and whiteboard explanations from the interviewer to solve it. Despite this, the candidate was selected for future rounds.

you.io: (Details not explicitly provided, but listed as a step in the process)

Cultural Interview #1: This was the candidate's first cultural/HR interview, focusing mainly on teamwork in past projects. The candidate found it monotonous but passed.

Technical Interview #2: Started with questions about past projects. The candidate was then asked to design a technology mentioned in their resume. Though unprepared for system design, the candidate listed expectations, functionalities, data structures, and algorithms/implementations, which satisfied the interviewer. A simple coding problem was also asked and implemented.

Cultural Interview #2: More conversational, with the interviewer trying to understand the candidate better. Most questions were "why" extensions to previous responses, prompting deeper thought. The candidate enjoyed this round.

Founder Interview: (Details not explicitly provided, but listed as a step in the process).

Result: The candidate received an offer.