Growth Project Manager - Operations (Contract)

Run the team's shipping rhythm: daily ship log, weekly recaps, and async standups.

Hold contractors and pillar leads to weekly experiment targets calibrated to each pillar's complexity.

Maintain a rolling experiment backlog so no one waits for a brief.

Onboard new contractors quickly: first ship within their first week.

Own the experiment tracker: structure, completeness, and consistency across pillars.

Make outcome tagging (worked / didn't / inconclusive) a standard step.

Connect experiment outcomes to the right downstream signals (revenue, registrations, rankings, or visibility) depending on the pillar.

Produce a weekly recap that gives leadership a clear read on what shipped, what worked, and what's next.

Track approval and review SLAs. Surface anything stuck before it becomes a problem.

Map cross-pillar dependencies and resolve them before they block ships.

Flag capacity, performance, or process issues to leadership in real time, with a recommended path forward.

Turn strategic intents into shippable briefs with clear owners, success criteria, and deadlines.

Run a weekly cross-pillar sync — short, written, and focused on collisions and dependencies.

Own quarterly planning logistics: pulling leads together, prepping materials, and producing a written plan.

5 or more years running operations or program management in a high-throughput environment: agency, growth team, or product team shipping experiments weekly.

Has personally built or rebuilt a tracking or operating system from scratch, not just maintained one. Concrete examples expected in the interview.

Comfortable with spreadsheets at the level of pivots and lookups; can read a basic SQL or Looker query.

Async-first communicator. Strong written English. Doesn't let questions sit waiting for a meeting.

Has worked inside a growth function before — SEO, paid, CRO, or lifecycle. You don't need to be a specialist; you do need to read a brief and tell whether it makes sense.

Understands funnel mechanics and the difference between leading and lagging indicators without translation.

Familiarity with at least two of: SEO tools (Ahrefs, Semrush), paid platforms (Google, Meta, LinkedIn Ads), A/B testing tools, and marketing attribution platforms.

Has shipped real outcomes through other people, not just managed tickets. Can articulate the difference between coordinating and project-managing.

Comfortable holding senior contributors accountable to cadence — including people who are more experienced or more credentialed than you.

Can write a one-page brief that turns a vague intent into a shippable experiment.

Knows when to escalate and when to absorb.

Not a status-update role. If the work would be "forwarding emails and updating a Monday board," this isn't it.

Not a pure scrum or agile coaching role. We ship experiments, not sprints.

Not advisory. The role is operational and hands-on.