Past Projects Deep Dive

What they ask

Across the Egypt office, whether the role is embedded engineering, a platform consultant or a tester, the technical interview spends a large block on your previous work. It is not a formality; the interviewers pick a project from your CV and go through it layer by layer.

Typical prompts:

• Pick the project you are proudest of. What was the problem, what did you build, what was the outcome?
• Describe the most complex technical problem you solved there. What were the options and why did you choose the one you did?
• What technology did you use, and what would you change with hindsight?
• Which parts were yours, and which were done by teammates or reused from libraries?
• How successful was it, in numbers if you have them?
• Why do you want to join this company, and what do you know about the kind of clients we serve here?

What they look for

• Precision about ownership. Overstating your part is the fastest way to lose the room when two engineers are asking in turn.
• A decision story with trade-offs, not just a list of technologies.
• Honesty about failures and what you learned; a project that shipped late with a clear lesson is a fine answer.
• The link between what you did and what the role needs, which you should make explicitly rather than hoping they infer it.