I hope this will be helpful for the people preparing for linkedIn interviews

Exp: 4.8y (startups)

Round 1: Dsa postponed multiple times

• k points near origin (2D space)
  • extended into any point in the 2D space, asked how will I approach?
  • Solved it in 20mins, approach for any point -> approximate n nearest neighbor
• Similar to LRU Cache (don't remember question properly)

Round 2: Dsa postponed multiple times

• question similar to diameter of tree with n children
• check if two linkedlist merges?
  • check if endpoint is same for (lists without cycle)
  • check if any list has cycle ( then both should have cycles, and 1 point on first cycle should be present in another )
  • extend to figuring out the cycles , and also the starting point in the cycle

Round 3: HLD

• Design KV store
  • Didn't followed any yt, sys design structure
  • started with purpose
  • storage, compute
  • sharding etc

Round 4: HM

• Asked about Previous Experience
  • Has less scale in my prev startup but built the product from scratch to profitable
  • I can sense he got disinterested because of scale.
• Design and tradeoffs,approaches
• how do you evaluate pocs?
• explain any scenario where you had design decisions with your peers and they didn't went ahead with your proposed approach
• Design Job Scheduler

Verdict: Reject

• good for high level SDE2 but not SDE3

R1,R2 are strong hire but R3,R4
I got feedback that the discussion should be structure and also work on projects with high scale and reappear for linkedIn interviews again.

Overall: The experience is good.

• Prepare prev leetcode dsa
• prepare common hld design questions

Currently reading DDIA, and following hello-interview and is helping HLD interviews but still HLD interviews are depressing :(. Seems like it is based on luck or just go over all the designs on any sys design site or yt
and jabbering it for imaginary scale.

But DDIA is fun :). I love that book