Interim Proofreader

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading. Use

• for lists. Use

  for prose. Do not repeat job title. Do not include Job ID etc. Remove boilerplate: EEO, etc. Keep substantive info. We need to parse the posting. Key details: - Position: Interim Proofreader (part-time, temporary). Hours: 20-30 hrs/week beginning 11/16/26; incumbent returns part-time 3/15/27; assignment concludes as incumbent returns full-time on 3/28/27 (dates subject to change). Fully remote. Open to 1099 contractors. - Job duties: list many bullet points (starting with _JOB DUTIES:). Need to extract each duty as list items. - Educational/experiential requirements: list items. - Physical/cognitive requirements: list items. - Compensation: Hourly rate range $25.00 to $40.00 per hour. - About Collective Measures: description paragraph. We need sections: About the role (maybe summary), Responsibilities (duties), Requirements (maybe educational/experiential?), Qualifications (maybe similar?), Skills (maybe from requirements?), Benefits (none given), Pay (compensation), Schedule (hours and dates). We must only include sections that have real specific content. So we need to decide which sections to include. We have content for: - About the role: could be the introductory paragraph describing position (part-time, temporary, remote, 1099). That's substantive. - Responsibilities: the job duties list. - Requirements: educational/experiential requirements. - Qualifications: maybe same as requirements? Could combine but we need separate sections only if distinct content. The posting has "EDUCATIONAL/EXPERIENTIAL REQUIREMENTS". Could treat that as Requirements. Qualifications maybe not separate; we could skip Qualifications if no distinct content. But we could treat "Solid understanding..." etc as qualifications. However to avoid thin sections, maybe combine into Requirements and Skills. - Skills: could list specific skills like proficiency with MS Office, knowledge of grammar, AP style, etc. Those are in requirements. Could make a Skills section. - Benefits: none given (no mention of benefits). So omit Benefits. - Pay: compensation range given. - Schedule: hours and dates given. Thus we will include sections: About the role, Responsibilities, Requirements, Skills, Pay, Schedule. We need to ensure we don't create sections with filler like "commensurate with experience". The posting includes "and/or commensurate proofreading or copy-editing experience". That's part of requirement; we should keep it as is. We must not include boilerplate like EEO statement, legal, etc. Remove that. Now craft HTML. Structure:

  About the role

  Collective Measures is seeking an Interim Proofreader to support the team during a parenting leave. This is a part‑time, temporary position that will scale in hours as the assignment progresses. The role is fully remote and open to 1099 contractors. Anticipated schedule: 20–30 hours per week beginning November 16, 2026; the incumbent returns part‑time March 15, 2027, with the assignment concluding as the incumbent returns full‑time on March 28, 2027 (dates subject to change).

  But note schedule details maybe better in Schedule section. So About the role could be brief: description of role, part-time temporary, remote, 1099. We'll keep schedule details in Schedule section. Thus About the role:

  Collective Measures is seeking an Interim Proofreader to support the team during a parenting leave. This is a part‑time, temporary position that will scale in hours as the assignment progresses. The role is fully remote and open to 1099 contractors.

  Responsibilities:

  Responsibilities

  • ... each duty
  We need to extract each duty from the _JOB DUTIES: block. Let's list them: - At key stages: proofread, fact-check, and line-edit large volumes of projects for brand editorial style, accuracy, and appropriateness. - Ensure consistent application of copy standards across multiple concurrent marketing projects. - Review copy and marketing deliverables for correct grammar, spelling, sentence structure, and typographical errors. - Proofread and quality-check paid media and SEO-driven content — including paid search and paid social ad copy, organic/SEO copy, and blog content — for accuracy, agency or client brand voice, and channel-specific style requirements. - Review weekly, monthly, quarterly, and annual client and performance reports for accuracy, consistency, and brand voice. - Proofread and quality-check marketing and internal communications deliverables, including points of view (POVs), blog posts, case studies, website content, and the company newsletter. - Support new business efforts by proofreading and quality-checking RFI and RFP responses, which frequently operate on compressed, deadline-driven timelines. - Apply the appropriate voice and tone for brand-specific and department-specific work. - Articulate best practices and style/grammar choices to project teams. - Review projects at various stages of development, from first-draft copy deck through final, website-ready copy. Make each a
