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.
{
"question": {
"slug": "figma-to-react-task",
"title": "Figma to React Task",
"difficulty": "medium",
"tags": [
"frontend",
"role-frontend",
"take-home"
],
"is_free": true,
"locked": false,
"frequency": 0.667,
"last_reported_at": "2025-08-14T19:12:35.320059Z",
"url": "https://www.mokabla.com/en/c/bosta/figma-to-react-task",
"agent": {
"page": "https://www.mokabla.com/agent/en/c/bosta/figma-to-react-task",
"question": "https://www.mokabla.com/agent/_call/get_question?company=bosta&question=figma-to-react-task"
},
"company": {
"slug": "bosta",
"name_en": "Bosta"
},
"body_md": "## What they ask\nFor the frontend team the funnel is: a short HR call, then a filtration task, then an HR interview. The task is a Figma design you implement in React. It is described as simple, but candidates consistently say it is bigger than a typical filter task, closer to a small feature than a single component.\n\nA representative brief (the real Figma changes, the shape does not):\n\n- A shipments page with a searchable, filterable table (status, city, date range).\n- A details drawer for one shipment with its tracking timeline.\n- Responsive down to mobile, matching the Figma spacing and typography.\n- Data comes from a mock JSON you are given, or a simple mocked API.\n\nWhat gets read closely is not the pixels. Reviewers look at folder structure, how you use TypeScript (typed props, API models, no `any`), how state and data fetching are organised, and whether the code would survive a second feature being added.\n\nAfter the task there is an HR interview with standard questions: how do you improve your skills, what are your biggest achievements, why this company.\n\n## What they look for\n- A sensible layout: features or pages, shared components, hooks, services, types.\n- Strict TypeScript and a clean data layer, not everything inside one component.\n- Reusable table and filter components rather than copy-paste.\n- A README that explains how to run it and what you would do next with more time.\n\nOne honest caveat from candidates: feedback on the task can be thin, and it is not always clear an engineer reviewed it. Keep a copy and be ready to walk through it yourself.",
"follow_ups_md": "- How would you add pagination and server-side filtering without rewriting the table?\n- Where does form validation live in your structure?\n- What would you unit test first in this task?"
},
"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."
}
| action | input | permission | |
|---|---|---|---|
| get_question One question with its body. Bodies are paid content unless the question is free. | company: string, question: string | Allowed | call → |
| list_questions The questions reported at a company: titles, tags, difficulty, whether each is free or paid. | company: string, page: number? | Allowed | call → |
| buy_access Buy 30 days of access to a company. | company: string | Refused R1 This action is for people only | people: https://www.mokabla.com/en/pricing |
| post_comment Comment on a question. | question: string, text: string | Refused 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.