Growth engineers sit at the intersection of engineering and GTM. They build acquisition funnels, instrument analytics pipelines, run experiments, and architect viral loops into developer products. They are also one of the highest-intent buyer personas for developer tooling — if your product touches onboarding flows, usage tracking, feature flagging, or analytics, a growth engineer is likely evaluating you right now.
The problem: growth engineers do not post on LinkedIn announcing "I am evaluating tools." They express intent on GitHub — starring PostHog, opening issues in LaunchDarkly SDKs, mentioning "activation rate" in a discussion thread, or committing A/B testing infrastructure to a product repo. GitLeads captures those signals in real time.
What Growth Engineers Do on GitHub
- Star analytics, feature flag, and experimentation repos (PostHog, GrowthBook, Unleash, Statsig, Eppo)
- Open issues requesting SDK integrations, webhook payloads, or cohort export APIs
- Comment in discussions about activation metrics, retention funnels, and onboarding flows
- Push commits with keywords like "viral loop", "activation funnel", "experiment rollout", "feature gate"
- File PRs adding analytics event tracking to open-source developer tools
Signal 1: Stargazer Tracking on PLG Tool Repos
Track new stars on repos that growth engineers use: PostHog, GrowthBook, Statsig, Eppo, Flipt, Unleash, Optimizely Feature Experimentation, Amplitude SDKs, Mixpanel SDKs, and Segment. A new star from someone whose GitHub profile shows "Growth Engineer" or "PLG" in the bio is a high-intent signal. GitLeads captures this and enriches the profile with company, email, top languages, and follower count.
Signal 2: Keyword Mentions in Issues and Discussions
Configure GitLeads keyword signals for terms growth engineers use when evaluating tools: "activation rate", "feature flag rollout", "A/B test SDK", "onboarding funnel", "viral coefficient", "referral loop", "PLG motion", "self-serve funnel". When someone opens an issue or posts a discussion mentioning these phrases in a relevant repo, GitLeads surfaces the lead.
// GitLeads keyword signal config for growth engineer leads
{
"keywords": [
"activation rate",
"feature flag rollout",
"A/B test",
"onboarding funnel",
"viral coefficient",
"referral loop",
"PLG motion",
"self-serve growth",
"product-led growth"
],
"repos": [
"PostHog/posthog",
"growthbook/growthbook",
"Unleash/unleash",
"Flagsmith/flagsmith",
"statsig-io/statsig-node"
],
"destination": "hubspot"
}Signal 3: Commit Messages and Code Mentions
Growth engineers often instrument their own codebases. GitLeads keyword signals scan public commit messages and code for phrases like "track activation event", "growth experiment", "referral attribution", or "onboarding step complete". These are engineers building growth infrastructure — exactly who needs your developer tool.
Routing Growth Engineer Leads to Your Stack
GitLeads integrates with HubSpot, Apollo, Clay, Slack, Smartlead, Instantly, and 10+ other tools. For growth engineer leads, a typical workflow: GitLeads detects signal → enriches profile → pushes to Clay for additional enrichment (company size, funding stage, tech stack) → routes to Smartlead for personalized outreach sequence. Growth engineers respond well to technical, value-first messaging — lead with the specific signal you captured.
- HubSpot: create contact with "Growth Engineer" persona tag and enroll in developer-focused sequence
- Clay: enrich with company funding stage and tech stack to qualify for ICP fit
- Slack: instant #sales-alerts notification for high-follower growth engineers
- Smartlead: personalized cold email referencing the specific repo or keyword signal
Why GitHub Is the Best Channel for Growth Engineer Leads
Growth engineers are builders first. They evaluate tools by reading the source, checking the SDK, and testing the API — not by attending webinars. Their GitHub activity is a direct map of their tool stack and active evaluations. A star on your PostHog competitor's repo is more actionable than any intent data from a website visitor because you know exactly what they are evaluating and why.