Interview Questions

Agni W. - "Interesting questions. Thank you for asking it. S: Suppose I want to add notifications service to an app that provides user directed content, that is is dependent on user's past preferences T: if you ask me for a prototype, then I would use API gateway/ LB, Lambda, storage in SQL and No SQL both, have caches. later we could use CDN, have EC2 instances to run the app. We could deploy Kafka pipeline also. Create notification service on the existing app. - that will be a micro service A: Since"See full answer

Anuradha T. - "Clarifying questions: What kind of users are we talking about? Internal or external ? (Assumption: External) When was this issue discovered? (Not so long ago) Is this specific to a particular geographical location ? (Answer: No) External: Geography, time ? Internal: Pain points: Technical - latency, lag Engagement - Less engagement available on website , users are bored while waiting for their search results to appear Review - Explore platform options for users to review their experie"See full answer

Keval B. - "I would evaluate by comparing the results of old and new ranking algorithms, based on number of false positives."See full answer

Jax H. - "Let’s pick SFO (because it's a stupid choice.. probably easier if you pick a smaller airport) We know each passenger has to go through the scan at least once We can assume 10% of passengers go through twice People only go through scans when they depart but not when they arrive International planes are bigger so carry more people so need to calculate separately Approach Estimate how many gates there are Estimate airport operation hours Estimate the numbe"See full answer

Tanu M. - "I always look at the project from three angles, Scope, Schedule, and Cost. To measure the success of the project we also have to look at the other factors, other than the scope, schedule and cost. Here are some of the factors I look at while measuring the success : Metrics : While defining the Goal of the program, we also define the metrics. To assess whether the goal is getting achieved or not, we need to measure the metrics i.e whether the metrics of the program are getting hit or not. For e"See full answer

Shahrukh K. - "When I transitioned from the Analytics team to the Product team, I faced challenges in gaining the trust of the engineering team. Having previously worked with them in a role where I provided insights rather than defining their priorities, they were initially hesitant to accept my inputs in my new role. This led to some misalignment, as they chose to focus on tasks independently rather than incorporating my recommendations. Recognizing the need to build credibility, I took a proactive approach."See full answer

Ash K. - "Below is the step by step approach I would take: Identify potential risks: Firstly, I thoroughly analyze the project and identify potential risks that could impact its success. This involves reviewing project documentation, conducting stakeholder interviews, and seeking input from team members who have expertise in different areas. Assess the impact and likelihood: I evaluate each identified risk by assessing its potential impact on the project objectives and determining the likelihood of"See full answer

Lee J. - "don't you need something like the below in the select clause SUM(rides) AS total_rides SUM(deliveries) AS total_deliveries "See full answer

Rev - "Acquisition: #DAU, #MAUs Engagement: listening duration #songs liked/ shared/ added to playlists from the recommendation list #times recommended songs are listened to Benchmark the above with original metrics (before implementing the change) "See full answer

Anonymous Dingo - "Here’s a commonly used Git branching and release strategy that we used at my previous role: Branching strategy (Git-based) a. Main Branches main: Production-ready branch. Only tested and stable code is merged here. develop: Feature branches are merged here before being merged into main. b. Supporting Branches Feature Branches (feature/) Release Branches (release/) Hotfix Branches (hotfix/) 2.Release Strategy a. Continuous Deplo"See full answer

Tiago R. - "function permute(nums) { if (nums.length <= 1) { return [nums]; } const prevPermutations = permute(nums.slice(0, nums.length-1)); const currentNum = nums[nums.length-1]; const permutations = new Set(); for (let prev of prevPermutations) { for (let i=0; i < prev.length; i++) { permutations.add([...prev.slice(0, i), currentNum, ...prev.slice(i)]); } permutations.add([...prev, currentNum]); } return [...permutations]"See full answer