Cars
51m
216
Which is the best car of all time?
Tech Industry
19h
1694
Why doesn't OpenAI offshore and reduce expense by 80%
Tech Industry
3d
41397
What happens when most of your team is Indian?
Tech Industry
5h
778
Question about women in their 30’s?
Tech Industry
6h
712
The man I love hates me because I’m Vietnamese
People who come for design interviews. Don’t panic. It is no different than your every day conversation with your coworkers 1) Don’t dive deep too early. Your success doesn’t depend only on an architecture diagram. 2) You DO NOT need to cover everything. 3) Understand what is asked by asking questions. Spend 5 minutes interviewing the interviewer why he wants a certain problem, what is the purpose, if you don’t get the answer, pick an answer and document as your assumption 4) when asked to develop an app, you own the requirements so start defining those, don’t ask the requirements. Drive the discussion here as a product owner. This is your chance to take the ownership of how interview needs to go. 5) Understand and define a small population of your customer and focus on that 6) Architraves diagram should be 1/3 of your interview 7) if you have not used a tech, talk about how you think this can work, don’t just mention a tech and try to quickly move on. Interviewer will dig any tech you mention 8) stop trying to use document Db, cache, load balancing, just because you have to. Understand the use case of each. 9) if interviewers interrupts to ask a question, listen carefully. Nobody is looking to get answer in next second, understand why questions is asked and what interviewer wants to get to. Dive deep on question. Don’t just throw the solution. We want to know your thought process, not the name of the tech. It hurts me seeing how smart and technical folks mess up the design interview trying to hurry and go deep. Biggest issue I see in design interviews ? Interviewees just think a complicated architecture diagram will get you a success. Good question from a Microsoft person. So adding my answer here WHO I WOULD PICK TO HIRE IN DESIGN INTERVIEW Someone who touched on all areas in a structured format with composure and knows what he/she/they doesn’t knows. It will go something like this - Goal of the app - Metrics of success (business and tech) - Key User base - Lisy of requirements (all features you can list quickly) - MVP out of requirement form above - Data / APIs for few requirements - Architecture diagram - Scaling up / down option (might skip this) Based on role or level, any of these we might go deeper. Then I would change the major requirement and see how you react to it. Don’t necessarily have to find an answer, but being able to think on the fly. (THIS IS JUST MY OWN GUIDELINE). I might hire someone who missed some of those or hire someone who didn’t miss anything. Depends on tech depth as well, not just touching on these.
Is it safe to start small then scale up ? Also does this applies for product/api design?
Yes and yes
@Met@Meta i also wanted clarification on this as the design i.e databases and services will be different for 100 number of users and as we scale it will be different for billions of users. We won't have that much time right in an interview also i do not know if we should jump to billion users from the start as in real world we start small and then scale. Also how I can determine that for this many number of users SQL db will not be work? And now it's time to move to nosql
The whole point of interviews is to cause panic
No. The point is to see how you handle pressure and what is your thought process and technical depth
Won't you have to create pressure to check how someone handles pressure?
Thanks for detailed write up.
Sure . I hope it helps someone
How do you view nervous interviewees who are blanking out or are just really nervous. Is it understandable or taken into consideration as "not being able to handle pressure" ?
I will try to calm you down, make couple jokes. I am spending an hour with someone, I want that person to succeed and make my time worth. But if some doesn’t bounce back and control the conversation then I am not sure I want to work with that person in real pressure situation at work.
That's product design. Tell us about system design too please.
I see no difference. To have a good system design you really need to understand product, customer, use case and goal. System design is nothing without those
I agree but system design can be more technical.
I wish i will get interviewer like you for my upcoming Meta interview
Good luck
How's your preparation going? What's your leetcode profile like?
Am I having a stroke or is this post devoid of certain words like “the”?
It does. I can always get away with “Not my first language” or one out of 4 languages I speak .
Thanks @Dragos very useful stuff
So are you doing interviews in march?
That’s my secret cap, I am always interviewing
Do the level of the interviewer depend on the level of the candidate or it doesn't matter? Also if i choose a given language for coding is the interviewer required to understand that language?
May I also suggest extending the design interview length to 1 hour as Google does since WFH?
There are Buffers always
please THANK YOU!!
??
No body took the time to explain this before, so thanks!!