LEDGER / DEVELOPER RELATIONS
Building the team.
Opening the ecosystem.
A first person account of building Ledger’s Developer Relations team, developer documentation, global partnerships and integration support.
The starting point
When I joined Ledger, its developer experience and ecosystem presence had room to catch up with its reputation in hardware security. The company was often perceived as closed, with limited developer documentation, a modest presence on the global events circuit and few ongoing relationships with external developers and blockchain foundations.
Building the function
I established a dedicated Developer Relations team and trained colleagues from different parts of the company. The goal was to build an internal capability that combined technical understanding, developer education and ecosystem relationships.
Making the ecosystem accessible
We improved and relaunched the developer documentation, produced content consistently, built global partnerships and expanded Ledger’s participation in conferences and developer events. These efforts created more practical ways for developers and foundations to engage with the company.
Turning relationships into integrations
Alongside ecosystem, product and engineering teams, we supported more integrations and reduced the time needed to onboard blockchains. The DevRel team also helped onboard staking integrations into Ledger Live, contributing to the growth of digital services revenue.
The leadership lesson
Building DevRel from zero means connecting team development, documentation and relationships to a shared product and business direction. The integration and commercial outcomes came from collaboration across teams; my role was to build and lead the DevRel capability that helped make that work possible.
Explore the programs
Official resources provide context for the programs described here. This case is my account of my contribution during my time at the company.
Ledger Developer PortalConversation with Ian Rogers on Ledger’s podcast