• . Requirements: from _EDUCATIONAL/EXPERIENTIAL REQUIREMENTS: block. List items: - Bachelor's degree in English, Strategic Communications, Journalism, or a related field, and/or commensurate proofreading or copy-editing experience; agency experience preferred. - Solid understanding of the digital publishing and production process, including the ability to recognize layout problems. - Proficiency with Microsoft Office, including the creation, editing, review, and use of documents and spreadsheets. - Thorough knowledge of English grammar, spelling, and punctuation rules. - Familiarity with digital media and SEO terminology — paid search, paid social, organic/SEO copywriting conventions, and industry trends — given that a majority of deliverables in this role are media- and SEO-related. - Familiarity with AP style. - Ability to read and comprehend text rapidly and thoroughly to meet tight and ever-changing deadlines. - Ability to apply relevant standards across a wide variety of publication types. - Comfort managing multiple concurrent deliverables and shifting priorities across departments, including under the tighter turnaround demands of new business responses. We could split into Requirements and Skills. Perhaps Requirements: education/experience. Skills: proficiency with MS Office, grammar knowledge, AP style, digital media/SEO familiarity, ability to read quickly, apply standards, manage multiple deliverables. Physical/cognitive requirements: list items: - Must be able to speak, write, and read English proficiently. - Must be able to sit for extended periods of time. - Must be able to use a keyboard and a telephone. These could be part of Requirements or maybe a separate section but we have no specific heading for physical. Could include under Requirements as well, but we might create a separate section "Physical & Cognitive Requirements". However the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No explicit physical heading. So we could fold them into Requirements or Skills. Probably better to include them under Requirements as they are requirements. Thus Requirements section will include education/experience plus physical/cognitive. Skills section could include specific proficiencies: MS Office, grammar, AP style, digital media/SEO terminology, ability to read quickly, apply standards, manage multiple deliverables. But we might double-count. To avoid thin sections, maybe combine education/experience and skills into Requirements, and skip Skills. However we need to decide. The instruction: "Prefer a few substantive sections over many thin ones." So we could have About the role, Responsibilities, Requirements, Pay, Schedule. That's 5 sections. That seems good. Thus we will not create Skills separate; we will incorporate skill-related items into Requirements. Thus Requirements will contain both education/experience and skill/physical items. Now Pay:

  Pay

  Hourly rate range for this role is $25.00 to $40.00 per hour.

  Schedule:

  Schedule

  Anticipated: 20–30 hours/week beginning 11/16/26; incumbent returns part-time 3/15/27; assignment concludes as incumbent returns full-time on 3/28/27 (dates subject to change). Fully remote position. Open to 1099 contractors.

  Wait we already mentioned remote and 1099 in About the role. To avoid duplication, we could keep remote/1099 in About the role and schedule just hours/dates. But the schedule section should contain schedule specifics. The remote and contractor info could be in About the role. Let's keep schedule: hours and dates. Thus Schedule:

  Anticipated: 20–30 hours/week beginning November 16, 2026; incumbent returns part‑time March 15, 2027; assignment concludes as incumbent returns full‑time on March 28, 2027 (dates subject to change).

  Now About the role: include remote and 1099. Thus About the role:

  Collective Measures is seeking an Interim Proofreader to support the team during a parenting leave. This is a part‑time, temporary position that will scale in hours as the assignment progresses. The role is fully remote and open to 1099 contractors.

  Now we need to ensure we don't repeat any info. The schedule section does not mention remote/1099. Now we need to ensure we preserve all substantive information. Did we miss anything? The "About Collective Measures" paragraph describing the agency: we might want to include that as part of About the role? The instruction says use heading "About the role" for section headings. The "About Collective Measures" is more about the company, not the role. But we could include it under About the role as context. However the instruction says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So About the role likely refers to role description, not company. But we could still include company description under About the role? Might be okay but could be considered not strictly role. However we have no other heading for company info. Could we create a separate section "About Collective Measures"? Not in the list. The instruction says use those headings as examples, but not limited? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It implies those are the expected headings. So we should stick to those. The company description could be placed under About the role as a brief overview, but it's not about the role. However we could incorporate a sentence about the company within About the role: "Collective Measures is the agency brands call when they're ready to move past the noise..." etc. That is substantive and we should preserve it. So we can include that in About the role paragraph. Thus About the role paragraph will include both role description and company overview. Let's craft:

  Collective Measures is seeking an Interim Proofreader to support the team during a parenting leave. This is a part‑time, temporary position that will scale in hours as the assignment progresses. The role is fully remote and open to 1099 contractors. Collective Measures is the agency brands call when they're ready to move past the noise. We don't wait for certainty; we create it. Built at the intersection of media and analytics, we turn raw signals into directions that are clear, actionable, and built to scale. Our work fuses the logic of data with the momentum of conviction, shaping systems that turn constant change