Web Content Strategist
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones.
We need to extract relevant content: The posting includes:
- Opening line: "Open to 100% Remote Candidates - Cannot convert candidates FTE who are based in the following states: California, Connecticut, Washington D.C., and OhioConversion salary range is currently $80-90k**Candidates must be able to go W2 directly with client**"
That's a bit garbled: "Conversion salary range is currently $80-90k**Candidates must be able to go W2 directly with client**". Probably they mean conversion salary range $80-90k? Also "Candidates must be able to go W2 directly with client". Also note: "Open to 100% Remote Candidates - Cannot convert candidates FTE who are based in the following states: California, Connecticut, Washington D.C., and Ohio". So we have location restrictions.
Then "Description" heading (but we shouldn't repeat job title). Then description paragraphs.
Then "Key Responsibilities" with bullet points.
Then "Structured Content, Taxonomy, and Governance" etc.
Then "Sitecore Implementation, Optimization, and Quality"
Then "Cross-Functional Project Delivery"
Then "Sitecore Ecosystem and Stakeholder Collaboration"
Then "Qualifications" with Required and Preferred.
Then "Skills" list.
Then "Job Type & Location": "This is a Contract to Hire position based out of Rochester, NY."
Then "Pay And Benefits": pay range $40.00 - $45.00/hr. Benefits list.
Then "Workplace Type": fully remote.
Then "Application Deadline": anticipated to close on Oct 4, 2026.
Then "About TEKsystems" etc (boilerplate). We need to remove boilerplate: legal/EEO etc. So we should drop the "About TEKsystems" paragraphs, equal opportunity statements, etc. Also drop "Application Deadline"? The instruction says remove application instructions. Application deadline maybe considered application instruction? It says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Application deadline is likely an application instruction, so we should drop it. Also "Job Type & Location" maybe we keep location info? It's substantive. "Pay And Benefits" we keep if actual pay and benefits stated. Yes we have pay range and benefits list. So we keep Pay and Benefits sections.
We also have "Workplace Type" fully remote; maybe we can incorporate into location or as a note. Could be part of "Job Type & Location". The instruction says we can have sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We may not need a separate Workplace Type; we can incorporate location and remote info under "About the role" or "Job Type & Location". But we need to follow headings list: they gave examples but not strict requirement to use only those; they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those headings. We should not create other headings like "Job Type & Location" unless we map to one of those. Perhaps we can put location info under "About the role". Or we could create a "Job Type & Location" heading but that's not in the list; better to avoid. Use "About the role" for description, location, remote, contract type, etc. Use "Responsibilities" for duties. Use "Requirements" maybe for qualifications? They have Qualifications section. Could map "Qualifications" to that heading. Use "Skills" for skills list. Use "Pay" for pay range. Use "Benefits" for benefits list. Possibly "Schedule" not present; we can omit.
We must not create sections with filler. So we need to ensure each heading has substantive content.
Let's extract substantive content:
About the role: Should include description of role, remote, contract type, location restrictions, conversion salary range? Actually there is mention of conversion salary range $80-90k (maybe for FTE conversion?). Also "Candidates must be able to go W2 directly with client". Also "Open to 100% Remote Candidates - Cannot convert candidates FTE who are based in the following states: California, Connecticut, Washington D.C., and Ohio". Also "This is a Contract to Hire position based out of Rochester, NY." Also "Workplace Type: fully remote". So we can combine.
Responsibilities: list from Key Responsibilities, Structured Content..., Sitecore Implementation..., Cross-Functional..., Sitecore Ecosystem... We can combine all duty bullets into one Responsibilities section, or split into sub-sections? The instruction says prefer few substantive sections over many thin ones. So we can have one Responsibilities section with all duty bullets.
Requirements: Could be the qualifications required? But we have Qualifications section with Required and Preferred. Could treat Required as Requirements, Preferred as maybe additional qualifications but we could combine into Qualifications section. The heading list includes Requirements and Qualifications both. We could put Required under Requirements, Preferred under Qualifications? Or we could combine both under Qualifications. But we need to avoid filler. Let's decide: Use "Requirements" for required qualifications, and "Qualifications" for preferred qualifications? Or we could use "Qualifications" for both required and preferred, and omit Requirements. The instruction says include a section ONLY when posting has real, specific content for it. We have both required and preferred content, so we could have two sections: Requirements (required) and Qualifications (preferred). That seems reasonable.
Skills: we have a Skills list: Content management, Digital marketing, Marketing communications, Content strategy, Digital content. We'll put under Skills.
Pay: pay range $40.00 - $45.00/hr.
Benefits: list of benefits.
Schedule: not present, so omit.
We must not include boilerplate like "About TEKsystems", equal opportunity, etc.
We must preserve all substantive information: need to keep the conversion salary range $80-90k? That's mentioned in opening line. Also "Candidates must be able to go W2 directly with client". Also location restrictions. Also contract to hire based out of Rochester, NY. Also fully remote. Also application deadline? We'll drop as application instruction.
Also need to keep the description paragraphs about role responsibilities etc (but those are covered in Responsibilities). However the description paragraph includes some details not captured in bullet lists: e.g., "The Web Content Strategist is a time-limited role supporting content strategy, information architecture, governance, content development, and implementation for our client's web modernization efforts. The position translates source material and subject-matter expertise into clear, engaging, structured web content and implements it in Sitecore using approved templates, components, content models, taxonomy, and design standards. The role works across internal teams, agency partners, project management, change management, analytics, DAM, search, and subject-matter experts to ensure content supports audience needs, brand standards, accessibility, SEO/GEO, analytics, reuse, and measurable engagement goals. Working within established direction and governance, the strategist is expected to exercise independent judgment, manage assigned work through completion, and ensure quality and on-time delivery." This is substantive; we should include it in About the role (or maybe as part of Responsibilities). Since it's a description of the role, we can put in About the role.
Now we need to format as HTML fragment: use for section headings, - for lists,
for prose.
We need to ensure we don't repeat job title as heading. The job title is "Web Content Strategist". We'll not use that as heading.
We need to drop duplicated lines.
Let's craft sections:
About the role
Open to 100% remote candidates. Candidates based in California, Connecticut, Washington D.C., or Ohio cannot be converted to FTE. This is a contract‑to‑hire position based out of Rochester, NY, with the ability to work fully remote. The role is time‑limited, supporting the client’s web modernization effort through content strategy, information architecture, governance, content development, and implementation in Sitecore. The strategist translates source material and subject‑matter expert input into clear, engaging, structured web content, applies approved templates, components, content models, taxonomy, and design standards, and works across internal teams, agency partners, project management, change management, analytics, DAM, search, and subject‑matter experts to ensure content meets audience needs, brand standards, accessibility, SEO/GEO, analytics, reuse, and measurable engagement goals. Working within established direction and governance, the strategist exercises independent judgment, manages assigned work to completion, and ensures quality and on‑time delivery. Candidates must be able to go W2 directly with the client. The conversion salary range for this role is $80,000–$90,000.
That seems to capture all.
Now Responsibilities: combine all duty bullet points from Key Responsibilities, Structured Content..., Sitecore Implementation..., Cross-Functional..., Sitecore Ecosystem...
We need to extract each bullet.
Let's list them:
From Key Responsibilities:
- Support development, refinement, and implementation of content strategies for highly visible website projects
- Translate institutional content and subject-matter expert input into concise, audience-centered web content.
- Draft, edit, and optimize page copy, headlines, calls to action, summaries, metadata, information architecture frameworks, and other digital content.
- Structure content around audience personas, user journeys, engagement goals, and business objectives.
- Apply established brand, voice and tone, editorial, accessibility, and content design standards.
- Identify content gaps, duplication, inconsistencies, and opportunities for consolidation, reuse, or syndication.
From Structured Content, Taxonomy, and Governance:
- Support development and implementation of structured content models, taxonomies, metadata, and controlled vocabularies that enable content reuse, filtering, search, aggregation, personalization, and dynamic syndication.
- Apply established content types, fields, relationships, taxonomy, and metadata consistently when developing or migrating content.
- Support content governance standards and practices related to ownership, lifecycle, review, approval, publishing, archiving, and ongoing maintenance.
- Work with content, UX, search, analytics, DAM, and technical teams to ensure content structures and taxonomy support audience and business needs and can scale to future use cases.
From Sitecore Implementation, Optimization, and Quality:
- Build and maintain pages and structured content in Sitecore using approved templates, components, content models, taxonomy, and design-system standards.
- Translate content and page requirements into appropriate page structures, components, and reusable content objects.
- Support content migration, mapping, entry, review, testing, and launch-readiness activities.
- Apply SEO and GEO practices to content structure, headings, metadata, internal linking, and copy to improve search visibility and engagement.
- Partner with the Web Analytics Lead to align content with KPIs, tracking requirements, and performance goals and use available data to inform optimization.
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to extract relevant content: The posting includes: - Opening line: "Open to 100% Remote Candidates - Cannot convert candidates FTE who are based in the following states: California, Connecticut, Washington D.C., and OhioConversion salary range is currently $80-90k**Candidates must be able to go W2 directly with client**" That's a bit garbled: "Conversion salary range is currently $80-90k**Candidates must be able to go W2 directly with client**". Probably they mean conversion salary range $80-90k? Also "Candidates must be able to go W2 directly with client". Also note: "Open to 100% Remote Candidates - Cannot convert candidates FTE who are based in the following states: California, Connecticut, Washington D.C., and Ohio". So we have location restrictions. Then "Description" heading (but we shouldn't repeat job title). Then description paragraphs. Then "Key Responsibilities" with bullet points. Then "Structured Content, Taxonomy, and Governance" etc. Then "Sitecore Implementation, Optimization, and Quality" Then "Cross-Functional Project Delivery" Then "Sitecore Ecosystem and Stakeholder Collaboration" Then "Qualifications" with Required and Preferred. Then "Skills" list. Then "Job Type & Location": "This is a Contract to Hire position based out of Rochester, NY." Then "Pay And Benefits": pay range $40.00 - $45.00/hr. Benefits list. Then "Workplace Type": fully remote. Then "Application Deadline": anticipated to close on Oct 4, 2026. Then "About TEKsystems" etc (boilerplate). We need to remove boilerplate: legal/EEO etc. So we should drop the "About TEKsystems" paragraphs, equal opportunity statements, etc. Also drop "Application Deadline"? The instruction says remove application instructions. Application deadline maybe considered application instruction? It says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Application deadline is likely an application instruction, so we should drop it. Also "Job Type & Location" maybe we keep location info? It's substantive. "Pay And Benefits" we keep if actual pay and benefits stated. Yes we have pay range and benefits list. So we keep Pay and Benefits sections. We also have "Workplace Type" fully remote; maybe we can incorporate into location or as a note. Could be part of "Job Type & Location". The instruction says we can have sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We may not need a separate Workplace Type; we can incorporate location and remote info under "About the role" or "Job Type & Location". But we need to follow headings list: they gave examples but not strict requirement to use only those; they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those headings. We should not create other headings like "Job Type & Location" unless we map to one of those. Perhaps we can put location info under "About the role". Or we could create a "Job Type & Location" heading but that's not in the list; better to avoid. Use "About the role" for description, location, remote, contract type, etc. Use "Responsibilities" for duties. Use "Requirements" maybe for qualifications? They have Qualifications section. Could map "Qualifications" to that heading. Use "Skills" for skills list. Use "Pay" for pay range. Use "Benefits" for benefits list. Possibly "Schedule" not present; we can omit.
We must not create sections with filler. So we need to ensure each heading has substantive content.
Let's extract substantive content:
About the role: Should include description of role, remote, contract type, location restrictions, conversion salary range? Actually there is mention of conversion salary range $80-90k (maybe for FTE conversion?). Also "Candidates must be able to go W2 directly with client". Also "Open to 100% Remote Candidates - Cannot convert candidates FTE who are based in the following states: California, Connecticut, Washington D.C., and Ohio". Also "This is a Contract to Hire position based out of Rochester, NY." Also "Workplace Type: fully remote". So we can combine.
Responsibilities: list from Key Responsibilities, Structured Content..., Sitecore Implementation..., Cross-Functional..., Sitecore Ecosystem... We can combine all duty bullets into one Responsibilities section, or split into sub-sections? The instruction says prefer few substantive sections over many thin ones. So we can have one Responsibilities section with all duty bullets.
Requirements: Could be the qualifications required? But we have Qualifications section with Required and Preferred. Could treat Required as Requirements, Preferred as maybe additional qualifications but we could combine into Qualifications section. The heading list includes Requirements and Qualifications both. We could put Required under Requirements, Preferred under Qualifications? Or we could combine both under Qualifications. But we need to avoid filler. Let's decide: Use "Requirements" for required qualifications, and "Qualifications" for preferred qualifications? Or we could use "Qualifications" for both required and preferred, and omit Requirements. The instruction says include a section ONLY when posting has real, specific content for it. We have both required and preferred content, so we could have two sections: Requirements (required) and Qualifications (preferred). That seems reasonable.
Skills: we have a Skills list: Content management, Digital marketing, Marketing communications, Content strategy, Digital content. We'll put under Skills.
Pay: pay range $40.00 - $45.00/hr.
Benefits: list of benefits.
Schedule: not present, so omit.
We must not include boilerplate like "About TEKsystems", equal opportunity, etc.
We must preserve all substantive information: need to keep the conversion salary range $80-90k? That's mentioned in opening line. Also "Candidates must be able to go W2 directly with client". Also location restrictions. Also contract to hire based out of Rochester, NY. Also fully remote. Also application deadline? We'll drop as application instruction.
Also need to keep the description paragraphs about role responsibilities etc (but those are covered in Responsibilities). However the description paragraph includes some details not captured in bullet lists: e.g., "The Web Content Strategist is a time-limited role supporting content strategy, information architecture, governance, content development, and implementation for our client's web modernization efforts. The position translates source material and subject-matter expertise into clear, engaging, structured web content and implements it in Sitecore using approved templates, components, content models, taxonomy, and design standards. The role works across internal teams, agency partners, project management, change management, analytics, DAM, search, and subject-matter experts to ensure content supports audience needs, brand standards, accessibility, SEO/GEO, analytics, reuse, and measurable engagement goals. Working within established direction and governance, the strategist is expected to exercise independent judgment, manage assigned work through completion, and ensure quality and on-time delivery." This is substantive; we should include it in About the role (or maybe as part of Responsibilities). Since it's a description of the role, we can put in About the role.
Now we need to format as HTML fragment: use for section headings, - for lists,
for prose.
We need to ensure we don't repeat job title as heading. The job title is "Web Content Strategist". We'll not use that as heading.
We need to drop duplicated lines.
Let's craft sections:
About the role
Open to 100% remote candidates. Candidates based in California, Connecticut, Washington D.C., or Ohio cannot be converted to FTE. This is a contract‑to‑hire position based out of Rochester, NY, with the ability to work fully remote. The role is time‑limited, supporting the client’s web modernization effort through content strategy, information architecture, governance, content development, and implementation in Sitecore. The strategist translates source material and subject‑matter expert input into clear, engaging, structured web content, applies approved templates, components, content models, taxonomy, and design standards, and works across internal teams, agency partners, project management, change management, analytics, DAM, search, and subject‑matter experts to ensure content meets audience needs, brand standards, accessibility, SEO/GEO, analytics, reuse, and measurable engagement goals. Working within established direction and governance, the strategist exercises independent judgment, manages assigned work to completion, and ensures quality and on‑time delivery. Candidates must be able to go W2 directly with the client. The conversion salary range for this role is $80,000–$90,000.
That seems to capture all.
Now Responsibilities: combine all duty bullet points from Key Responsibilities, Structured Content..., Sitecore Implementation..., Cross-Functional..., Sitecore Ecosystem...
We need to extract each bullet.
Let's list them:
From Key Responsibilities:
- Support development, refinement, and implementation of content strategies for highly visible website projects
- Translate institutional content and subject-matter expert input into concise, audience-centered web content.
- Draft, edit, and optimize page copy, headlines, calls to action, summaries, metadata, information architecture frameworks, and other digital content.
- Structure content around audience personas, user journeys, engagement goals, and business objectives.
- Apply established brand, voice and tone, editorial, accessibility, and content design standards.
- Identify content gaps, duplication, inconsistencies, and opportunities for consolidation, reuse, or syndication.
From Structured Content, Taxonomy, and Governance:
- Support development and implementation of structured content models, taxonomies, metadata, and controlled vocabularies that enable content reuse, filtering, search, aggregation, personalization, and dynamic syndication.
- Apply established content types, fields, relationships, taxonomy, and metadata consistently when developing or migrating content.
- Support content governance standards and practices related to ownership, lifecycle, review, approval, publishing, archiving, and ongoing maintenance.
- Work with content, UX, search, analytics, DAM, and technical teams to ensure content structures and taxonomy support audience and business needs and can scale to future use cases.
From Sitecore Implementation, Optimization, and Quality:
- Build and maintain pages and structured content in Sitecore using approved templates, components, content models, taxonomy, and design-system standards.
- Translate content and page requirements into appropriate page structures, components, and reusable content objects.
- Support content migration, mapping, entry, review, testing, and launch-readiness activities.
- Apply SEO and GEO practices to content structure, headings, metadata, internal linking, and copy to improve search visibility and engagement.
- Partner with the Web Analytics Lead to align content with KPIs, tracking requirements, and performance goals and use available data to inform optimization.
- for lists,
for prose. We need to ensure we don't repeat job title as heading. The job title is "Web Content Strategist". We'll not use that as heading. We need to drop duplicated lines. Let's craft sections:
About the role
Open to 100% remote candidates. Candidates based in California, Connecticut, Washington D.C., or Ohio cannot be converted to FTE. This is a contract‑to‑hire position based out of Rochester, NY, with the ability to work fully remote. The role is time‑limited, supporting the client’s web modernization effort through content strategy, information architecture, governance, content development, and implementation in Sitecore. The strategist translates source material and subject‑matter expert input into clear, engaging, structured web content, applies approved templates, components, content models, taxonomy, and design standards, and works across internal teams, agency partners, project management, change management, analytics, DAM, search, and subject‑matter experts to ensure content meets audience needs, brand standards, accessibility, SEO/GEO, analytics, reuse, and measurable engagement goals. Working within established direction and governance, the strategist exercises independent judgment, manages assigned work to completion, and ensures quality and on‑time delivery. Candidates must be able to go W2 directly with the client. The conversion salary range for this role is $80,000–$90,000.
That seems to capture all. Now Responsibilities: combine all duty bullet points from Key Responsibilities, Structured Content..., Sitecore Implementation..., Cross-Functional..., Sitecore Ecosystem... We need to extract each bullet. Let's list them: From Key Responsibilities: - Support development, refinement, and implementation of content strategies for highly visible website projects - Translate institutional content and subject-matter expert input into concise, audience-centered web content. - Draft, edit, and optimize page copy, headlines, calls to action, summaries, metadata, information architecture frameworks, and other digital content. - Structure content around audience personas, user journeys, engagement goals, and business objectives. - Apply established brand, voice and tone, editorial, accessibility, and content design standards. - Identify content gaps, duplication, inconsistencies, and opportunities for consolidation, reuse, or syndication. From Structured Content, Taxonomy, and Governance: - Support development and implementation of structured content models, taxonomies, metadata, and controlled vocabularies that enable content reuse, filtering, search, aggregation, personalization, and dynamic syndication. - Apply established content types, fields, relationships, taxonomy, and metadata consistently when developing or migrating content. - Support content governance standards and practices related to ownership, lifecycle, review, approval, publishing, archiving, and ongoing maintenance. - Work with content, UX, search, analytics, DAM, and technical teams to ensure content structures and taxonomy support audience and business needs and can scale to future use cases. From Sitecore Implementation, Optimization, and Quality: - Build and maintain pages and structured content in Sitecore using approved templates, components, content models, taxonomy, and design-system standards. - Translate content and page requirements into appropriate page structures, components, and reusable content objects. - Support content migration, mapping, entry, review, testing, and launch-readiness activities. - Apply SEO and GEO practices to content structure, headings, metadata, internal linking, and copy to improve search visibility and engagement. - Partner with the Web Analytics Lead to align content with KPIs, tracking requirements, and performance goals and use available data to inform optimization.