Context and role

As a Content Marketing Coordinator at Digital Extremes, I supported the content and publishing work that helped Warframe updates, events, collaborations, and announcements reach players.

The role sat between writing, editing, asset preparation, schedule tracking, and cross-functional coordination. I worked with marketing, design, and development stakeholders to help content move through review, revision, approval, and delivery.

Not included: confidential screenshots, unreleased information, internal metrics, proprietary documents, or franchise art.

Channels supported

Player-facing deliverables.

I supported content prepared for web, social, and in-product channels. The work included announcements, event and collaboration support, live-service update content, and related player-facing materials.

Web content Social content support In-product messaging Live-service update support Event and collaboration content

Contribution

Writing, editing, footage, and assets.

My day-to-day work included producing and revising player-facing content, preparing gameplay footage and visual assets, and helping materials stay aligned with campaign goals, review feedback, and release timing.

The work required practical communication: understanding what the audience needed to know, what the internal stakeholders needed to approve, and what details had to be ready before publishing.

Coordination

Schedules, approvals, and delivery.

I coordinated publishing schedules, revisions, approvals, and content handoffs across marketing, design, and development teams. That included keeping deliverables moving through edit readiness, review status, and time-sensitive release windows.

This is the part of the work that connects most directly to publishing, PR, communications, marketing operations, and production coordination: making sure creative and informational work has enough structure to reach players on time.

Visibility tracker

Workload visibility alongside Jira.

I proposed and built a shared Excel tracker to complement Jira for a remote team. It helped make assignments, edit readiness, and approval status easier to see at a glance, and the team adopted it as part of the ongoing workflow.

The tracker was useful because it did not try to replace the primary project-management system. It solved a smaller visibility problem with a tool the team could understand and maintain.

Relevant strengths

This experience is most relevant to roles involving:

  • Publishing coordination
  • PR and communications support
  • Marketing operations
  • Content operations
  • Live-service delivery
  • Production coordination

More context.

The Experience page includes this role in chronological context, alongside operations, reporting, and internal communications work from other organizations.

View experience