This question has more surface area than it looks.
Choose a project that genuinely excited you and had real constraints, then narrate it as a story: the problem, your motivation, key technical decisions (especially trade-offs), and what you actually shipped. Keep it concise and focus on your thought process and the impact, not just the tech stack.
Pro tip: Emphasize the trade-offs you made and what you learned from them—ARM values engineers who can navigate ambiguity and make pragmatic decisions. Also, be honest about what didn't work or what you'd do differently; it shows maturity.
Briefly describe the project and the problem it solved. Explain why you personally cared about it—this could be a frustration you had, a gap you noticed, or a skill you wanted to develop.
Outline how you scoped the project and the key decisions you made. Highlight any constraints (time, budget, skills) and how they influenced your choices.
Dive into one or two significant technical decisions, explaining the alternatives you considered and why you chose your path. Show awareness of pros and cons.
Concretely state what you built and delivered. Include metrics if possible (users, performance improvements, etc.) and any feedback you received.
Share what you learned and how it has influenced your work since. Connect it to the role or ARM's values, showing how this experience makes you a better engineer.
AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.