Devrev's coding rounds are generally considered medium to hard difficulty, aligning closely with Google and Meta. The unique challenge is the expectation to write production-quality, modular code with clear edge-case handling and test cases, rather than just a brute-force solution. They also frequently incorporate elements of their product domain (e.g., integrations, APIs) into problems.
The Bar Raiser is a 60-minute behavioral round conducted by a senior leader outside the hiring team, focused on the Amazon Leadership Principles (which Devrev uses). Prepare by structuring 8-10 detailed stories using the STAR method, with concrete metrics. Practice articulating how each story demonstrates at least 2-3 principles like 'Customer Obsession' or 'Dive Deep.' It's not just a chat; it's a structured evaluation of your leadership potential.
Focus on mastering core topics: Arrays, Strings, Linked Lists, Trees (BST, Tries), Graphs (BFS/DFS), Recursion, and Dynamic Programming (medium difficulty). Aim to solve at least 150-200 curated LeetCode problems, with 60% medium and 40% hard. Prioritize problems from platforms like LeetCode's 'Top Interview Questions' and company-specific lists, ensuring you can explain time/space complexity and optimize solutions on the spot.
SDE-2 interviews have a significantly stronger emphasis on system design and architectural thinking. You'll get a dedicated 45-60 minute system design round where you must design a scalable service, discuss trade-offs, data modeling, and APIs. For SDE-1, system design is more foundational (OO design, low-level design). SDE-2 also expects more nuanced behavioral examples demonstrating mentorship and project leadership.
The top mistake is jumping into coding without clarifying requirements and edge cases. Devrev interviewers expect you to ask clarifying questions about input constraints, error handling, and expected outputs. Other mistakes include writing messy, monolithic code instead of modular functions, neglecting to write test cases, and being unable to optimize an initial solution when prompted.
Beyond solving the problem, standing out requires demonstrating product sense and pragmatic engineering. Discuss how your solution impacts the user, mention potential monitoring/observability, and consider operational aspects like deployment or caching. In the Bar Raiser, use data-rich stories that show you took ownership and drove measurable impact, aligning directly with Devrev's focus on customer outcomes.
Weeks 1-4: DSA intensives. Solve 30-40 problems/week, focusing on core patterns. Weeks 5-6: System design for SDE-2 (study Grokking the System Design Interview, design 5-6 systems) & OOD for SDE-1. Simultaneously, draft and rehearse your 8-10 behavioral stories daily. Week 7: Take 3-4 timed mock interviews with peers focusing on communication. Week 8: Review weak areas, re-solve high-frequency Devrev problems from forums like LeetCodeDiscuss, and finalize your story bank.
The end-to-end process typically takes 4-6 weeks. After each round, feedback is usually provided within 3-5 business days. If you haven't heard in a week, a polite follow-up to your recruiter is appropriate. The entire loop (4-5 rounds) is often scheduled within 2-3 consecutive weeks once started. Offer deliberation can take an additional 1-2 weeks after the final round.
