Developer Marketing Manager

The Role

The Developer Marketing Manager is building a new function with a clear thesis: the next wave of pipeline won't come from traditional SEO or paid search; it will come from how well Apryse shows up inside AI-generated answers, developer communities, and third-party technical channels. This is a rare early role: you'll help shape what developer-focused AEO (Answer Engine Optimization) looks like in practice: seeding technical content in the right communities, engaging authentically with developers, and ensuring Apryse is the answer when an LLM is asked “what’s the best PDF SDK for Python?” or “how do I add annotation to a React app?”

Responsibilities

• Execute the AEO & off-page strategy across third-party developer channels — Stack Overflow, Reddit, GitHub Discussions, dev.to, Discord communities, and emerging AI-indexed surfaces.
• Create and distribute genuinely useful technical content: code snippets, integration guides, tutorials, and answers that developers bookmark, not scroll past.
• Engage in developer communities as a trusted voice for Apryse—not as a marketer, but as someone who understands the problems developers are solving with document and scanning SDKs.
• Identify and build relationships with technical influencers, open-source contributors, and community moderators relevant to Apryse's ecosystem.
• Monitor and grow Apryse's presence in LLM-generated answers and AI search surfaces, iterating on content strategy based on what's getting cited and why.
• Collaborate with product, developer relations, and content teams to surface technical narratives and ensure Apryse's documentation and third-party footprint are aligned.
• Track pipeline attribution from off-page and community activity—you'll be expected to connect your work to commercial outcomes, not just brand impressions.
• Help refresh and evolve the Apryse developer brand across external channels, bringing a sharper, more developer-native voice to everything we put out.

Skills

• You can "speak developer"—you understand the difference between a good code sample and a bad one, even if you're not writing production code yourself.
• You're a hustler who's comfortable with grunt work: writing the 10th community post, tweaking the content angle again, doing the manual outreach.
• You don't wait for scale before doing the work.
• You're commercially minded. You know the difference between a campaign that built brand awareness and one that moved pipeline, and you care about the latter.
• You're a strong written communicator who can adapt tone; from a precise technical answer on Stack Overflow to a punchy Reddit comment to a detailed integration guide.
• You're self-directed and comfortable in a fast-moving, early-stage function where the playbook is still being written.

Requirements

• 3–6 years in developer marketing, developer relations, technical content, or a closely adjacent role—ideally at a company that sells to engineers.
• A track record of creating technical content that developers actually engage with: tutorials, code walkthroughs, community posts, documentation, or similar.
• Demonstrated experience building presence in developer communities— you've been in the trenches on Stack Overflow, GitHub, Discord, or similar, not just posting from a brand account.
• Familiarity with AEO, GEO, or LLM-era content strategy is a strong plus; genuine curiosity about how AI answers are shaped is a must.
• Experience in a developer tools, SDK, API, or infrastructure company is strongly preferred. SaaS-only backgrounds are unlikely to be a fit.