*CodSpeed is the continuous performance optimization platform trusted by world-class engineering teams. We shift performance testing left to catch regressions before they ship. From open-source projects like Mozilla, Vercel, and Pydantic to enterprise teams at OpenAI, Cloudflare, and beyond. CodSpeed empowers developers to measure, track, and improve software efficiency across the stack.*

Developers already find us. We post performance reports on open-source projects, engineers discover CodSpeed, adopt it on their own repos, and it spreads. That's how teams at large companies started using us before we ever reached out.

This is a growth and operations role, not a quota-carrying sales seat. You own pipeline generation. You turn product-usage signals into qualified pipeline, and the founder runs the closing conversations. You are equal parts builder, operator, and creative campaigner.

What you'll do

• Own pipeline generation end to end: find the right developers and teams, qualify them, and hand the founder warm, well-briefed conversations.
• Turn product usage into pipeline. Spot the users and teams already getting value from CodSpeed and engage them at the right moment with the right context.
• Run a champion-led motion. Find the developer who already loves CodSpeed, arm them with what they need, and help them bring it to their team.
• Build the outbound engine: create and detect buying signals across the developer community, then run targeted, personal, signal-based outreach at scale.
• Design and run creative campaigns, digital and in person, to build the developer community and grow awareness. Give value before asking for anything.
• Run account-based programs against the specific companies we most want in the room: research the accounts, find the internal champions, and orchestrate multi-touch plays to get the founder a meeting.
• Start manual, then automate. Learn what converts by hand, then build the flow once a pattern works.
• Get technical enough to hold your own with engineers and engineering leaders, and to support demos when needed.

Requirements

• 3 to 6 years of experience, with at least one early-stage or founding GTM stint where you built a motion from scratch.
• A track record in growth, GTM engineering, or revenue operations: you build pipeline with systems, signals, and campaigns, not just conversations.
• Strong technical fluency. You can get credible with developers and engineering leaders and learn a technical product fast.
• Resourceful above all. You will do manual grunt work one day and build automation the next, and you are happy doing both.
• Creative. You find angles other people miss. We can teach structure. We cannot teach this.
• Comfortable with an early phase where not every signal is perfectly qualified. We trade some noise for speed and learning.