Track: Other
Other Roles Role-Structured Interview Briefing
Overview
Razorpay’s hiring process for non-engineering roles (e.g., Associate Technical Consultant, Product Support Engineer) is foundation-focused, emphasizing technical fundamentals, scenario-based problem-solving, and behavioral alignment. These roles often involve telephonic interviews, technical assessments, and HR rounds, with a moderate difficulty level.
Round Breakdown
1. Technical Round
Format: 30-60 minutes, conceptual and scenario-based.
Common Question Types:
- Programming Fundamentals: E.g., OOPs, data structures, algorithms.
- Database Queries: E.g., SQL joins, subqueries.
- Scenario-Based: E.g., handling team conflicts, system design trade-offs.
Exact Questions Asked:
-
OOPs Concepts:
- Problem: "Explain OOPs concepts (e.g., inheritance, polymorphism)."
- Source: GeeksforGeeks
-
SQL Queries:
- Problem: Write a query involving
JOIN, SUBQUERY, and FOREIGN KEY constraints.
- Source: Trusted Source
-
Scenario-Based:
- Problem: "As a Team Leader, how would you handle an underperforming employee?"
- Source: GeeksforGeeks
2. Managerial Round
Format: 30 minutes, behavioral and resume-driven.
Common Question Types:
- Project Discussions: Deep dive into past work, technologies used.
- HR Questions: Motivation for joining Razorpay, career goals.
Exact Questions Asked:
- Project Justification:
- Problem: "Why did you choose your college? What did you learn from your projects?"
Key Takeaways
- Success: Strong technical fundamentals, scenario-handling skills, and behavioral alignment.
- Failure: Weak conceptual knowledge, inability to justify decisions, or poor cultural fit.
- Preparation: Focus on OOPs, SQL, scenario-based problem-solving, and behavioral storytelling.
Track: SDE-2
SDE-2 Role-Structured Interview Briefing
Overview
The SDE-2 role at Razorpay typically involves three rounds: a technical coding round, a system design round, and a managerial round. Candidates are expected to demonstrate strong problem-solving skills, OOPs and low-level design proficiency, and scalable system design thinking. Rejections often occur due to incomplete solutions, inability to optimize, or lack of depth in design discussions.
Round Breakdown
1. Technical Round
Format: 45-60 minutes of problem-solving focused on Data Structures, Algorithms, and OOPs. Candidates are asked to solve 1-2 problems and explain their approach.
Common Question Types:
- Tree/Graph Traversals: E.g., N-ary tree traversal, path-finding problems.
- Dynamic Programming: E.g., minimizing maximum difference, path optimization.
- System Design Fundamentals: E.g., designing in-memory SQL, database constraints.
Exact Questions Asked:
-
N-ary Tree Traversal:
- Problem: Traverse an N-ary tree and find the maximum path from root to leaf.
- Constraints: Dynamic children nodes, time/space complexity analysis.
- Source: GeeksforGeeks
-
In-Memory SQL Design:
- Problem: Design functions to add, remove, select, and delete tables, and execute queries like
SELECT * FROM table.
- Constraints: Write pseudocode or partial working code under time constraints.
- Source: GeeksforGeeks
-
Meeting Rooms Problem:
- Problem: Determine if all meetings can take place given entry/exit times and the number of rooms.
- Constraints: Sorting-based solution, optimal time complexity.
- Source: GeeksforGeeks
2. System Design Round
Format: 60 minutes of designing scalable systems. Candidates must choose their approach (language, data structures) and justify trade-offs.
Common Question Types:
- In-Memory Databases: E.g., RDBMS with constraints, primary keys, indexes.
- Notification Services: E.g., scalable systems for push notifications, SMS, email.
- Low-Level Design: E.g., parking systems, expense-sharing apps.
Exact Questions Asked:
-
In-Memory RDBMS:
- Problem: Design an in-memory RDBMS with features like tables, rows, columns, insertion, deletion, update, primary keys, indexes, and constraints.
- Constraints: Follow interviewer’s specification sheet, code on-screen share.
- Source: GeeksforGeeks
-
Notification Service:
- Problem: Design a scalable notification service handling push notifications, SMS, webhooks, and email.
- Constraints: Identify bottlenecks (e.g., rate-limiting, retry mechanisms) and propose solutions.
- Source: GeeksforGeeks
-
Expense-Sharing Application:
- Problem: Design an in-memory expense-sharing app (e.g., Splitwise) with equal/unequal splits.
- Constraints: Ensure extensibility for future features (e.g., percentage-based splits).
- Source: LeetCode
3. Managerial Round
Format: 30-60 minutes of behavioral and technical deep-dive. Focuses on project experience, flaws in past systems, and justification for design choices.
Common Question Types:
- Project Architecture: Explain past projects, identify flaws, propose improvements.
- Behavioral Questions: Handle arguments with seniors, justify technical decisions.
- Technology Trends: Discuss current trends (e.g., microservices, NoSQL vs. SQL).
Exact Questions Asked:
-
Project Flaws:
- Problem: "Identify flaws in your current system and propose a redesign."
- Source: LeetCode
-
Behavioral Justification:
- Problem: "How do you justify yourself in arguments with seniors?"
- Source: GeeksforGeeks
Key Takeaways
- Success: Strong problem-solving, clear communication, and depth in design.
- Failure: Incomplete solutions, inability to handle edge cases, or weak justifications for design choices.
- Preparation: Focus on DSA, OOPs/LLD, System Design, and behavioral storytelling.
Track: Intern
Intern Role-Structured Interview Briefing
Overview
The intern hiring process at Razorpay is highly competitive and multi-staged, combining online assessments (OA), technical interviews, and HR rounds. Candidates are evaluated on problem-solving skills, CS fundamentals (OS, DBMS, OOP, DSA), and behavioral alignment. The OA often serves as a filter, with MCQs testing theoretical knowledge and coding questions assessing practical implementation.
Round Breakdown
1. Online Assessment (OA)
Format: 1.5 hours, MCQs + Coding Problems.
Weightage:
- MCQs: +4 to +5 (varies by paper), -1 to -2 for incorrect answers.
- Coding: +50 per question.
Common MCQ Topics:
- CS Fundamentals: OS, DBMS, OOP, Computer Networks.
- Aptitude/Reasoning: Logical puzzles, quantitative problems.
Exact Questions Asked:
-
MCQs:
- Topics: OS (processes vs. threads, scheduling), DBMS (joins, SQL queries), OOP (polymorphism, inheritance), DSA (time/space complexity).
- Example: "What is the difference between multithreading and multiprocessing?"
- Source: GeeksforGeeks
-
Coding Problems:
-
Problem 1: Decimal sum of binary numbers from 1 to N.
- Constraints: Efficient computation, time complexity.
- Source: GeeksforGeeks
-
Problem 2: Largest triangular subsequence in an array.
- Constraints: Steeper constraints, dynamic programming.
- Source: TopCoder
-
Problem 3: Maximize |A[i] - A[j]| + |i-j|.
2. Technical Interview
Format: 45-60 minutes, resume-driven with a mix of DSA and conceptual questions.
Common Question Types:
- DSA: Array/string manipulation, graph traversals, dynamic programming.
- Concepts: System design fundamentals, database queries, OOPs principles.
Exact Questions Asked:
-
Array Problem:
- Problem: "Given an array, find two numbers from their sum and XOR."
- Source: GeeksforGeeks
-
SQL Joins:
- Problem: Design a query involving
JOIN, GROUP BY, and HAVING.
- Source: Trusted Source
-
Merge Intervals:
- Problem: Merge overlapping intervals in an array.
- Source: Trusted Source
3. Managerial Round
Format: 30 minutes, behavioral and resume-driven.
Common Question Types:
- Project Discussions: Deep dive into past projects, technologies used.
- HR Questions: Motivation for joining Razorpay, work culture preferences.
Exact Questions Asked:
-
Project Justification:
- Problem: "Why did you choose your college? What did you learn from your projects?"
- Source: GeeksforGeeks
-
Core CS Questions:
- Problem: "Explain the difference between TCP and UDP."
- Source: GeeksforGeeks
Key Takeaways
- Success: Strong DSA skills, CS fundamentals, and project depth.
- Failure: Weak conceptual knowledge, incomplete coding solutions, or poor behavioral alignment.
- Preparation: Focus on MCQs (OS/DBMS/OOP), DSA (arrays, trees, DP), and project storytelling.
Track: QA / SDET
QA / SDET Role-Structured Interview Briefing
Overview
The Senior SDET hiring process at Razorpay is highly technical, combining problem-solving, system design, and test framework development. Candidates are evaluated on their ability to design scalable testing systems, optimize algorithms, and communicate clearly under pressure.
Round Breakdown
1. Telephonic Round
Format: 30 minutes, problem-solving focused.
Common Question Types:
- Algorithm Optimization: E.g., stock buy-sell problems.
- CS Fundamentals: E.g., data structures, OOPs.
Exact Questions Asked:
- Stock Buy-Sell Problem:
- Problem: Optimize an O(n²) solution to O(n) time complexity.
- Constraints: Explain approach, trade-offs, and edge cases.
- Source: GeeksforGeeks
2. Technical Round 1
Format: 60 minutes, system design and coding.
Common Question Types:
- Client-Server Systems: E.g., email service design.
- Test Framework Development: E.g., stack implementation with parallel requests.
Exact Questions Asked:
-
Email Service Design:
- Problem: Design an email service in a client-server architecture with server selection logic based on success probability.
- Constraints: Implement core logic, handle edge cases.
- Source: GeeksforGeeks
-
Parallel Stack:
- Problem: Implement a stack that handles parallel requests using synchronized blocks.
- Constraints: Ensure thread safety, explain time/space trade-offs.
- Source: GeeksforGeeks
3. Technical Round 2
Format: 45 minutes, test framework development.
Common Question Types:
- Automated Testing: E.g., writing test cases, executing frameworks.
Exact Questions Asked:
- Test Framework:
- Problem: Develop a test framework for the email service system and execute at least one test case.
- Constraints: Accept all test cases, ensure reliability.
4. HR / Managerial Round
Format: 30 minutes, behavioral and cultural fit.
Common Question Types:
- Work Culture: Discuss preferences, team collaboration.
- Career Goals: Align with Razorpay’s vision.
Key Takeaways
- Success: Strong testing mindset, system design skills, and behavioral alignment.
- Failure: Weak test framework design, inability to optimize algorithms, or poor cultural fit.
- Preparation: Focus on system design, test automation, thread safety, and behavioral storytelling.
Track: SDE-1 / New Grad
SDE-1 / New Grad Role-Structured Interview Briefing
Overview
The SDE-1 hiring process for new graduates at Razorpay is rigorous and multi-staged, combining an online assessment, technical rounds, and a techno-managerial round. Candidates are evaluated on DSA skills, system design fundamentals, and behavioral alignment. The process is highly competitive, with a strong emphasis on problem-solving clarity and CS fundamentals.
Round Breakdown
1. Online Assessment (OA)
Format: 1.5 hours, hosted on HackerEarth.
Components:
- 15 MCQs: OS, DBMS, Computer Networks, OOP.
- 3 Coding Problems: 1 Easy, 1 Medium-Hard, 1 Easy-Medium.
Exact Questions Asked:
-
Coding Problems:
- Problem 1 (Easy): DFS-based problem (e.g., HackerEarth Problem).
- Problem 2 (Medium-Hard): DP-based problem to minimize the maximum difference by removing K elements.
- Problem 3 (Easy-Medium): Recursion-based problem to find the number of ways to go from 0 to N under constraints.
-
MCQs:
- Topics: OS (multithreading vs. multiprocessing), DBMS (abstraction levels), OOP (polymorphism), CN (TCP vs. UDP).
2. Technical Round 1
Format: 45 minutes, problem-solving focused.
Common Question Types:
- String/Array Manipulation: E.g., transforming strings, word ladder problems.
- Graph Traversals: E.g., bi-directional BFS.
Exact Questions Asked:
-
String Transformation:
- Problem: Calculate the minimum number of steps to change
str1 to str2 (variation of a known problem).
-
Word Ladder:
- Problem: Implement a bi-directional BFS to find the shortest transformation sequence from
beginWord to endWord.
3. Technical Round 2 (System Design)
Format: 60 minutes, system design focused.
Common Question Types:
- Caching Systems: E.g., LRU Cache design.
- Scalable Architectures: E.g., notification services.
Exact Questions Asked:
- LRU Cache:
- Problem: Design an LRU Cache from scratch using strong OOP principles.
- Constraints: Explain time/space trade-offs, implement core methods (
get, put).
4. Techno-Managerial Round
Format: 60 minutes, behavioral and CS fundamentals.
Common Question Types:
- Project Discussions: Deep dive into past projects, technologies used.
- Core CS Questions: Hashmaps, NoSQL vs. SQL, multithreading vs. multiprocessing.
Exact Questions Asked:
-
Hashmaps:
- Problem: Explain how hashmaps work, their use cases, and when not to use them.
-
NoSQL vs. SQL:
- Problem: Why use NoSQL databases (e.g., MongoDB) over SQL databases?
-
Behavioral:
- Problem: "Discuss a time you argued with a senior and how you justified your stance."
Key Takeaways
- Success: Strong DSA skills, system design fundamentals, and project depth.
- Failure: Weak CS fundamentals, inability to optimize solutions, or poor behavioral alignment.
- Preparation: Focus on DSA (graphs, DP, strings), system design (caching, scalability), and behavioral storytelling.
Track: Data Science / ML
Data Science / ML Role-Structured Interview Briefing
Overview
The Data Science/ML hiring process at Razorpay is technical and scenario-driven, focusing on problem-solving, domain expertise, and system design for ML systems. Candidates are evaluated on their ability to design scalable ML pipelines, optimize algorithms, and communicate technical trade-offs. The process is moderate in difficulty and involves deep dives into past projects.
Round Breakdown
1. Technical Round
Format: 60 minutes, ML system design and problem-solving.
Common Question Types:
- Document Indexing: E.g., designing a system to index large PDFs.
- Algorithm Optimization: E.g., scalable ML models, feature engineering.
Exact Questions Asked:
- Document Indexing:
- Problem: "How would you index a 1000-page PDF for efficient search and retrieval?"
- Constraints: Discuss scalability, trade-offs, and tools/technologies (e.g., Elasticsearch, NLP libraries).
- Source: Trusted Source
Key Takeaways
- Success: Deep ML expertise, scalable system design, and clear communication.
- Failure: Weak justification for design choices, inability to optimize algorithms, or poor project impact discussion.
- Preparation: Focus on ML system design, scalable indexing, and behavioral storytelling.
Track: Staff / Principal
Staff / Principal Role-Structured Interview Briefing
Overview
The Staff/Principal Engineer hiring process at Razorpay is highly selective, focusing on deep technical expertise, architectural vision, and leadership alignment. The process is resume-driven, with a single technical round centered on project discussions and system-level thinking.
Round Breakdown
1. Technical Round
Format: 60 minutes, project-driven deep dive.
Common Question Types:
- Project Architecture: Explain past projects, justify design choices, identify flaws.
- System-Level Thinking: Discuss scalability, trade-offs, and future-proofing.
Exact Questions Asked:
- Project Explanation:
- Problem: "Explain one of your past projects in detail. What were the key challenges and how did you address them?"
- Constraints: Focus on architectural decisions, trade-offs, and impact.
- Source: Trusted Source
Key Takeaways
- Success: Deep technical expertise, clear architectural vision, and strong project impact.
- Failure: Weak justification for design choices, inability to discuss trade-offs, or poor leadership alignment.
- Preparation: Focus on project storytelling, system design trade-offs, and behavioral leadership.
Track: Product / Frontend
Product / Frontend Role-Structured Interview Briefing
Overview
The Product/Frontend Engineer hiring process at Razorpay emphasizes architectural decision-making, problem-solving, and technology stack expertise. Candidates are evaluated on their ability to design scalable systems, justify tech choices, and handle edge cases in frontend architectures.
Round Breakdown
1. Online Assessment (OA)
Format: 1.5 hours, MCQs + Coding Problems.
Components:
- 20 MCQs: Multiple Choice Questions covering frontend technologies (React, JavaScript), DSA, and CS fundamentals.
- 2 Coding Problems: Medium-level LeetCode problems.
Exact Questions Asked:
- Coding Problems:
2. Technical Round 1
Format: 60 minutes, frontend and DSA focused.
Common Question Types:
- Data Structures: E.g., linked lists, trees.
- Frontend Technologies: E.g., React, Spring Boot, Java.
Exact Questions Asked:
-
Linked List Problems:
- Problem: Detect a loop in a linked list.
- Problem: Find the intersection node of two linked lists.
-
Matrix Traversal:
- Problem: Zigzag traversal of a matrix.
-
Tech Stack Justification:
- Problem: "Why was React chosen over Angular for your project?"
3. Technical Round 2
Format: 60 minutes, problem-solving and frontend architecture.
Common Question Types:
- Array/Graph Problems: E.g., finding duplicates, Kadane’s algorithm.
- Frontend Architecture: E.g., state management, API design.
Exact Questions Asked:
-
Array Problems:
- Problem: Find the non-duplicate number in an array.
- Problem: Find duplicates in sorted/unsorted arrays.
-
Kadane’s Algorithm:
- Problem: Find the maximum sum subset/subarray in an array.
4. Managerial Round
Format: 30 minutes, behavioral and Hiring Manager feedback.
Common Question Types:
- Scenario Handling: E.g., "How would you handle a situation where your feature fails in production?"
- Company Fit: Discuss alignment with Razorpay’s product vision.
Key Takeaways
- Success: Strong frontend expertise, DSA skills, and architectural thinking.
- Failure: Inability to justify tech choices, weak problem-solving, or poor behavioral alignment.
- Preparation: Focus on React/Spring Boot, DSA (arrays, linked lists), and frontend architecture.