Loading Question...
Jobra drops you into a broken repo. Find it, fix it, ship it. AI helps you debug like on the job.
Jobra drops you into a broken repo. Find it, fix it, ship it. AI helps you debug like on the job.
Round 1: DSA
The first round was entirely focused on DSA and problem-solving. The interview invitation email included a link to their coding platform. Once I opened the link and joined the session, the coding question was already displayed on the codepad.
Question 1: Trapping Rain Water (LeetCode-style problem)
The interviewer explained the problem, and before jumping into coding, I asked about the constraints and edge cases to understand the problem better.
The interviewer was quite friendly and interactive throughout the discussion. He also provided hints whenever required, making it more of a collaborative problem-solving discussion rather than a one-sided assessment.
Question 2: Median of Two Sorted Arrays of Different Sizes
This question focused primarily on arriving at the optimal solution.
The interviewer was particularly interested in understanding my thought process, reasoning, and approach at every stage. It wasn't just about reaching the final solution; I had to explain the logic behind every iteration and loop.
Key takeaway: Be prepared to explain your approach at every step. Understanding the optimal solution is important, but being able to justify why it works is equally important.
Round 2: Machine Learning & Resume-Based Discussion
The second round was primarily focused on my resume and technical fundamentals.
The interviewer explored my projects in detail, asking questions about the underlying concepts, implementation choices, and technical decisions.
Last updated Nov 10, 2026
The discussion covered a broad range of topics across:
Machine Learning: Core ML algorithms, fundamentals, and conceptual understanding.
Deep Learning: Neural networks and their underlying concepts.
Natural Language Processing (NLP): Fundamental concepts and related techniques.
Resume-based questions: In-depth discussions around projects, their architectures, implementation details, and the reasoning behind technical choices.
The round tested both the breadth and depth of my understanding. Having projects on your resume is one thing, but being able to explain every technical decision and defend your implementation is what matters.
Tips: Final takeaway: The interview process was a good experience, especially the first round, where the interviewer was friendly and encouraged collaborative problem-solving. My biggest learning was that strong fundamentals and the ability to articulate your reasoning matter just as much as getting the code right.