Job Description

Percona is looking for someone who can own our technical voice across social and content channels – someone who reads a MySQL, PostgreSQL, or MongoDB changelog for fun, can turn an engineer’s Slack message into a post developers actually stop scrolling for, and thinks in terms of a content strategy rather than a content calendar.

This role sits inside Engineering, not Marketing. You’ll be embedded with the people doing the actual database work, sitting in on the same standups and design discussions, because that’s where the content comes from. This isn’t an events role, and it isn’t a “translate engineering for the business” role either – it’s for someone credible enough to be treated as a peer by engineers, who happens to also own how that work gets told to the world.

What You Will Do

Social & Content Strategy (the core of the role)

• Own the social media strategy end to end: channel priorities, content pillars, voice, cadence, and how success is measured – not just execution of a plan handed to you.
• Translate real engineering work (patches, RFCs, performance benchmarks, incident postmortems, contributions upstream) into content developers and DBAs actually value. Threads, technical breakdowns, short-form video, dev.to/blog cross-posts.
• Build a repeatable system for sourcing content directly from engineering work in flight. Release cycles, RFC discussions, on-call retros etc. rather than depending on ad hoc asks.
• Use AI-assisted tools for production (video, drafting, repurposing) without losing technical accuracy or authenticity.
• Define and track the metrics that actually matter for a technical audience (engaged developers, not just impressions) and report on what’s working.

Embedded Technical Credibility

• Sit close enough to engineering to actually understand what’s shipping and why. Attend the relevant standups, sprint reviews, or design discussions as a regular participant, not an occasional observer.
• Be genuinely fluent in open source database engineering conversations. MySQL, PostgreSQL, MongoDB internals, replication, performance tuning, or similar. Enough to interview an engineer, catch a technical inaccuracy, and ask the right follow-up questions.
• Participate authentically in the communities you’re writing for (forums, Slack/Discord, GitHub discussions). This is source material and credibility, not a separate job.
• Push back on engineers’ first drafts of an explanation when it’s technically sloppy or won’t land with the audience, and earn the trust to do that.

Community Signal, Not Community Ops

• Monitor community sentiment and conversation on social and community channels to inform what content to make next.
• Amplify contributor and community voices as part of the content strategy.
• Light moderation/engagement on owned channels as needed – this is in service of content and strategy, not a standalone community-management function.

What’s Explicitly Out of Scope

This role does not own event logistics, on-site conference representation, swag/booth coordination, or contributor/ambassador program administration. Some occasional travel for content capture (e.g., filming at a conference Percona is already