Blog Post: From Arm Ambassador to Edge AI Developer Strategist

From curiosity to community Growing up, the companies people talked about were the visible ones: the brands on phones, laptops, hoodies, and social media bios. Embedded systems, meanwhile, stayed quietly in the background, invisible to most people despite powering almost everything around us. Ironically, that invisible world was exactly what I fell in love with. As a child, I was always taking devices apart to understand how they worked. My parents were understandably worried, so when I was 9, they bought me a desktop computer. It had traveled from Germany to Ghana, and I still remember opening the system unit just to study the motherboard and see how everything connected. That curiosity stayed with me through school and university. Even though my parents hoped I would become a neurosurgeon or petrochemical engineer, I knew I wanted to study computer engineering. I was fascinated by hardware, optimization, constraints, and the challenge of making intelligence run on small, resource-limited devices. That curiosity eventually led me to Arm. What the ambassador experience taught me If you had told my younger self that I would one day work at Arm, I probably would have stared at you blankly. Not because Arm was not impressive, but because I had never even heard of it. Arm was already part of my life; I just didn’t realize it. Like billions of other people, I was using Arm-based technology every day. It was inside the devices I used, the systems I admired and tore apart, and the embedded technology I was slowly learning to understand. Looking back, that is what makes this journey feel complete. I went from being curious about the invisible systems around me to becoming an Arm ambassador, and now I help developers build on those same systems as an Arm employee. My journey began when I joined the Arm Developer Program and later became an Arm ambassador. During my BSc engineering capstone project presentation at the University of Ghana, I met Stephen Ozoigbo, who invited me to an Arm developer event and introduced me to the program. That moment became an important turning point. From the outside, I learned, shared, built communities, and saw how developers used Arm technology to solve real problems. I wrote technical learning paths and blogs about TinyML on Arm using PyTorch and ExecuTorch, supported student and developer communities, presented Arm-based boards at events, and helped make embedded systems and AI more approachable for emerging developers. That experience gave me more than awareness of Arm. It gave me perspective. Whether I was helping students prototype IoT applications, supporting developer events, or explaining Arm-based tools to emerging engineers, I saw how developer enablement works in practice: access, guidance, examples, and community all matter. Becoming an employee did not feel like a completely separate chapter. It was a continuation of the same journey, only from the inside. Now, as a Developer Strategist at Arm, this experience shapes my work every day. I help developers adopt Edge AI technologies by making complex systems clearer, more practical, and easier to build on. Arm (E 3)NGAGE  ecosystem event: 4 th   February,  2023   Why developer enablement matters in Edge AI This role has taught me that developer enablement is not just documentation or tooling. It is the bridge between curiosity and confidence. It helps developers answer questions that matter most: Where do I start? What works today? Which tools should I use? How do I go from prototype to deployment? What happens when I scale? Arm became the place where the things I had been curious about growing up finally came together. What I once imagined as “a semiconductor company” turned out to be a global compute platform shaped by technology, software, ecosystem collaboration, and developer enablement. Engineers build the underlying technology, ecosystem teams work with partners and developers, strategy teams think about timing, and developer teams turn complex roadmaps into practical entry points. Real innovation happens when different teams align around the problems developers and the ecosystem need to solve. The real challenge in technology is rarely building powerful hardware. It is enabling developers to use it effectively. Another lesson is that timing matters almost as much as technology. Developer experience is not an afterthought. It is infrastructure. Good enablement reduces friction. Good documentation builds trust. Good tooling helps ecosystems grow. Arm at Super AI: 10-11 th   June,  2026   Developers start with problems, not platforms In Edge AI, where hardware, software, frameworks, distributions, drivers, cloud pipelines, and deployment workflows all collide, clarity becomes incredibly valuable. In this role, I have worked with engineering, product, ecosystem, and developer teams to help connect the pieces. I have learned how much coordination happens behind the scenes before developers ever see the finished result. Hardware roadmaps evolve. Priorities shift. Strategies change. Developers still need clarity. A huge part of the work is deciding what developers need to see, and when: What should developers see today? What can they realistically build today? What is not ready yet? How do you maintain trust while everything evolve s ? That balancing act has been one of the most fascinating aspects of the role. Another surprise was how much my background prepared me for it. Before joining Arm, I spent years working across AI, IoT, embedded systems, edge computing, developer communities, and strategy. At times, that path felt unfocused because I was interested in too many things at once. Now I realize those intersections were the point. Edge AI is inherently interdisciplinary. You cannot understand it properly from a single perspective. You need to understand developers. You need to understand systems. You need to understand deployment. You need to understand business incentives. And increasingly, you need to understand ecosystems. One of the biggest things this role has confirmed for me is this: Developers do not start with platforms. They start with a problem they need to solve. Maybe this resonates so deeply with me because, at my core, I have always been that kind of engineer. Developers want to build something meaningful: a smart camera, a robotics workflow, a predictive maintenance system, or an intelligent edge device. The tooling, frameworks, and hardware only matter if they help developers reach that goal faster. That perspective has shaped how I now think about developer strategy. Not as marketing. Not as documentation. Not even as DevRel in the traditional sense. But as helping an ecosystem grow. Still learning, still obsessed Same location, different roles These six months have also stretched me personally. I have had to become more comfortable with faster decisions, executive communication, stakeholder management, and shifting priorities. I have also learned that technical ability is not enough on its own. Visibility, communication, alignment, and trust matter just as much in a large organization. Looking back, one thing is clear: the younger version of me who once spent hours obsessing over low-level systems for fun would be genuinely happy that I ended up here. Because I get to work on problems that genuinely excite me, alongside people who are building the future of computing. Six months down. Still obsessed. The Ambassador program did not just introduce me to Arm. It helped me see that I belonged in the ecosystem I had always admired. For anyone curious about building, learning, and growing with Arm, the Developer Program is a powerful place to start. Join the Arm Developer Program Become an Arm Ambassador