**Status**: Experienced, Amazon/Atlassian/Startups\n**YOE** : 6.5\n**Position**: L7 Sr. SE at Rippling\n**Location**: Bengaluru, India\n**Date**: February 13, 2024\n\n**Interview experience**\nRecruiter Phone screen (1 hour):\n - Reason for lookout\n - Technologies I have worked with\n - Experience\n - How would you design a deployment system\n - How would you monitor a system\n\n\n**Tech Screen Design Round**\nProblem: Design a News Aggregator\n\n**Onsite**\n**System Design**: Design an event tracking system like amplitude\n\nThis was interesting problem because the interviewer gave me a lot of requirements before hand - sdk, servers, database, query, chart render etc.\nI gave a few sub-optimal solutions for a few components and could not discuss all the requirements.\nWhen there was 5 minutes left I took the opportunity to talk about all the missed components at a high level and also touched points on observability - metrics, logging, tracing. I also mentioned on-call alerting, incident, SOPs, scalability, problems with retries bottlenecks.\nI believe this helped me get through the interview\n\n**DSA**: Write a KV in memory store\nThe interviewer gave a relatively simple problem initially with only save and delete operations and then later added commit, rollback (transaction)\n\n**Hiring Manager**\n\nThis was a cultural round - can you talk about time when XXXX. Have you been mentored, have you mentored people. General situational questions.\n\n**Project Presentation**\nI was asked to prepare a presentation on one of the projects that I have worked on in previous companies. They expected highlevel architecture, project impact, etc. The interviewer was impressed in this round because I took a practical approach of presentation. Instead of presenting it to be something cutting edge I explained him that this is something that every big enterprise does.

Status: Experienced, Amazon/Atlassian/Startups\nYOE : 6.5\nPosition: L7 Sr. SE at Rippling\nLocation: Bengaluru, India\nDate: February 13, 2024\n\nInterview exp