This is the kind of question that sounds easy until you're actually in it.
Choose a project that genuinely excited you and had real technical depth, then tell its story as a narrative arc: motivation, key decisions, what shipped, and honest lessons from failures. Focus on trade-offs and constraints rather than just listing features, and connect your learnings to how you'd approach engineering problems at ARM.
Pro tip: Pick a project where something actually failed or forced a pivot — interviewers at ARM value engineers who can diagnose problems and adapt, not just those who only show polished successes. Be specific about the technical 'why' behind decisions, including what you'd do differently.
Briefly explain what the project was and why you chose it — what gap or curiosity drove you. Keep it to 2-3 sentences so you have time for the technical meat.
Describe 2-3 important choices (e.g., language, architecture, hardware, libraries) and the trade-offs you weighed. Explain why you picked one option over another, including constraints like time, cost, or performance.
Be concrete about the final deliverable: what worked, how it was used, and any metrics or outcomes. If it was incomplete, say so honestly and explain what was left.
Discuss at least one thing that failed or didn't go as planned, what you learned from it, and how you adapted. This shows resilience and self-awareness.
Tie your learnings back to software engineering at ARM — e.g., low-level optimization, cross-team collaboration, or designing for constraints. Show how this experience makes you a stronger candidate.
AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.