AGENT VIEW · Mokabla · Question · java-spring-boot-screen
AgentGate · request ag_32e8f1fb23c0

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/etisalat/java-spring-boot-screen

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": "java-spring-boot-screen",
    "title": "Java and Spring Boot Screen",
    "difficulty": "medium",
    "tags": [
      "sql",
      "technical",
      "swe",
      "backend",
      "fundamentals"
    ],
    "is_free": true,
    "locked": false,
    "frequency": 0.333,
    "last_reported_at": "2025-05-05T10:12:49.215173Z",
    "url": "https://www.mokabla.com/en/c/etisalat/java-spring-boot-screen",
    "agent": {
      "page": "https://www.mokabla.com/agent/en/c/etisalat/java-spring-boot-screen",
      "question": "https://www.mokabla.com/agent/_call/get_question?company=etisalat&question=java-spring-boot-screen"
    },
    "company": {
      "slug": "etisalat",
      "name_en": "e& Egypt (Etisalat)"
    },
    "body_md": "## What they ask\n\nSoftware hires go through two technical interviews and one HR interview. The technical rounds mix Java, Spring Boot and SQL questions with behavioral ones, and lean on your past projects.\n\nQuestions in this area, for example:\n\n- **Java**: `HashMap` internals and why `equals` and `hashCode` must agree; checked vs unchecked exceptions; `final`, immutability and thread safety; what `synchronized` actually locks.\n- **Spring Boot**: how dependency injection resolves a bean and what happens with two candidates; `@Transactional` propagation and where it silently does nothing (self-invocation); building a REST controller with validation; JPA lazy vs eager loading and the N+1 problem.\n- **SQL**: write a query returning the top 3 subscribers by monthly usage per plan; explain a plan that ignores your index; difference between `WHERE` and `HAVING`.\n- **Behavioral**: a production issue you owned, and how you handle conflicting priorities from two managers.\n\n## What they look for\n\n- Depth on whatever you claim on your CV; they pick the framework you list and go three questions deep.\n- Practical answers (\"I would check the transaction boundary first\") over definitions.\n- Reasonable SQL fluency without an IDE; they may hand you a pen.",
    "follow_ups_md": "- How would you cache a slow read endpoint in Spring and invalidate it safely?\n- Where would you put a rate limit for a public API in a telecom stack?"
  },
  "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.