Angel One SDE-2 Interview Experience- Bangalore

Over the last two-three months, I’ve given almost a dozen interviews. As a way of giving back to the community, I’ll be sharing my interview experiences. I hope they’ll be helpful to others who are preparing for interviews or navigating the job search. All the best, and happy interviewing!

I applied through LinkedIn Easy Apply, and the recruiter reached out to me. He scheduled my next round for the following day. There were three rounds: Coding and Problem Solving, Design, and Managerial. All the rounds were elimination rounds. The entire interview process, from the recruiter’s initial outreach to receiving the offer, took just one week.

Round 1: Coding and Problem Solving

It was a 60-minute round that began with a brief introduction from both of us. The interviewer then gave me two coding questions to solve.

1. Given an integer array nums, return the length of the longest strictly increasing subsequence. Example:

Input: nums = [10,9,2,5,3,7,101,18]

Output: 4

1. There are n gas stations along a circular route, where the amount of gas at the ith station is gas[i].

You have a car with an unlimited gas tank, and it costs cost[i] of gas to travel from the ith station to its next (i + 1)th station. You begin the journey with an empty tank at one of the gas stations.

Given two integer arrays gas and cost, return the starting gas station's index if you can travel around the circuit once in the clockwise direction. Otherwise, return -1.

Example:

Input: gas = [1,2,3,4,5], cost = [3,4,5,1,2]

Output: 3

Round 2: Design

He asked me to explain one of my previous projects in depth, including all the design patterns I had used. He then asked me about the SOLID principles and how I had applied them in my project. After that, he gave me an LLD problem to solve:

Design the core of a GTT order system for a broking app. A user sets a trigger on a stock, such as: “If RELIANCE falls to ₹2,400 or below, place a limit BUY of 10 shares at ₹2,405.”

The system watches the live price feed and places the order automatically when the trigger condition is met.

Follow-up questions asked by the interviewer:

1. How should we design the APIs and request models for creating a GTT order and a normal stock order?
2. Can we reuse the same request model for both normal orders and GTT orders?
3. How can we determine whether an API request represents a GTT order or a normal order?
4. How does the system route a request to the GTT workflow when a GTT order is selected?
5. Can we handle both normal and GTT order creation through a single API endpoint? What are the trade‑offs?
6. How would you write the pseudocode for a common controller that handles both normal and GTT orders?
7. Which design patterns would be suitable for this system, and why?
8. How does the Strategy Design Pattern work in this system? Explain the code step by step.

Round 3: Tech + Managerial

He asked me to explain the high-level architecture of one of my projects in detail. He then asked me the following questions:

1. What is the purpose of observability in my project?
2. Where and how I configured alerts?
3. Which system-level metrics I used to monitor for APIs, message queues, workers, and downstream services?
4. Is API response time measured using average latency? What are the different latency metrics I used?
5. What is P95 latency, and why is it important?
6. How did I monitor HTTP status codes and configured alerts for API errors?
7. How I leveraged AI for my project? (In depth detail)
8. What is the purpose of a system prompt, how are tools used by an AI agent, and how do they work together?
9. Difference between a user prompt and system prompt.

Then, he asked me 5–6 behavioural questions.

After 30 minutes, the recruiter informed me that all my interview feedback was Strong Hire, so no further discussion was needed. He asked me to submit the required documents, and I received the offer the very next day.

Verdict: Selected

Note: This was the best interview experience I’ve ever had. The recruiter was also one of the best I’ve ever interacted with.