Über diese Developer Relations Lead Stelle bei Hubble Network
Hubble Network was founded with the intention of delivering on the promise of what Internet-of-Things (IoT) was supposed to be. We're building a global Bluetooth® network dedicated to machine-to-machine connectivity. We differentiate ourselves as the first modem-less and gateway-less, direct-to-satellite network from off-the-shelf Bluetooth® Low Energy chips. Hubble is ideal for applications in logistics, AgTech, and maritime where economies of scale for volume consumer and enterprise asset tracking is a priority. Our goal is to be the first billion-endpoint-connected network in the world.
Hubble is an early-stage, venture-backed startup supported by some of the best investors in the world. In their previous lives, the founding team has been successful in raising $100s of millions in venture funding, developing the Amazon Sidewalk network, launching billions of dollars of space assets, and leading their teams to successful exits, both through acquisition and IPO. We are now looking to bring on talented team members who are the best at what they do to help us make Hubble a reality for the world.
Role Overview
We're looking for a Developer Relations Lead to grow the community of developers building on Hubble's satellite and terrestrial connectivity platform. Hubble lets standard Bluetooth Low Energy devices talk to a global network, both terrestrial and direct-to-satellite, without cellular modems, SIM cards, or GPS.
That capability only matters if developers find it, understand it, and ship with it. This role owns that outcome. Success is one number above all: developers who ship a working Hubble integration, and the active community that grows around them.
You'll be the face of Hubble in the developer community. You'll write the tutorial an embedded engineer finds at 11pm, give the conference talk that makes a firmware team rethink their connectivity stack, and answer the community question that unblocks someone's integration. As the function proves out, you'll define what a DevRel team looks like and help build the case for who to hire first.
We want an engineer first. You've shipped real products (ideally embedded, BLE, or IoT systems) and found you love teaching other developers as much as building. You can read our SDK source, write an opinionated working integration from scratch, and then explain it so clearly that a developer who's never touched satellite connectivity gets to first success in an afternoon.
Responsibilities
- Own Hubble's developer relations strategy end to end: content, community, events, and advocacy across the terrestrial network, satellite network, and Device SDK
- Create technical content with working code at the center. Tutorials, integration guides, sample projects, demo videos, and blog posts that take a developer from curiosity to a shipped device
- Build and maintain public example projects (asset trackers, sensor networks, finding-network applications) using the Hubble Device SDK
- Own the Hubble devkit: define what's in the sample kit we hand new developers (hardware, preloaded firmware, quick-start guide, first-project walkthrough) and keep refining it until a new dev gets from unboxing to first message on the network in one sitting
- Represent Hubble at developer events: speak at embedded, IoT, and connectivity conferences, run workshops and live demos, organize Hubble meetups and hackathons
- Make Hubble work in agent-driven workflows. Most developers now start integrations through coding agents (Claude Code, Cursor), so keep our content agent-readable: llms.txt, canonical examples agents can copy correctly, and rules/skills files for popular agents. Regularly test whether a coding agent can complete a Hubble integration from our docs alone, and flag product-surface gaps to Product
- Grow Hubble's developer community across GitHub, Discords, and social channels. Be the person developers ping when they're stuck, and make our most engaged users visible and celebrated
- Hire and manage technical writer contractors while defining what a DevRel team looks like
- Set and track the metrics that ladder up to engagement. Own content reach, community growth, developer contributions and spotlights, devkit components, and contribute developer funnel feedback to Product
- Channel developer feedback into the product. Gather friction points, feature requests, and integration patterns from the community and hand them to Product as structured, actionable input
- Serve as Hubble's developer-facing liaison to silicon and ecosystem partners: chipset/module vendors and RTOS platforms
- Support product launches by producing the developer-facing technical assets (demos, sample code, launch-day tutorials) that make new capabilities usable on day 1
Qualifications
Must Haves
- 8+ years in developer relations, advocacy, or developer education, and experience leading or mentoring others
- Has shipped production code. Able to write an integration against an unfamiliar SDK
- A track record of technical content developers actually used: tutorials, sample repos, conference talks, videos, or open-source projects you can point to
- Proven public speaking at developer events, including the ability to give a live demo that works
- Deep empathy for the developer journey. You notice where people get stuck and instinctively build the thing that unblocks them
- Community instincts: you've grown or been an active part of developer communities (open source, forums, meetups, Discord/Slack)
- Metrics-driven. You set adoption goals, measure what's working, and cut what isn't
- Strong collaborator across Product, Engineering, and Marketing, with the judgment to know which team owns what
- Self-directed and autonomous. You thrive with ownership and minimal supervision in a fast-moving, early-stage environment
- Willing to travel for important conferences, meetups, and community events
Nice to Haves
- Embedded systems, BLE/wireless, firmware, or IoT device software strongly preferred, with comfort in C/C++ plus a higher-level language (Python, TypeScript)
- Passion for IoT, satellite networks, and connectivity. You're drawn to hard problems with real-world impact
- Fluent in AI-assisted development. You use coding agents in your own work and understand what makes docs and SDKs easy (or impossible) for them to use correctly
COMPENSATION & BENEFITS
💰 Salary: $173000-$285,000 (commensurate with experience) Ops to complete
🩺 Comprehensive Benefits – Health, Dental, Vision, & HSA options
🌍 Unlimited PTO
🚇 Commuter Benefits (if working from HQ)
🎓 Learning & Development Allowance
💪 Health & Wellness Stipend
🌎 Sabbatical Program – Recharge and explore new ideas
🛠 Cutting-Edge Space Tech – Work on state-of-the-art satellite system
ITAR REQUIREMENTS
Hubble is required by the U.S. Government to comply with various space technology export regulations including the International Traffic in Arms Regulations (ITAR). All applicants must be U.S. citizens or lawful permanent residents (“green card holders”) as defined by ITAR (22 CFR §120.15). More information on ITAR can be found here.
Hubble is committed to creating a diverse environment and is proud to be an equal-opportunity employer. Each individual has the right to work in a professional environment that promotes equal employment opportunity and prohibits discriminatory practices, including harassment. All qualified applicants will receive consideration for employment without regard to race, color, religion, gender, gender identity or expression, sexual orientation, national origin, genetics, disability, age, or veteran status.
Seattle Washington