Telegraph
· Remote · Full-time · Start ASAP
About Telegraph
We built the Google for machines: a network that turns every API, dataset and toolkit into something a machine can search, verify, and pay for.
Telegraph is building a permissionless intelligence and API routing network for autonomous software and AI agents. Today, agents and applications typically rely on fixed API providers, model providers, and centralized routers. Telegraph creates a competitive network where independent providers supply models, APIs, tools, and specialized intelligence, while the network evaluates providers, ranks their performance, routes demand toward the best available provider, and settles payment based on performance.
The vision: when an agent needs something, it shouldn't need to know which provider to use. It should ask Telegraph, and the network should find the best available capability.
Developers are already showing up. Our first hackathon opened with over 1,300 registered developers on day one, before a single line of marketing spend. Alongside that we're seeing strong interest from AI infrastructure companies, agent platforms, model and inference providers, API companies, payment infrastructure, evaluation platforms, and enterprise software companies.
We need someone to turn that interest into an aggressive commercial pipeline and a rapidly expanding integration ecosystem.
Read this part first
We only want to work with evangelists. You can join as a Product Manager on a path to CPO, or start as a CPO - up to you. Either way, at this early stage, we need fanatical builders obsessed with solving a problem and hyperscaling our network.
We are not hiring people who are on the fence. Instead, we look for people who cannot stop thinking about Telegraph. Ask anyone on this team what they're working on and they'll tell you it's the coolest and craziest thing they've ever touched, and they'll mean it. That's the bar. If you join and you're not saying the same thing within two-weeks, one of us made a mistake.
This is a moonshot. Every developer on the planet with an API becomes a supplier. Every agent becomes a buyer. The network decides who wins on merit and settles it automatically. Nobody has aligned the incentives for this before. It's a big enough swing that the opportunity is hard to pass up, and it's early enough that the person who takes this role will have shaped whether it worked.
You will own your area completely. Not "own" in the corporate sense where you present to a committee. You will be the person actually in charge of and responsible for product and commercial growth at Telegraph, and how fast we scale will be directly downstream of how well you do it. That's a real weight. Some people find that thrilling and some find it terrifying, and we're only interested in the first group.
How we work: go out and do your job. Move without asking permission. Then check in with each other constantly, not to report status but to help. Where are we weak? What's breaking? What would make this a serious protocol instead of an interesting one? We're direct with each other about all of it, and nobody here is protecting territory.
We want early employees who give everything they have, because that's what the window requires, and who get the ownership and upside that should come with it.
The Role
This is not a traditional corporate Product Manager/CPO role. You'll operate at the intersection of product, integrations, partnerships, a little business development, and growth, working directly with the founders and engineering team.
The goal:
Find the right companies → get them integrated → get them using Telegraph → expand distribution → generate measurable commercial traction.
You'll have significant autonomy and ownership over that process.
What you'll do
1. Build the commercial pipeline
Our target universe spans model providers, inference providers, MCP ecosystems, agent platforms, API providers, payment infrastructure, evaluation companies, and enterprise platforms.
You will identify and prioritize the highest-value opportunities, run founder-level outreach, own inbound, and take discovery calls with founders, CEOs, CTOs, and product leaders. You'll maintain a structured pipeline from prospect to deployment, tracking expected network volume, revenue, strategic value, and probability of conversion.
We're not looking for a collection of logos. We're looking for actual commercial opportunities. Your goal is to connect the machines broadcasting requests across the web with the miners who answer them.
2. Turn conversations into integrations
You own the full path: prospect → conversation → technical discovery → POC → test environment → production → usage → revenue.
Not every partner needs to wait for the entire network to be production-ready. Where appropriate, get partners into a test environment, validate the use case, collect technical feedback, establish the commercial relationship, and prepare the integration for production.
We are a neutral layer. We are building this for everyone, and we want to help as many people as possible with what we've created. Speed matters. We move aggressively while staying honest about what Telegraph can currently support.
3. Create distribution, not just partnerships
The objective isn't for companies to just integrate Telegraph. It's for Telegraph to become part of how agents actually operate:
Keep asking: who needs Telegraph, and who can distribute Telegraph? An agent platform that exposes Telegraph to thousands of developers may be worth more than a single direct customer.
4. Develop strategic partnerships
Not every relationship has the same purpose. You'll determine whether a company should become a miner/provider, customer, distribution partner, ecosystem partner, payment/identity partner, evaluation partner, infrastructure partner, or strategic integration.
Target areas include AI and inference, compute infrastructure, agent platforms and MCP ecosystems, developer platforms, agent commerce, payments, identity, settlement, evaluation, observability, and security.
5. Work directly with engineering
You don't need to write our Rust or backend code. You do need to be fluent enough to discuss APIs, SDKs, MCP, AI agents, LLM inference, model routing, evaluation, distributed infrastructure, payments, and system architecture.
You should be able to ask a CTO "what would it actually take to integrate Telegraph?", understand the answer, and turn it into actionable requirements: what's integrable today, what needs engineering, what can stay in a sandbox, what must be production-ready, and which integrations offer the most distribution leverage.
6. Help shape the product
You'll be closer to partners than anyone. If ten of them independently say "we need X before we can deploy," that's product intelligence. You'll bring it back and help prioritize it. You aren't just executing an existing roadmap - the market will help shape what Telegraph becomes, and you'll be the primary channel for that information.
7. Build measurable fundraising traction
Prospecting investors may ask how many integrations we have, how fast they're growing, how many companies are actively testing, how much transaction volume and revenue the pipeline represents, and why those companies chose Telegraph.
You should be able to turn the pipeline into numbers:
100 targets → 30 conversations → 12 POCs → 6 integrations → X expected monthly requests → $Y expected revenue
The numbers will evolve. The principle won't: commercial traction must be measurable.
What success looks like
First 30 days. Deep understanding of the technology, positioning, roadmap, and economics. Existing target list reviewed and prioritized. Structured CRM and pipeline in place. Founder-level outreach underway (we use Boardy.ai, which is highly effective, and you will too). Inbound interest converted into active opportunities. First technical discovery and POCs started.
First 60 days. Multiple active integration discussions. Multiple companies testing Telegraph. Initial strategic partnerships. Clear integration playbooks. Measurable pipeline value and expected network volume from major opportunities.
First 90 days. More integrations, more demand, more network activity, more revenue potential, more strategic distribution.
Who we're looking for
You should be comfortable with cold outreach on social media, founder-to-founder conversations, technical discovery calls, negotiating integrations/partnerships, selling a technical vision, working directly with engineers, operating without a predefined playbook, and moving across time zones at speed.
This isn't for you if you want a large team underneath you, want to always have clearly defined responsibilities, want a long strategy phase before execution, want a role centered on roadmaps and documentation, want someone else generating your pipeline, or want a structured corporate environment.
It is for you if you thrive in ambiguity, are obsessed with execution, can sell a technical vision without misrepresenting the product, want to work somewhere the mission is the whole point, and can turn a conversation into an integration, an integration into usage, and usage into revenue.
Why Telegraph?
The machine economy is developing extremely quickly. Thousands of companies are building models, APIs, tools, agents, payment infrastructure, evaluation systems, and specialized intelligence, but these capabilities remain fragmented.
Telegraph is building the layer that connects demand to the best available intelligence. If we execute, an agent will never need to ask "which provider should I use?" It will simply ask Telegraph, and the network will figure it out.
Your job is to make that network ubiquitous.
Application
Send us: