Allowed R6 · Within policy
{
"slug": "take-home-task-review",
"title": "Take-Home Task Review",
"difficulty": "medium",
"tags": [
"system-design",
"frontend",
"swe",
"backend",
"role-frontend",
"take-home"
],
"is_free": true,
"locked": false,
"frequency": 0.667,
"last_reported_at": "2026-02-06T20:14:01.745129Z",
"url": "https://www.mokabla.com/en/c/robusta/take-home-task-review",
"agent": {
"page": "https://www.mokabla.com/agent/en/c/robusta/take-home-task-review",
"question": "https://www.mokabla.com/agent/_call/get_question?company=robusta&question=take-home-task-review"
},
"company": {
"slug": "robusta",
"name_en": "Robusta"
},
"body_md": "## What they ask\nThe loop is three steps and candidates describe it as conversational rather than stressful: an HR phone screen, then a task sent by email, then a technical interview that reviews the task and your background, and finally an open discussion with a manager about mindset. Test automation roles are rated the hardest; software engineer roles the easiest.\n\nThe task depends on the track. For frontend it is a small React feature (a list with filtering, a form with validation, or a page consuming a public API) with attention to state, loading and error states. For backend it is a small Laravel or Node service with a couple of endpoints, a relational model and tests. In both cases the review call, not the task, is where the decision is made.\n\nWhat the review covers:\n- Walk us through the structure. Why these folders, components or layers?\n- Which decision are you least happy with, and what would you change with another day?\n- How did you test it, and what did you decide not to test?\n- Where would this break if the data grew a hundred times?\n- Something from your background that relates: a similar problem in a past project.\n\n## What they look for\nOwnership of the decisions in the code, honesty about shortcuts, clean commits and a README that runs. They are an agency working with many clients, so they also listen for how you explain technical choices to a non-technical person.",
"follow_ups_md": "- If the client changes the requirement after you submit, how do you restructure?\n- What would you add first: more tests, CI, or documentation?",
"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."
}