AGENT CALL · Mokabla · get_question
request ag_3a957f60bcb4

Decision

Allowed   R6 · Within policy

input
{"company":"moneyfellows","question":"head-of-engineering-round"}

Result

{
  "slug": "head-of-engineering-round",
  "title": "Head of Engineering Round",
  "difficulty": "medium",
  "tags": [
    "behavioral",
    "final",
    "backend"
  ],
  "is_free": true,
  "locked": false,
  "frequency": 0.5,
  "last_reported_at": "2025-11-13T15:13:32.453074Z",
  "url": "https://www.mokabla.com/en/c/moneyfellows/head-of-engineering-round",
  "agent": {
    "page": "https://www.mokabla.com/agent/en/c/moneyfellows/head-of-engineering-round",
    "question": "https://www.mokabla.com/agent/_call/get_question?company=moneyfellows&question=head-of-engineering-round"
  },
  "company": {
    "slug": "moneyfellows",
    "name_en": "MoneyFellows"
  },
  "body_md": "## What they ask\nAfter the technical round there is a one-hour conversation with the head of engineering, followed by a 30-minute HR wrap-up. This round is less about patterns and more about judgement. The core of it is your previous technical experience in your current organisation, examined closely:\n\n- Walk me through the system you own today. What is the weakest part of it?\n- Tell me about a technical decision you made that you would now reverse.\n- How do you decide what to refactor and what to leave alone?\n- What does your release process look like, and what broke last time?\n- Why a fintech, and why one built around savings circles?\n\nFor design-leaning roles the same round focuses on your design process instead: how a feature goes from idea to shipped, and how you handle disagreement with product.\n\nThe HR part covers notice period, salary expectations, and hybrid working. The whole process, from first recruiter call to answer, tends to run about ten days.\n\n## What they look for\n- Honest ownership of trade-offs, including the ones that did not work out.\n- Evidence you think about users and money at the same time: a payout that arrives late is a trust problem, not just a bug.\n- Communication with non-engineers, since product and operations sit close to engineering.\n- Signals that you will stay: curiosity about the product, questions about the roadmap.\n\nA known weak spot: candidates who were rejected report vague or slow feedback. Ask at the end of this round when and how you will hear back.",
  "follow_ups_md": "- What would you do in your first 30 days here?\n- How do you handle a production incident involving customer money?",
  "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."
}

Navigate (pre-filled links you can follow)