RESTful APIについてのアプローチ、素晴らしいですね！EchoAPIを使ってエンドポイントのレスポンスをシミュレートすることで、問題を早期に発見でき、テスト環境に対する自信が大きく向上しました。

It's good. But is an interview this long in 2024? I'm used to using star concisely with a specific example.

I was expecting STAR model response.

sh asked many question after her last QUESTION..LOL

“Google, Facebook, Amazon, and other STARTUPS” 😂 Great videos overall! 🙏🏽

Good video! For KZbin scale, I am sure load balancers and GeoDNS are a good idea. These should be included in the design. Good detail from the mock interviewee here about the video upload, separation of concerns, storage and compute. Surprising that search of videos was not considered as a feature at the very start. It is an important feature! :)

Pretty weak design, not the de facto standard of how to put in a flowchart, this video kinda feels unrealistic..

which website he used for designing?

This is just mock interview, pretty much scripted. An 8+ years experience guy talking about system design architecture is a joke. Why do we need NFRs to design a system design architecture. Either he must have by hearted it or copy paste of from somewhere.

I loved this video, it is perfect, straight to the point and content is exactly what I wanted to hear. You've +1 subscriber

She looks like an AI

❤❤❤

Could you guys please make these interviews easier to understand? It seems to confuse more than make understand.

Is she AI ?

How do I prepare for this as a fresher intern with no prior work experience?

interview went on so smooth

"Tell me about" ... ? Does anyone pay attention to the following impact: 1. An event 2. A pattern (mastery) 3. An underlying structure (culture) 4. A vision (leadership) 5. A mindset (research logic, thinking skills: system, critical, lateral, disruptive, question, inversion, scenarios/evolution, etc) 6. Spiritual experience (something extraordinary/divine) happened. Instead of STAR try (I)SBAR (Ask the interviewer, too): I-Issue/Challenge S-Situation, facts only B-Background/Context A-Assessment R-Recommendation Execution is another matter. Results in STAR should be further probed with R.O.I.: R-Immediate "R"esult O-"O"utcome, what change had to be made to support "R" I-Long term "I"mpact For example, two technicians plus an engineer resigned. After a "small" change I made, for the next two years (until the end of my employment), the company never employed those three roles. Was it a small change? If I did nothing else, until I left, the change covered the cost of all my salaries and much more? In your interview, ask Amazon: How have you got rid of "I am right you are wrong" paradigm? (How) Do you practice Lateral/Disruptive Thinking? What have you learned?

Formal framework for defect is assigning severity to defect. All severity of 1 must resolved without question. Deadline has to move.

Amazing and very helpful

1. Google 2. Facebook 3. LinkedIn 4. Uber 5. Lyft 6. Coinbase 7. Twitter 8. Yahoo 9. Asana 10. Salesforce 11. Atlassian 12. IBM 13. Yelp 14. Workday 15. Intuit

Condition #3 seems to be redundant. If every node (excluding the root) has exactly 1 parent and there is exactly 1 root, then a cycle cannot exist because by definition a cycle contains 1 point with 2 parents.

"There's a decline in add-to-cart action" "Is the button working?" "Not working in the android app" "Then fix the button"

So this guy came up with all this on the fly without any prior knowledge of Prime other than being a user? 🙂But good pointers for a mock interview.

If you are a product manager : What do you do if your product his shit?

Very useful video, Thank you :)

thanks Kevin!

This was beautiful! Proving your algo works with test cases is just the best thing any dev can and should do.

She's so beautiful, I watched the interview twice and don't remember what she said.

this felt like a manager teaching its subordinate, lmao!

Thanks

I had to go back to the start of the video because the interview question seemed to have changed halfway through. This is not a root cause analysis, the question tells you explicitly that the metrics came from launching KZbin comments on mobile devices. The interviewee spent almost the entire time on root cause when she should’ve been identifying the North Star metric and setting up an A/B test to validate her hypothesis. Weak answer IMHO, please don’t follow this format if you’re asked an execution tradeoff question during your interview!

Seems like a KT session about message queue.

Smart pointers are there

Thanks

why are create account, and login internal endpoints? aren't they called externally from the client UI?

Thanks for providing such a great example! I recently completed the 2-sum problem and was excited to quickly find the approach of assuming one element as part of the target combination. This simplifies the problem into a 2-sum problem. It’s also fun to consider how the optimal solution shifts when the problem evolves from 2-sum to 3-sum. For instance, hashing, which offers O(n) time complexity for 2-sum, is no longer the best choice for 3-sum because we inevitably need at least O(n²) time due to the additional loop. This makes the pointer-based approach, with its O(n log n) sorting overhead, more feasible and efficient. It’s intriguing to see how the nature of the problem changes the optimal solution.

wait you are a PM?

Thanks!

Hi Neamah, I had seen your 2 videos APIs and system interview and found them excellent as it seems to be well prepared. Please keep this up to facilitate people. again excellent content with excellent delivery in a very short time

Interesting scenario but the video is too long without any timestamp to navigate through it, it gets interesting around 30 mins into the video

if (progress > 100 ) progress = 100; if (progress < 0 ) progress = 0;

I'd love to have a manager like Dave.

This is how I might approach this: First, there are three stakeholders to handle here, the sales team, the customer and the engineers. For the sales team, is this an approach that’s consistent with the sales team to go to the engineers to request a feature or it’s just a one off. For the customer, what rank are they in in our northstar, are they clear winner or just bigger in another metric . For the engineers, do they usually accept this request ? Or a one off ?

hi Neamah, excellent. very well explained within 4 minutes. love this

So much to learn or reinforce on this conversation 😬👏👏🙏🏻🙏🏻

Brilliant. Completely brilliant. Learned a lot from this Mock on approaching a product question and progressing with a very clear dictation of thinking processes. However, I stumbled upon one thing. The prioritisation in the solution part. Production effort wise, it makes sense that the other two solutions would be more than the setting up of the reminders. But in case to validate which to prioritise based on what effort which solution would make, I would have started the experiments with two solutions: Reminders and Support Groups. Experiment wise also, effort looks a lot but for a selective user segment this could have been achieved. I would have experimented the Support Groups solution by creating groups on external app like Slack or Discord and setup a process where I would ask the peers to nudge each other to do the meditation everyday. Because that statement hit me hard, "It's much more difficult to disappoint others than disappoint yourself". This has a lot of value. I would have run both the experiments for two different set of user segments of the same persona for a few duration say a few weeks or a few months. Get the report of which experiment benefitted the most wrt engagement and then I would have taken a call to prioritise a solution. Nonetheless, I liked the feedback provided by Kevin as well. His feedback on making the interview experience vibe positive even for those who might not be in a mood to take interview just made me learn a lot. Brilliant feedback from Kevin. Thank you so much for sharing these mock experiences.

No framework in his answers. Seems all over the place

midlevel at best :-) Thanks for the video