概要
公開日: 2026-06-29
翻訳生成に失敗したため、原文をそのまま保存しています。
原文
We are looking for 1-2 people to join our technical business development team. This is a uniquely designed role for someone with technical skill who wants to learn go to market and business from the ground up at a mobile infrastructure company. You will learn from some of the best in the business, people obsessed with building for builders, thinking about developer trust everyday. We will introduce you to a fast paced startup and teach you everything you need to know about business. You will research some of the best mobile teams in the world, figure out what they are building, understand where Expo can help, and start useful conversations with engineers and technology leaders. This post takes you through how we approached bringing Expo to companies don’t know about Expo Services, you’ll hear from Colin Hunt who pioneered the role, and you’ll learn more about the day to day work. The bar is simple —> we want someone who built an app on Expo and now wants to talk about it with folks who don’t yet use Expo. If that sounds like you, reach out. This post will take you through why we built a technical BDR function at Expo, the experience of the role, and how we approached the work. Colin Hunt pioneered this technical BDR motion Colin became the first real owner of this motion. His job was not just “send outbound.” His job was to help us build the system with our GTM Ops leader. We wanted to reach out to these companies manually, like a human would, and offer help. What Colin did: - Research accounts - Find the right people - Write the first messages - Engage on LinkedIn - Offer guidance with Expo - Learn what worked - Route qualified conversations to AEs - Keep improving the process He has already shown the profile we want more of: curious, technical, persistent, and useful to customers. But what’s unique about Colin Hunt is that he built an app on Expo before working with Expo, so he knew the product intimately. The best BDRs at Expo will not be generic sales development reps. They need to understand developers, mobile teams, and infrastructure well enough to be helpful before a call ever happens. Let’s hear from Colin directly. Why I took this technical BDR role with Expo Colin [object Object] I took on this work because I'm obsessed with mobile apps. Expo enables developers to create beautiful apps and deploy them everywhere. From the moment I ran my first “Hello World” program in C++, all I wanted to do was figure out how to make something show up on my phone. There is just something so compelling about mobile. Your app is not just a tab in Safari. It’s on your home screen. It feels real. I bought a Mac Mini and started following Apple’s Tutorials for Native Development. It was too much too fast. Learning this new environment was too cumbersome for me. I was studying Electrical Engineering, not computer science. I was contending with a new language, a new environment, and new tools. Needless to say, I gave up. A year later, in 2017, I found React Native. A framework that would allow me to create cross-platform mobile apps in Javascript. Seemed promising. Javascript was a little more familiar to me, and there was this thing called Expo that allowed me to run my app on my phone within the first 10 minutes of discovering it. Magic - I was hooked. I spent the next 7 years building Prospre, an app that generates meal plans based on your macro targets. We ejected from the Expo framework, but we used Expo libraries whenever possible, as we knew that we could trust the team to deliver robust and high-quality packages. I was grateful for everything Expo was building, but we didn’t consider ourselves an Expo app any longer. But Expo had a vision for what the mature framework would look like that wasn’t clear to me from the outside. I started to see things happening, and the FOMO set in. It started with improvements to expo-web that allowed us to ditch our React App completely, and ship our React Native codebase to the web. Then, I learne