Coding or system design, a problem from the library, and the level you're aiming for. The level sets what Mambo expects of you.
Mambo knows the problem's details but never volunteers them. Ask, and it answers exactly what you asked.
How many new links a day, and do they expire?
In system design, a shared board fills in as you talk, dashed until you commit. In coding, you write in an editor and Mambo reads along.
Mambo stays neutral and never says whether you're right. Miss something that matters and it nudges, broad first, then closer.
Then I'd just add a cache.
Why?
End when you're ready. A minute later: a hiring verdict, what to fix first with the line that earned it, and how you came across.
Name the trade-off when you choose a database.
“I'll use a NoSQL store because it scales.”
Calm and organised. You asked about scale before drawing anything, which is what interviewers hope to see.
Mambo is invite-only. Ask the admin to add your Google email first.