Allowed R6 · Within policy
{
"slug": "physics-phenomenon-visualization",
"title": "Physics Phenomenon Visualization",
"difficulty": "medium",
"tags": [
"frontend",
"role-frontend",
"take-home"
],
"is_free": true,
"locked": false,
"frequency": 0.25,
"last_reported_at": "2021-03-21T11:13:32.965628Z",
"url": "https://www.mokabla.com/en/c/nagwa/physics-phenomenon-visualization",
"agent": {
"page": "https://www.mokabla.com/agent/en/c/nagwa/physics-phenomenon-visualization",
"question": "https://www.mokabla.com/agent/_call/get_question?company=nagwa&question=physics-phenomenon-visualization"
},
"company": {
"slug": "nagwa",
"name_en": "Nagwa"
},
"body_md": "## What they ask\nJavaScript developer candidates are given a take-home task that matches the product: build an interactive visualisation of a physics phenomenon in the browser. Interviews for the role took place in Cairo, and the task is sent before the technical discussion.\n\nReported shape of the brief: pick or be assigned a phenomenon (projectile motion, a simple pendulum, wave interference, or a ball bouncing with damping), and build a page where a student can change one or two parameters (angle and initial speed, string length, frequency) and watch the result update. Plain JavaScript with Canvas or SVG is welcome; a framework is fine if it does not hide the physics.\n\nMinimum expectations that come up in the review:\n- The physics is right: units, time step, and the equations used are stated in a comment or the README.\n- Animation uses `requestAnimationFrame` and does not depend on frame rate for the simulation step.\n- Controls are keyboard and mouse accessible and the page works on a tablet.\n- The code is organised: simulation state separated from rendering, no globals sprawl.\n\n## What they look for\nCorrectness of the model first, then how clearly you can explain it to someone who teaches physics. A polished but wrong pendulum loses to a plain but correct one. They also look at how you handle edge inputs (zero speed, negative angle) and whether the code would let a content team add a second phenomenon without a rewrite.",
"follow_ups_md": "- How would you add a \"trace\" of the trajectory without hurting frame rate?\n- How would you make the same simulation replayable step by step for a lesson?",
"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."
}