Hey any idea what to expect with this one? It's not distributed systems...
Wierdest interview I faced so far. Probably because I didn't know what to expect. So let me help you out. 1. You are writing a service which returns a static text banner. It is used by internal developers. How will you design its api ? Interviewer remained silent most of the interview with a wierd expression on his face. Was very careful not to steer me in right direction. Oh well.
OP what kind of question did you end up getting?
+1
Can you please share your experience? I have one day after tomorrow
I was asked to design a system that 1. Accepts and saves a text post from FB for 1B+ users 2. Once the post is stored (no time limit), build search capability across all FB users (assume all posts are public-ably available) - Scale is very important - Think about effective caching strategy - Post processing - once the text is stored in a db, data needs to processed before it’s searchable.
2024 Tax
11h
1882
Biden’s new tax proposal is wild
Cars
Yesterday
2016
Why are Americans obsessed with SUV?
Tech Industry
18h
2468
Go woke, go broke: Google fires 28 employees involved in pro-Hamas protest
2024 Presidential Election
3h
1051
Biden ruined America and tech! Tax plans are insane
Personal Finance
Yesterday
3078
IRS took 73K 😭
I haven’t interviewed at FB, but I’d start with the graph API and actions you can perform on each of the entities. Example: photos. How would you design the graph API to look up photos that belong to a user? Photos a user is tagged in? Photos a user’s friends are tagged in? Users tagged in a photo?
Is graph api just a normal rest api but with circular connections or when you say graph api you mean to say something like use graphql or similar to do that?
It’s publicly documented. I’d suggest starting there and getting a feel for their conventions.