My first step was an online, recorded assessment. I had to answer a set of prompt questions using a video-style recording setup, and I only had a limited attempt—once I recorded, I couldn’t redo it. The questions were fairly standard pattern-based prompts, and the whole thing felt structured but a little stressful because I knew any mistake would be permanent.
After that, the rest of the flow still relied on filmed delivery. I had a separate video interview where I had to speak to the camera consecutively for a few minutes, with a tight cadence between questions and no opportunity to redo any part. The process felt like it was checking how I presented myself under pressure, not just whether I had the right answers.
11 months ago
Average Positive Cairo, Cairo Governorate
My interviews leaned strongly on full-stack fundamentals and structured problem-solving. I first faced an hour-and-a-half technical conversation that started with conceptual questions across the stack—front-end ideas, backend architecture, databases, and how deployment worked. After that, I moved into a problem-solving section where I was given a scenario and asked to reason out my approach while explaining how I’d handle it.
Then the process continued into rounds that mixed technical depth with communication and context. One round asked about projects and included SQL and Python topics tied to my resume, and another touched on culture fit—how I worked with others and how I’d handle collaboration. A technical client-facing round also repeated some earlier themes rather than moving cleanly forward, but it still tested problem-solving with a concrete task involving a 2D matrix.
> 1 year
Average Positive Egypt
My interview started after I waited for a bit, and when I finally got into the room the first questions were personal information. After that, the tec…
Unlock every Full Stack Engineer interview experience
