Senior Content Writer
Compound Content Studio · United States · 1 mo ago
RemoteRemoteMarketing$125k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must remove boilerplate like About Us, etc. Must preserve all substantive info.
We need to parse the posting.
Content:
- About Us: not needed (boilerplate). Remove.
- About the role: we have paragraph: "We’re looking for a strong writer who can also operate as a strategic partner. This role combines content execution with strategy and client collaboration. You’ll work with founders and operators to extract ideas, shape positioning, and translate that into high-performing content. You will own the quality and direction of content across client accounts."
That's prose.
- What you'll do: list of duties (bulleted). We'll put under Responsibilities.
- What we're looking for: list of requirements (minimum 5-7 years experience etc). We'll put under Requirements or Qualifications? The instruction: Use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide where each piece goes.
We have "What we're looking for:" bullet list: Minimum 5–7 years of experience in content, copywriting, or related roles; Exceptional writing skills with the ability to adapt voice across clients; Excellent attention to detail; Strong writing fundamentals: clarity, structure, and tone; Experience working with SaaS, tech, or product-led companies; Strong strategic instincts, able to think in messaging, positioning, and audience; Comfortable leading client conversations and guiding direction; Ability to manage multiple accounts without sacrificing quality; Direct experience in an agency or startup environment.
These are requirements/qualifications. Could split into Requirements (experience) and Qualifications (skills). But we can just put under Requirements.
- Nice to have: list of nice-to-have: Experience supporting founder or executive content; Familiarity with LinkedIn as a content and growth channel; Exposure to strategy development, campaigns, performance metrics, and content iteration. Could be under Skills or maybe Qualifications. We'll put under Skills (nice-to-have) maybe.
- What success looks like: list of outcomes: You own content quality and direction across your accounts; Clients trust you as both a writer and a strategic partner; Your work contributes to measurable engagement, audience growth, and client business outcomes; You elevate the quality of content across the team; Within 90 days you have scaled to a full client load. This could be under Responsibilities? Actually it's about success metrics. Could be under a separate section like "Expectations" but not in allowed headings. Could be placed under Responsibilities as additional bullet points? Might be better to include under Responsibilities as they describe expected outcomes. But we already have responsibilities list. Could add a separate section "Expectations" but not allowed. Could incorporate into Responsibilities as additional bullet points. However we must not invent sections; we can only use allowed headings. We could put under Responsibilities (makes sense). Or we could create a section "Qualifications" for success? Not ideal.
Better: Keep Responsibilities for duties, and maybe add a section "Expectations" but not allowed. So we could put success metrics under Responsibilities as additional bullet points (makes sense). Or we could put under "Skills"? Not.
We'll include under Responsibilities both the duties and success metrics.
- Compensation and logistics: "Experience: 5-7+ years; Comp: Up to $125,000; Location: Remote". So we have Pay: Up to $125,000. Schedule? Not mentioned. Benefits? Not mentioned. Growth Path: "This role can grow into Senior Content Strategist / Lead, with expanded ownership across accounts, team mentorship, and creative direction." That's maybe under Benefits? Not exactly benefits but growth path. Could be under Benefits? Or maybe under Qualifications? Not. The instruction: include a section ONLY when posting has real, specific content for it. We have Pay (compensation). So we will include Pay section with that info. Benefits: not mentioned explicitly (no health, etc). So we omit Benefits. Schedule: not mentioned, omit. Experience: we already have in Requirements. Could also include under Pay? Not needed.
- Compound Core Values: This is boilerplate about values; could be considered part of About Us? It's not boilerplate but it's values. Might be considered substantive but not a standard heading. Could we include under About the role? Not really. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Core values might be considered not boilerplate but it's still fluff. However it's substantive about company culture. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep it. But where to put? There's no heading for Culture/Values. Could we create a section "About the role"? Already used. Could we add a section "Values"? Not allowed headings. The allowed headings are limited. We could maybe put under About the role as additional prose. But About the role currently has a paragraph about role description. We could extend that paragraph to include core values? Might be okay but risk of misrepresenting. However the instruction says we must not omit substantive info. So we need to include it somewhere. Perhaps we can create a section "About the role" and include both role description and core values as prose. That seems acceptable: About the role heading can contain prose about the role and also company values? Might be stretching but it's the only place.
Alternatively, we could create a section "Qualifications" and include core values there? Not appropriate.
Better: Keep About the role heading for role description, and then add another heading "Company Values"? Not allowed. So we must embed within allowed headings. Perhaps we can add a section "Skills" and include core values as soft skills? Not ideal.
Given the instruction to prefer a few substantive sections over many thin ones, we could combine About the role and Company Values into About the role section. That would preserve the info.
Thus About the role section will contain: the role description paragraph + core values paragraph(s). We'll keep them as separate for each section.
Sections we will include:
- About the role (contains role description and core values)
- Responsibilities (duties + success metrics)
- Requirements (minimum experience etc)
- Skills (nice-to-have)
- Pay (compensation)
We might also include Qualifications? But we have Requirements covering experience and skills; we could split: Requirements for experience, Qualifications for skills. But we already have Skills for nice-to-have. Could move the main requirements to Qualifications and keep Requirements for experience? Let's see.
We have: Minimum 5–7 years of experience in content, copywriting, or related roles (experience). Exceptional writing skills..., Excellent attention to detail..., Strong writing fundamentals..., Experience working with SaaS..., Strong strategic instincts..., Comfortable leading client conversations..., Ability to manage multiple accounts..., Direct experience in an agency or startup environment.
These are a mix of experience and skills. Could treat all as Requirements. Then Skills for nice-to-have.
Thus we will have:
elements. Now we need to output HTML fragment with headings
for each section.
Sections we will include:
- About the role (contains role description and core values)
- Responsibilities (duties + success metrics)
- Requirements (minimum experience etc)
- Skills (nice-to-have)
- Pay (compensation)
We might also include Qualifications? But we have Requirements covering experience and skills; we could split: Requirements for experience, Qualifications for skills. But we already have Skills for nice-to-have. Could move the main requirements to Qualifications and keep Requirements for experience? Let's see.
We have: Minimum 5–7 years of experience in content, copywriting, or related roles (experience). Exceptional writing skills..., Excellent attention to detail..., Strong writing fundamentals..., Experience working with SaaS..., Strong strategic instincts..., Comfortable leading client conversations..., Ability to manage multiple accounts..., Direct experience in an agency or startup environment.
These are a mix of experience and skills. Could treat all as Requirements. Then Skills for nice-to-have.
Thus we will have:
About the role
role description paragraph
core values paragraph(s)
Responsibilities
- Write high-quality LinkedIn content for founders, executives, and company pages
- Lead development of brand voice, messaging, and content direction
- Partner with clients to extract insights and shape narratives
- Translate complex SaaS and product concepts into clear, engaging content
- Own content quality and consistency across accounts
- Collaborate with peer writers to improve output and efficiency
- Iterate on content based on feedback, performance, and evolving client goals
- Own content quality and direction across your accounts
- Clients trust you as both a writer and a strategic partner
- Your work contributes to measurable engagement, audience growth, and client business outcomes
- You elevate the quality of content across the team
- Within 90 days you have scaled to a full client load
Requirements
- Minimum 5–7 years of experience in content, copywriting, or related roles
- Exceptional writing skills with the ability to adapt voice across clients
- Excellent attention to detail
- Strong writing fundamentals: clarity, structure, and tone
- Experience working with SaaS, tech, or product-led companies
- Strong strategic instincts, able to think in messaging, positioning, and audience
- Comfortable leading client conversations and guiding direction
- Ability to manage multiple accounts without sacrificing quality
- Direct experience in an agency or startup environment
Skills
- Experience supporting founder or executive content
- Familiarity with LinkedIn as a content and growth channel
- Exposure to strategy development, campaigns, performance metrics, and content iteration
Pay
Up to $125,000
We should not include Benefits or Schedule. Check for any leftover substantive info: "Growth Path: This role can grow into Senior Content Strategist / Lead, with expanded ownership across accounts, team mentorship, and creative direction." This is substantive. Where to put? Could be under Pay? Not. Could be under Responsibilities? Maybe as a bullet about growth. Could be under About the role? Could be under Skills? Not. Could be under Qualifications? Not. We need to include it. Perhaps we can add a section "Growth" but not allowed. Could we put under Responsibilities as a bullet? It's about growth path, not a responsibility. Could be under Skills? Not. Maybe we can put under About the role as additional prose: mention growth path. That seems okay: About the role can include description of role and growth potential. Thus we will add a paragraph after core values about growth path. Now check for any other info: "Compound Core Values..." we already included as prose. Check for duplicated lines: We have "You own the quality and direction of content across client accounts." in About the role paragraph. Also in Responsibilities we have "Own content quality and direction across your accounts". Slightly different but okay. Now ensure we didn't include boilerplate like "About Us", "Compound Core Values" heading (we removed heading). We kept the values as prose. Check for any mention of location: Remote. Should we include under Pay? Not. Could add a short paragraph under Pay? But location is not Pay. Could we add a section "Location"? Not allowed. Could we embed location in Pay section? Not ideal. Could we add a short paragraph under About the role? Might be okay: mention location remote. But we already have About the role with prose; we could add a sentence about location. However the instruction: do not put Job ID/requisition numbers as headings — fold minor metadata into a shortor drop it. Location is minor metadata; we could fold into a short
maybe under Pay or under About the role. Since we have Pay section, we could add location there as a separate sentence. But Pay section currently only has compensation. Could add "Location: Remote". That seems okay. Thus Pay section:
Up to $125,000 • Location: Remote
or two? We'll use one
with both. Now check for any other metadata: Experience: 5-7+ years already