Online test
The process started with an online coding test sent a few days after filling out the application form for the SDE role.
Platform: A standard coding platform with an integrated editor and test cases.
Duration: 90 minutes.
Pattern:
2 data-structures/algorithms coding problems (arrays / strings / trees, typical medium level).
5–8 MCQs on time–space complexity, OOP, and basic DB and OS concepts.
Example questions:
Implement an LRU-style operation or sliding-window problem.
Given an array, compute something with constraints that force you to use prefix sums / hashing.
Evaluation:
Visible sample tests plus hidden tests.
Needed to pass most hidden tests to be shortlisted for interviews, so edge cases and complexity mattered.
Two days later, an email confirmed that the test was cleared and scheduled the first technical interview.
Technical round 1 (DSA + core CS)
This round was with a senior developer over video, using a shared coding editor.
Focus areas:
Coding:
2 DSA problems (one easy, one medium).
The interviewer looked at:
How the problem was understood and clarified.
Whether brute force was discussed before moving to optimal.
Code correctness and readability.
Topics seen:
Arrays, hash maps, stack / recursion.
Complexity analysis for the final solution.
Follow-up questions:
How would the solution behave for very large inputs.
Possible optimizations or trade-offs (e.g., time vs memory).
CS fundamentals:
A few quick questions on:
Difference between process and thread.
What happens when you type a URL in a browser (high level).
Basic OOP: encapsulation, inheritance, and an example from past projects.
The round ended with a quick chance to ask about the team and tech stack.
Technical round 2 (System + project deep dive)
The second technical round was more design- and project-focused, with a different engineer (often a team lead).
Main parts:
Low-level / API design:
Design a small feature or service, e.g., a URL shortener or a basic task management API.
Discussed:
Data models and tables.
APIs and request–response flow.
Handling scale at a high level (caching, indexing).
Code walkthrough:
Asked to walk through one of the main projects from the resume:
Problem the project solved.
Key design choices and trade-offs.
Testing and performance considerations.
Behavior inside tech:
Questions like:
A time when a bug took very long to find and how it was debugged.
A disagreement on a technical approach and how it was resolved.
The interviewer assessed clarity of thought, ownership of code, and how feedback is handled as much as raw coding skill.
HR round
The final round was with HR / a recruiter, mostly behavioral and fit-focused.
Typical areas:
Motivation:
Why SDE, why this company, why this tech stack.
Short-term and long-term career goals.
Culture and values:
Questions using the STAR pattern:
A time you worked in a team with conflicting opinions.
A failure and what was learned from it.
Handling stress or tight deadlines.
Practical details:
Preferred joining date, location, and work mode.
General salary range and expectations, but final numbers usually come with the offer.
The round was conversational; the main expectation was honesty, clarity, and alignment with company values.
