Growth & Digital/Content Manager — job description
EDIT VIA GITHUB · /content
PlanningOpenContractor

Content Manager

Uses the design system in Storybook to assemble pages, and Sanity to keep content current, without requiring custom engineering for routine page work.

JOB DESCRIPTION
edit content/roles/content-manager.md

Uses the design system in Storybook to assemble pages, and Sanity to keep content current, without requiring custom engineering for routine page work.

What you'll do

  • Assemble new pages from existing, approved design-system components in Storybook — no custom component work.
  • Update and maintain content directly in Sanity: copy edits, new sections, asset swaps, and publishing on schedule.
  • Keep every published page consistent with brand and design-system standards, catching drift before it ships.
  • Escalate anything needing a genuinely new component or custom engineering to Full Stack Developer 1/2 rather than improvising a workaround.
  • Maintain a lightweight publishing calendar so Scott's team and the requesting channel teams know what's shipping and when.

About you

  • Comfortable working inside a component-driven page builder (Storybook or a comparable pattern library) — this is an assembly and content role, not a custom-build role.
  • Working knowledge of a headless CMS (Sanity).
  • Enough technical fluency to work correctly inside a design system without breaking it, but no engineering background required.

Nice to have: basic HTML/CSS literacy for troubleshooting minor layout issues before escalating; prior experience in a marketing-ops or web-ops adjacent role.

FILLED BY
T
TBH
Open
REPORTS TO
Scott Weaver — Sr Manager, Web Engineering & Digital Experience
ENGAGEMENT
Contractor · project-based, Redis paper, via Zip
ON TEAM & ACCESS
Content Manager (TBH)
JD SOURCE
Tech-stack framing from a PDF posting, scoped down to assembly-level
RATES & BUDGET
Not shown here by policy — see the Operating Model