Editorial Designer

We need to output HTML fragment only, with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no boilerplate, no navigation, legal, EEO, etc. Remove duplicated lines, application instructions. Also remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. We need to parse the posting. Key sections: Overview: description of role. Could be "About the role". We'll put that as

About the role

with

containing overview paragraph(s). Key Responsibilities: list bullet points. We'll put

Responsibilities

with

• each bullet. Required Qualifications: maybe "Requirements" or "Qualifications". The instruction says use headings like Requirements, Qualifications, Skills. We have both Required Qualifications and Preferred Qualifications. Could combine into Requirements and Preferred? But we need to decide. Probably we can have

  Requirements

  for Required Qualifications, and

  Preferred Qualifications

  for Preferred. Also maybe Skills separate? But we can include skills within qualifications. The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can choose appropriate headings. We'll have About the role, Responsibilities, Requirements (Required Qualifications), Preferred Qualifications (maybe as Qualifications?), Skills (maybe we can extract skills from responsibilities? But we could also have a Skills section summarizing required skills: image editing tools, AI tools, copywriting, etc. However we must not invent content; we can only include if posting explicitly states them. The posting includes "Proficiency with image editing and design tools such as Photoshop, Figma, or similar platforms." and "Ability to independently modify, optimize, and prepare visual assets", "Experience leveraging generative AI tools", "Strong attention to detail", etc. Those could go under Skills. But we already have Requirements and Preferred Qualifications sections. Might be redundant. The instruction says prefer a few substantive sections over many thin ones. So we could combine Required and Preferred into one Qualifications section? But they gave examples of both Requirements and Qualifications as possible headings. We need to decide. We have content: Overview, Key Responsibilities, Required Qualifications, Preferred Qualifications, What Success Looks Like, Contract Details, Why This Opportunity, Job Type & Location, Pay And Benefits, Workplace Type, Application Deadline, About TEKsystems (boilerplate), etc. We must remove boilerplate like About TEKsystems, equal opportunity, etc. Also remove Application Deadline? That's maybe metadata but not boilerplate; but it's not a section heading we need to include unless we have a specific section for it. The instruction says do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short

  or drop it. Application Deadline could be minor metadata; we could drop it or include in a short p under About the role? Probably drop. We need to include Pay And Benefits section: they gave pay range and benefits list. So we need

  Pay

  and

  Benefits

  maybe separate or combined? The instruction says include a section ONLY when posting has real specific content for it. Pay And Benefits includes both pay and benefits. Could split into Pay and Benefits sections. We'll do

  Pay

  with p containing pay range.

  Benefits

  with ul of benefits. Workplace Type: hybrid position in New York, NY. Could be under Schedule? Actually Workplace Type is not Schedule. Could be under "Schedule" heading? Not exactly. Could be under "Workplace Type" but not in allowed headings list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map Workplace Type to either Schedule or maybe we can drop it? The instruction: include a section ONLY when posting has real specific content for it — never emit a heading followed by filler/placeholder text. We have content about hybrid position; we could put under Schedule? Not accurate. Could we create a

  Schedule

  and put hybrid info? Might be misleading. Better to drop Workplace Type as minor metadata? But it's substantive: hybrid position in New York, NY. Could be included in About the role paragraph. We'll incorporate location into About the role. Contract Details: six-month contract engagement with potential for extension, opportunity to contribute to major product launch, highly collaborative environment. Could be under About the role or maybe a separate section? Not in allowed headings. Could fold into About the role. Why This Opportunity: could be part of About the role. What Success Looks Like: could be part of About the role or maybe a separate section? Not in allowed headings. Could fold into About the role. Thus we will have sections: About the role (overview + contract details + why + success), Responsibilities, Requirements (Required Qualifications), Preferred Qualifications (maybe as Qualifications?), Skills (maybe we can extract skills from responsibilities? But we already have Required Qualifications includes many skill-like items. Could combine Required and Preferred into Qualifications. But we have both Required and Preferred; we could have Requirements (Required) and Qualifications (Preferred). Or we could have Requirements (Required) and Skills (derived from Required). However we must not invent content; we can list skills explicitly mentioned: proficiency with image editing tools, ability to modify assets, experience leveraging generative AI tools, strong attention to detail, ability to work independently, manage priorities, create structure, etc. Those are in Required Qualifications. So we could have a Skills section listing those. But then Requirements would be maybe experience managing/curating content, demonstrated success writing short-form copy, etc. That seems plausible. Let's extract: Required Qualifications bullet points (each line): - Experience managing or curating content for a high-volume editorial surface such as an app marketplace, content platform, digital publication, media property, or curated feed. - Demonstrated success writing short-form product, editorial, or UX copy within strict character constraints. - Proficiency with image editing and design tools such as Photoshop, Figma, or similar platforms. - Ability to independently modify, optimize, and prepare visual assets without requiring dedicated design support. - Experience leveraging generative AI tools in production workflows with a strong understanding of their strengths, limitations, and appropriate applications. - Strong attention to detail and ability to consistently uphold quality standards across multiple stakeholders with competing priorities. - Ability to work independently, manage priorities, and create structure in an evolving environment. Preferred Qualifications bullet points: - Experience developing content specifications, submission requirements, or creative guidelines for external contributors or partners. - Experience building or maintaining content taxonomies, tagging systems, categorization frameworks, or ranking methodologies. - Familiarity with content review, moderation, compliance, or approval workflows. - Background working at the intersection of content, product, design, and user experience. What Success Looks Like bullet points: - A consistently high-quality discovery experience that highlights the most relevant and engaging content. - Improved partner submission quality over time through clear standards and guidance. - Efficient and scalable content operations that support platform growth. - Clear, compelling, and accurate user-facing copy across all discovery surfaces. - Strong alignment between editorial strategy, platform goals, and user needs. Contract Details bullet points: - Six-month contract engagement with potential for extension. - Opportunity to contribute to a major product launch and its initial growth phase. - Highly collaborative environment working alongside product, design, and content stakeholders. Why This Opportunity bullet points (actually paragraph): - This role offers the chance to shape the content experience for a new and highly visible consumer platform. - You will have significant ownership, influence key user experiences, and play a critical role in defining the content standards and discovery strategy during an important launch period. Overview paragraph: - Our client is seeking an experienced Editorial Designer & Content Curator to own the end-to-end content experience for a discovery platform supporting an emerging consumer hardware product. This individual will be responsible for determining what content is featured, maintaining editorial standards, managing creative assets, writing user-facing copy, and driving a high-quality discovery experience from launch through initial scale. This is a highly autonomous role that combines editorial judgment, content strategy, copywriting, visual asset management, and cross-functional collaboration. The ideal candidate thrives in fast-paced launch environments and enjoys balancing creativity with operational excellence. We can combine Overview, Contract Details, Why This Opportunity, What Success Looks Like into About the role section. Now Responsibilities bullet points (from Key Responsibilities): - Own content curation and prioritization across multiple discovery surfaces, including featured content areas, editorial selections, and top recommendations. - Establish and manage an editorial calendar while maintaining clear rationale for content placement and prioritization decisions. - Define, communicate, and enforce asset quality standards, ensuring all creative submissions meet established specifications and usability requirements. - Partner with external stakeholders to educate and improve content submission quality through clear briefs, guidelines, and feedback loops. - Review, edit, repair, or create visual assets when needed, including image recomposition, cropping, formatting, and optimizing assets for various display surfaces. - Write and edit high volumes of concise, user-facing copy, including titles, descriptions, editorial highlights, and promotional content while adhering to strict character limits. - Apply sound judgment when utilizing AI and generative tools in content production workflows and ensure appropriate governance and transparency. - Collaborate closely with Product, Design, and Partner-facing teams to improve content workflows, tooling, review processes, and platform capabilities. - Identify process gaps and recommend improvements that enhance efficiency, content quality, and scalability. Now Pay: pay range $90.00 - $115.00/hr. Also note about individual compensation factors. We'll include that. Benefits list: Medical, dental & vision; Critical Illness, Accident, and Hospital; 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available; Life Insurance (Voluntary Life & AD&D for the employee and dependents); Short and long-term disability; Health Spending Account (HSA); Transportation benefits; Employee Assistance Program; Time Off/Leave (PTO, Vacation or Sick Leave). We'll list as ul. Schedule: Not explicitly given besides hybrid position. Could we treat Workplace Type as Schedule? Not ideal. The instruction says include a section ONLY when posting has real specific content for it. We have no explicit schedule (e.g., full-time, part-time, hours). So we should not create a Schedule section. Skills: Could we create a Skills section from Required Qualifications? But we already have Requirements and Qualifications sections. Might be redundant. However we could have Requirements (experience) and Skills (tools/proficiencies). Let's see if we can split: Requirements: experience managing/curating content, demonstrated success writing short-form copy. Skills: proficiency with image editing tools, ability to modify assets, experience leveraging generative AI tools, strong attention to detail, ability to work independently, manage priorities, create structure. That seems reasonable and avoids duplication. Preferred Qualifications we can keep as Qualifications section (or Preferred Qualifications). But we already used Qualifications for skills? Hmm. We could have: Requirements (experience), Skills (tools/proficiencies), Preferred Qualifications (preferred). But allowed headings include Requirements, Qualifications, Skills. So we can map: Requirements = Required Qualifications (experience & writing). Qualifications = Preferred Qualifications. Skills = technical proficiencies (image editing, AI tools, attention to detail, independent work). That seems plausible. Let's extract Requirements (experience) bullet points: - Experience managing or curating content for a high-volume editorial surface such as an app marketplace, content platform, digital publication, media property, or curated feed. - Demonstrated success writing short-form product, editorial, or UX copy within strict character constraints. Skills bullet points: - Proficiency