AGENT VIEW · Mokabla · Question · system-design-caching-round
AgentGate · request ag_03a2d13afdff

Who you are, as far as this app can tell

declared   ClaudeBot · Anthropic   · not verified

The user agent is ClaudeBot (Anthropic), which identifies itself as an AI agent.

Signals: Known agent user agent

This classification is final for the session. The human pages are not served to agents.

This page

page
question
human URL
https://www.mokabla.com/en/c/thndr/system-design-caching-round

State

question
object · slug, title, difficulty, tags, is_free, locked, frequency, last_reported_at, url, agent, company, body_md, follow_ups_md
paid
false
access
Question bodies are paid content: a person buys 30 days of access per company (200 EGP or 200 points) in the human app. Agents get titles, tags and difficulty; bodies only for free questions.
{
  "question": {
    "slug": "system-design-caching-round",
    "title": "System Design and Caching Round",
    "difficulty": "hard",
    "tags": [
      "system-design",
      "technical",
      "backend"
    ],
    "is_free": true,
    "locked": false,
    "frequency": 0.333,
    "last_reported_at": "2026-03-16T12:14:16.653568Z",
    "url": "https://www.mokabla.com/en/c/thndr/system-design-caching-round",
    "agent": {
      "page": "https://www.mokabla.com/agent/en/c/thndr/system-design-caching-round",
      "question": "https://www.mokabla.com/agent/_call/get_question?company=thndr&question=system-design-caching-round"
    },
    "company": {
      "slug": "thndr",
      "name_en": "Thndr"
    },
    "body_md": "## What they ask\n\nThe technical interview is mainly system design, with side questions on databases, caching and optimization, and an emphasis on reliability and data consistency because the product moves real money.\n\nPrompts in this area, for example:\n\n- Design the live market data feed: prices for a few thousand symbols pushed to hundreds of thousands of app users during trading hours, with a latency budget of a couple of seconds.\n- Design the portfolio and money-movement flow: deposits, withdrawals, buy orders, and a balance that must never go negative or double-spend.\n\nSide questions reported: which cache to use and how to invalidate it when a price changes; when a read replica is enough and when it is not; which indexes you would add to a trades table; what ACID means for a transfer between two accounts; how you would find a slow endpoint.\n\n## What they look for\n\n- Fan-out design for the feed (pub/sub, WebSockets or SSE, batching, backpressure) and a story for clients that disconnect.\n- Transaction safety for money: idempotency keys, ledger-style append-only records, isolation level choices, reconciliation jobs.\n- Practical caching: what is cached, TTL vs event-driven invalidation, stampede protection.\n- Trade-off talk; they push on \"what breaks first\" and \"what do you monitor\".",
    "follow_ups_md": "- How do you keep balances consistent if the order matching service and the ledger are separate services?\n- Where would you put a rate limit, and what would you rate-limit?"
  },
  "paid": false,
  "access": "Question bodies are paid content: a person buys 30 days of access per company (200 EGP or 200 points) in the human app. Agents get titles, tags and difficulty; bodies only for free questions."
}

Actions you may take here

actioninputpermission
get_question
One question with its body. Bodies are paid content unless the question is free.
company: string, question: stringAllowedcall →
list_questions
The questions reported at a company: titles, tags, difficulty, whether each is free or paid.
company: string, page: number?Allowedcall →
buy_access
Buy 30 days of access to a company.
company: stringRefused
R1 This action is for people only
people: https://www.mokabla.com/en/pricing
post_comment
Comment on a question.
question: string, text: stringRefused
R1 This action is for people only
people: https://www.mokabla.com/en/companies

Allowed actions answer in JSON. Add ?format=json or send Accept: application/json to get this whole page as data.

Navigate (pre-filled links you can follow)

Notices

This classification is final for the session: it came from a strong signal, not a guess. The human pages are not served to agents.
Unverified agents are read-only. Signed requests (Web Bot Auth) are the path to write access.