Intuit SDE2 interviews
Anonymous User
2599

YOE: 2
Role: SDE2 in platform team working majorly with kubernetes
Had 4 onsite interviews back to back for sde2

**Phone screen- **

Given a graph of memory and a pod in crshback loop, tell your steps to debug. It was a graph with slowing increasing memory and then sudden drops.
Ans - its a memory leak. Then further asked reasons for memory leaks, how to debug it further.
1 simple DSA question.

Assignment -
Create a microservice to read from a db (use a csv for now), and expose 2 APIs to get all and get by id. Expose another API for rate limiting. Also create scripts for packaging as a docker image.
Did the assignment in golang since the team used golang heavily.

Interview1:
Had to present the design, code, demo of the assignment. Follow up questions on how paging can be done in APIs, how paging is done in sql db. Then another follow up question that went into system design. How to do rate limiting when you have multiple instances of the service running. Presented a external queue based async method. Then a load balancer based solution. Then we went into algorithms used by distributed in memory dbs. there was no pre-decided question with fixed answer. Questions were branching off from what I told them,

Interview 2:
2 easy DSA questions. Dont remember now. But leetcode medium is what can be expected.

Interview 3: (had to be the last round but happened before)
HM round: Asked about some situation where I had to use by debugging skills. Branched off into how to do db migrations without downtime. Pretty openended discussion with no fixed answer. Spent half the interview asking him questions about the team and work.

Interview 4:
Given the keyapd of the old design phones, and a string having numbers, give all possible combination of letters that can be formed
1 -> abc
2 -> def
12 can form ad, ae, af, bd, be ,bf ....
Asked questions around k8s.

  1. What can cause a pod to go in crashloop backoff state
    1. difference between liveness and readiness probes.
  2. Something about the db used by k8s (didnt know).

Verdict- selected. But the role got closed by the time my formalitites could complete. Waiting for another team matching round.

Comments (4)