Technical Marketing Lead

About the role

PLOMID’s position is technical or it is nothing: the storage contract, the planner, the status discipline. This role owns how that position reaches the outside world through architecture explainers, documentation direction, release notes and the engineering publication. The standard is simple: everything published must survive reading by the engineers it describes.

What you’ll do

• Write and edit architecture explainers: how the system works, stated precisely.
• Direct documentation priorities: what developers need to learn next, and in what order.
• Own release notes: what changed, what it means for existing users, what to watch.
• Maintain the engineering publication: topics worth explaining, scheduled by substance, not cadence.
• Review every public claim against what the product actually does.

What we’re looking for

• Writing that engineers trust: precise, concrete, free of superlatives.
• Enough systems knowledge to read database code and documentation accurately. You will work from sources, not briefings.
• Editorial judgment: knowing what to leave out, and when a draft is not ready.
• Comfort being the person who says no to a claim the product cannot support yet.

Nice to have

• A public archive of technical writing on databases, infrastructure or distributed systems.
• Documentation tooling experience: static sites, reference generation, versioned docs.
• Familiarity with SQL and the PostgreSQL ecosystem.

What you’ll work on

The documentation, the architecture page, the blog and every release. You will work closest with engineering, because the material only exists if the system does. With the roadmap, timing a claim correctly is half the job.

Why this role matters

Infrastructure is adopted on trust, and trust is built one accurate paragraph at a time. The site already refuses invented customers, benchmarks and partnerships; this role is the person who keeps it that way while making the real story impossible to miss.