A structured content strategist job description template helps you define the role clearly, attract qualified candidates, and set performance expectations. This framework covers essential sections, Canadian regulatory considerations, and how to adapt the template for different organizational contexts.
Start with role title clarity. 'Content Strategist' means different things across organizations, so specify the level upfront: junior/associate strategist, mid-level strategist, senior strategist, or lead/principal. Each tier carries different accountability.
The position summary should state the primary outcome this role exists to produce. Not what they'll do all day, but what changes as a result of their work. For example: developing content frameworks that guide editorial teams, auditing existing content ecosystems and recommending governance models, or building measurement systems that connect content performance to business outcomes.
Key responsibilities break into strategic versus tactical. Strategic: developing content models, creating governance frameworks, conducting audits, establishing taxonomies, defining success metrics. Tactical: writing briefs, managing calendars, coordinating with subject matter experts, maintaining style guides. Most roles blend both, but the ratio determines seniority and compensation. A senior strategist might spend seventy percent on strategy development, while an associate spends thirty percent.
Education requirements matter less than demonstrable skills in this field. Many effective content strategists come from journalism, technical writing, UX research, or marketing without formal credentials in 'content strategy.'
Focus the qualifications section on proven capabilities: experience conducting content audits using structured methodologies, demonstrated ability to build content models or taxonomies, track record developing style guides or governance documentation, proficiency with specific platforms your team uses.
For Canadian contexts, address language requirements explicitly. If the role serves Quebec markets or federal clients, specify bilingual proficiency levels using Canadian Language Benchmarks terminology. Don't assume 'bilingual' is self-evident.
Tool proficiency should name actual systems: content management platforms like WordPress or Contentful, analytics tools like Google Analytics or Adobe Analytics, project management systems like Asana or Monday, documentation platforms like Confluence or Notion. Vague 'familiarity with CMS platforms' tells candidates nothing useful.
The most common mismatch happens when job descriptions promise strategic autonomy but the actual role executes someone else's decisions. Be explicit about decision rights.
Specify what this person owns versus influences versus executes. Does the strategist define the content model independently, or do they recommend approaches that others approve? Do they set editorial standards, or maintain standards that leadership establishes? Can they implement taxonomy changes directly, or do they document recommendations for developer implementation?
Describe reporting structure and cross-functional relationships. A content strategist reporting to a marketing director faces different constraints than one reporting to a chief product officer. Detail which teams they'll collaborate with regularly: design, development, SEO, product management, legal, compliance.
For organizations with distributed content creation, clarify the governance role. Will this person review all content before publication, establish review processes that others follow, or audit content retrospectively? Each approach requires different skills and bandwidth.
Traditional job descriptions often skip defining how success gets measured. For content strategy roles, this creates misalignment quickly.
Outline key performance areas tied to business outcomes, not activity counts. Examples: reduced content duplication across properties, improved content discoverability through better taxonomy implementation, decreased time-to-publish through streamlined governance, increased content reuse through modular frameworks, better user task completion rates from improved information architecture.
Specify deliverables with realistic timeframes. A content audit of a large site might take six to eight weeks. Developing a comprehensive style guide could span three months. Implementing a new taxonomy across an existing CMS might require four to six months including stakeholder alignment.
For Canadian employers, note any accommodation requirements under provincial human rights legislation and employment standards. Remote work expectations, flexible scheduling, and accessibility considerations should appear in this section if they're part of the role's structure.
Salary ranges for content strategists in Canada vary significantly based on strategic scope, industry, and location. Avoid placeholder ranges that don't reflect your actual budget.
In major markets like Toronto, Vancouver, or Montreal, mid-level content strategists typically command higher compensation than in smaller cities, but remote work has compressed some geographic differentials. Consider whether you're hiring for on-site, hybrid, or fully remote work, and how that affects your competitive position.
Beyond base salary, detail other compensation elements: bonuses tied to specific deliverables, professional development budgets for conferences or certifications, tool access or software licenses, flexible work arrangements.
For contract versus permanent roles, specify the distinction clearly. Contract positions often carry higher hourly rates but lack benefits. If you're hiring a contractor, state the expected duration and whether conversion to permanent is possible. This matters particularly in Canada where misclassification between employee and contractor status carries tax implications through CRA.
This framework works as a starting point, not a rigid prescription. Modify based on organizational maturity with content operations.
Organizations new to content strategy need the role to establish foundational systems: creating the first style guide, implementing initial governance, setting up basic measurement. More mature content operations need strategists who can optimize existing systems, integrate new channels, or develop advanced personalization frameworks.
B2B versus B2C contexts shift emphasis. B2B content strategy often involves longer consideration cycles, complex approval chains, technical accuracy requirements, and sales enablement integration. B2C content strategy might prioritize rapid iteration, A/B testing frameworks, seasonal campaign coordination, and social distribution.
Adjust the technical depth based on your stack. Organizations using headless CMS platforms, digital experience platforms, or complex multi-site architectures need strategists comfortable with structured content, APIs, and technical constraints. Simpler environments allow focus on editorial and user experience aspects without deep technical requirements.
Content strategists typically focus on frameworks, governance, and how content gets structured and organized across channels. They build systems that guide creation. Content marketing managers usually own campaign execution, editorial calendars, and promotional distribution. One role architects the approach, the other drives implementation. Many organizations blend these responsibilities, but clear separation helps candidates understand the primary focus and avoids hiring someone expecting creative campaign work when you need information architecture expertise.
Industry experience requirements work best when the content domain requires specialized knowledge: healthcare regulation, financial compliance, technical software documentation. For general web content, editorial processes, or user experience writing, transferable skills often matter more than sector familiarity. Someone who built effective content systems in retail can usually adapt those frameworks to professional services. Requiring industry experience unnecessarily shrinks your candidate pool. Focus instead on the methodology and strategic thinking you need, then evaluate whether domain knowledge is truly prerequisite or learnable on the job.
Specify time zone expectations clearly, particularly if real-time collaboration is required with specific offices or client locations. Note any travel requirements for on-site workshops, stakeholder interviews, or team meetings. Address provincial employment law jurisdiction, especially for benefits and statutory requirements which vary by province. If the role serves Quebec clients or government contracts, state bilingual requirements with proficiency levels. For tools and systems, confirm the candidate can access required platforms from their location and has reliable internet connectivity for video collaboration.
Include the specific CMS platforms your organization uses, analytics tools for measuring content performance, project management systems for coordinating work, and any specialized tools like content inventory platforms, taxonomy management systems, or digital asset management solutions. For roles involving structured content, mention familiarity with content modeling, metadata schemas, or API concepts. SEO knowledge appears frequently but specify the level needed: basic understanding of optimization principles versus technical SEO implementation. Avoid requiring expertise in every possible tool; focus on the systems this person will actually use regularly.
Aim for eight to twelve specific responsibilities that represent the role's actual scope. Too few items feel vague and unhelpful; too many suggest unrealistic expectations or unclear prioritization. Group related tasks together rather than listing every minor activity separately. For each responsibility, use action verbs that convey the level of ownership: 'develop' and 'establish' suggest creation and decision authority, while 'support' and 'assist' indicate contributory roles. This clarity helps candidates assess whether the position matches their experience level and career goals.
Yes, particularly for mid-level and senior roles where organizational context significantly affects the position's scope. Specify who the role reports to directly, which teams or departments they collaborate with regularly, and whether they manage other content creators or strategists. For leadership positions, detail team size and composition. Knowing whether someone joins an established content team or builds content function from scratch helps candidates evaluate fit. Reporting structure also signals strategic priority: a content strategist reporting to the CMO has different influence than one several layers down in a marketing department.