Social Media Manager
Torentify · United States · 3 wk ago
RemoteRemoteMarketing$45–$55/hrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (maybe combine Required Qualifications and Preferred? but we can have Requirements section), Skills (maybe Skills & Competencies), Benefits (if present), Pay (if present), Schedule (if present). Also Education & Experience maybe part of Requirements? The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have headings: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. Possibly also Qualifications but we can combine. We must not repeat job title as heading. Must preserve all substantive info, no boilerplate. Remove cookie/navigation/legal/EEO etc. Also remove application instructions (like portfolio, case study) maybe considered application instructions? The instruction says remove application instructions. The posting includes "Application Materials Required: * Portfolio showcasing B2B social media work... * Case study demonstrating measurable results..." That's application instructions, so we should remove those lines. Also remove "Education & Experience" maybe not needed as separate heading but we can incorporate into Requirements? The instruction says include a section ONLY when posting has real, specific content for it. Education: "No specific educational requirement is stated" that's filler; we should not create Education section. Experience details are part of Requirements. So we can omit Education & Experience heading.
Work Arrangement & Schedule: includes Location, Work Arrangement, Employment Type, Contract Type, Initial Duration, Start Date, Time Commitment, Meetings, Reporting, Seniority Level, Job Function. Some of these are schedule-related (Time Commitment, Meetings) and others maybe not needed. The instruction: include Schedule section only if posting actually states them. It does state Time Commitment, Meetings, etc. So we can create a Schedule section with those details. Location maybe not schedule but could be included in Schedule or maybe omitted? The instruction didn't forbid location; but we can include location in Schedule or maybe in a short p. However they said "Prefer a few substantive sections over many thin ones." Could combine location into Schedule or maybe into a short p under Schedule. We'll include location as part of Schedule.
Compensation & Benefits: includes Pay Rate, Contract Duration, Benefit: Medical insurance. So we need Pay section (Pay Rate) and Benefits section (Medical insurance). Contract Duration maybe part of Pay or Benefits? Could be included in Pay section as note. We'll include Pay section with rate and contract duration. Benefits section with medical insurance.
Now we need to preserve all substantive info: About the role paragraph, Responsibilities list, Required Qualifications list, Preferred Qualifications maybe we can merge into Requirements or Skills? The instruction: Use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could have Requirements (including Required Qualifications), Preferred Qualifications maybe as part of Requirements or Skills. But we should not lose info. Could create Requirements section with both required and preferred? Or separate Required Qualifications and Preferred Qualifications as subheadings? But only allowed headings are those listed; we could still use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have headings: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. Possibly also Qualifications but we can combine. We must not repeat job title as heading. Must preserve all substantive info, no boilerplate. Remove cookie/navigation/legal/EEO etc. Also remove application instructions (like portfolio, case study) maybe considered application instructions? The instruction says remove application instructions. The posting includes "Application Materials Required: * Portfolio showcasing B2B social media work... * Case study demonstrating measurable results..." That's application instructions, so we should remove those lines. Also remove "Education & Experience" maybe not needed as separate heading but we can incorporate into Requirements? The instruction says include a section ONLY when posting has real, specific content for it. Education: "No specific educational requirement is stated" that's filler; we should not create Education section. Experience details are part of Requirements. So we can omit Education & Experience heading.
Work Arrangement & Schedule: includes Location, Work Arrangement, Employment Type, Contract Type, Initial Duration, Start Date, Time Commitment, Meetings, Reporting, Seniority Level, Job Function. Some of these are schedule-related (Time Commitment, Meetings) and others maybe not needed. The instruction: include Schedule section only if posting actually states them. It does state Time Commitment, Meetings, etc. So we can create a Schedule section with those details. Location maybe not schedule but could be included in Schedule or maybe omitted? The instruction didn't forbid location; but we can include location in Schedule or maybe in a short p. However they said "Prefer a few substantive sections over many thin ones." Could combine location into Schedule or maybe into a short p under Schedule. We'll include location as part of Schedule.
Compensation & Benefits: includes Pay Rate, Contract Duration, Benefit: Medical insurance. So we need Pay section (Pay Rate) and Benefits section (Medical insurance). Contract Duration maybe part of Pay or Benefits? Could be included in Pay section as note. We'll include Pay section with rate and contract duration. Benefits section with medical insurance.
Now we need to preserve all substantive info: About the role paragraph, Responsibilities list, Required Qualifications list, Preferred Qualifications maybe we can merge into Requirements or Skills? The instruction: Use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could have Requirements (including Required Qualifications), Preferred Qualifications maybe as part of Requirements or Skills. But we should not lose info. Could create Requirements section with both required and preferred? Or separate Required Qualifications and Preferred Qualifications as subheadings? But only allowed headings are those listed; we could still use for Required Qualifications and Preferred Qualifications? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive list. It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings; we could also use Qualifications heading. Safer to follow examples: we can have Requirements and Qualifications separate. But we also have Skills & Competencies. So we could have Requirements (maybe required qualifications), Qualifications (maybe preferred?), Skills (skills & competencies). However that may be thin. Better to combine: Requirements (required qualifications), Skills (skills & competencies), and maybe omit Qualifications heading. But we risk losing preferred qualifications info. We could include preferred qualifications inside Requirements as a note or inside Skills. The instruction: "Prefer a few substantive sections over many thin ones." So we should combine. Let's put Required Qualifications under Requirements heading, and include Preferred Qualifications as part of Requirements (maybe as a sublist labeled "Preferred"). Or we could have a separate Qualifications section for preferred. But that would be thin. I'll include both required and preferred under Requirements, with two sublists: Required and Preferred. That's still one section.
Skills & Competencies: we can have Skills section.
Now Benefits: medical insurance.
Pay: $45–$55 per hour, contract duration initial 6 months with potential extension.
Schedule: Location New York, NY, US; Work Arrangement Remote; Employment Type Contract/Freelance; Contract Type Temporary; Initial Duration 6 months, potential extension; Start Date ASAP; Time Commitment 30–40 hours per week; Meetings occasional virtual meetings during EST hours; Reporting Weekly check-ins and monthly performance reviews; Seniority Level Associate; Job Function Marketing.
We should preserve all that info.
Now we need to output only HTML fragment, no /, no markdown fences.
Let's craft:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive list. It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings; we could also use Qualifications heading. Safer to follow examples: we can have Requirements and Qualifications separate. But we also have Skills & Competencies. So we could have Requirements (maybe required qualifications), Qualifications (maybe preferred?), Skills (skills & competencies). However that may be thin. Better to combine: Requirements (required qualifications), Skills (skills & competencies), and maybe omit Qualifications heading. But we risk losing preferred qualifications info. We could include preferred qualifications inside Requirements as a note or inside Skills. The instruction: "Prefer a few substantive sections over many thin ones." So we should combine. Let's put Required Qualifications under Requirements heading, and include Preferred Qualifications as part of Requirements (maybe as a sublist labeled "Preferred"). Or we could have a separate Qualifications section for preferred. But that would be thin. I'll include both required and preferred under Requirements, with two sublists: Required and Preferred. That's still one section.
Skills & Competencies: we can have Skills section.
Now Benefits: medical insurance.
Pay: $45–$55 per hour, contract duration initial 6 months with potential extension.
Schedule: Location New York, NY, US; Work Arrangement Remote; Employment Type Contract/Freelance; Contract Type Temporary; Initial Duration 6 months, potential extension; Start Date ASAP; Time Commitment 30–40 hours per week; Meetings occasional virtual meetings during EST hours; Reporting Weekly check-ins and monthly performance reviews; Seniority Level Associate; Job Function Marketing.
We should preserve all that info.
Now we need to output only HTML fragment, no /, no markdown fences.
Let's craft:
About the role
About the role
... paragraph ...
Responsibilities
- ... each bullet ...
Requirements
Required Qualifications:
- ... each required qualification ...
Preferred Qualifications:
- ... each preferred qualification ...
but better to keep as
with bold. But we must not repeat job title as heading; fine. Now Skills section:
Skills
- ... each skill ...
Benefits
- Medical insurance
Pay
$45–$55 per hour; initial contract duration 6 months with potential for extension.
Schedule:Schedule
- Location: New York, NY, US
- Work Arrangement: Remote
- Employment Type: Contract / Freelance
- Contract Type: Temporary
- Initial Duration: 6 months, with potential for extension
- Start Date: ASAP
- Time Commitment: Approximately 30–40 hours per week
- Meetings: Occasional virtual meetings during EST hours
- Reporting: Weekly check-ins and monthly performance reviews
- Seniority Level: Associate
- Job Function: Marketing