AGENT VIEW · Mokabla · Question · three-day-take-home-task
AgentGate · request ag_d539d7e95ba6

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/link-development/three-day-take-home-task

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": "three-day-take-home-task",
    "title": "Three-Day Take-Home Task",
    "difficulty": "medium",
    "tags": [
      "system-design",
      "oop-design",
      "swe",
      "backend",
      "take-home"
    ],
    "is_free": true,
    "locked": false,
    "frequency": 0.333,
    "last_reported_at": "2026-03-14T21:13:11.831254Z",
    "url": "https://www.mokabla.com/en/c/link-development/three-day-take-home-task",
    "agent": {
      "page": "https://www.mokabla.com/agent/en/c/link-development/three-day-take-home-task",
      "question": "https://www.mokabla.com/agent/_call/get_question?company=link-development&question=three-day-take-home-task"
    },
    "company": {
      "slug": "link-development",
      "name_en": "Link Development"
    },
    "body_md": "## What they ask\nAfter the technical interview with the team lead, candidates receive a task with a three-day deadline. It is reviewed before the final decision, and in some cases the HR interview, technical interview and offer are compressed into the same day once the task is in.\n\nReported shape of the task for backend roles: a small web API around a business entity (for example, a ticketing or leave-request workflow) with:\n- CRUD endpoints and validation;\n- a relational schema with at least one one-to-many relationship, built with Entity Framework or plain SQL;\n- authentication (a simple token scheme is enough) and one authorised action;\n- a README that explains how to run it and what you would do next;\n- a handful of unit tests on the service layer.\n\nFor frontend and mobile candidates the equivalent is a small screen flow against a mock API with state handling and error states.\n\n## What they look for\n- Working software first: it must build and run from the README with no hand-holding.\n- Sensible structure (layers, naming, no business logic in controllers) over cleverness.\n- Tests that cover the rules, not the framework.\n- Honest scope: a short list of what you cut and why beats a half-finished extra feature.",
    "follow_ups_md": "- In the review: why this project structure, and how would it change if the API grew to fifty endpoints?\n- How would you add pagination and filtering to the list endpoint?"
  },
  "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.