Media Relations Strategist
Archetype · New York, NY · 3 wk ago
HybridMarketing$125k–$164k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually we have "The Role" and "What You Do", "What You Offer", "Why Archetype". Also location maybe part of "What You Offer"? Actually location is separate line after "What You Offer". Should we include a "Location" section? The rules: include a section ONLY when posting has real, specific content for it. Location is specific: San Francisco strongly preferred; New York City also considered. So we can include a "Location" section. Also Pay: we have salary range $125,000–$164,000 DOE. That's specific, so include Pay section. Benefits: many benefits listed: 401k with match, generous employer contributions toward insurance premiums, paid mental health benefits, paid sabbatical after every 6 years, paid short-term disability, extensive parental leave benefits, Archetype Academy, mentorship, etc. So Benefits section. Schedule? Not mentioned. So omit Schedule. Also we need headings: for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can use those headings if appropriate. The posting has sections: "The Role" (maybe About the role), "What You Do" (Responsibilities), "What You Offer" (Requirements/Qualifications/Skills?), "Why Archetype" (Benefits? Actually that's culture). But we need to map to allowed headings. We can use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should only include those that have content.
We have:
- About the role: could be the introductory paragraph about Archetype and the role description? The "The Role" section describes role. So we can put that under About the role.
- Responsibilities: "What You Do" list.
- Requirements/Qualifications/Skills: "What You Offer" includes experience, skills, etc. Could split into Requirements and Skills. But we can combine into Requirements or Qualifications. Since we prefer few substantive sections, we could have Requirements (includes experience, skills). Or we could have Qualifications and Skills separate if content distinct. Let's see: "What You Offer" includes: 7-9+ years experience, prior agency experience, proven record, media instincts, ability to win over reporters, love of media relations, ability to learn complex businesses, strong client counsel, exceptional writing/editing, ability to move among accounts, experience coaching, curious proactive approach, champion AI tools, ability to travel. That's a mix of qualifications and skills. Could put under Requirements.
- Benefits: benefits list.
- Pay: salary range.
- Location: not in allowed headings list but we could still include as a heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can use those headings if appropriate. The posting has sections: "The Role" (maybe About the role), "What You Do" (Responsibilities), "What You Offer" (Requirements/Qualifications/Skills?), "Why Archetype" (Benefits? Actually that's culture). But we need to map to allowed headings. We can use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should only include those that have content.
We have:
- About the role: could be the introductory paragraph about Archetype and the role description? The "The Role" section describes role. So we can put that under About the role.
- Responsibilities: "What You Do" list.
- Requirements/Qualifications/Skills: "What You Offer" includes experience, skills, etc. Could split into Requirements and Skills. But we can combine into Requirements or Qualifications. Since we prefer few substantive sections, we could have Requirements (includes experience, skills). Or we could have Qualifications and Skills separate if content distinct. Let's see: "What You Offer" includes: 7-9+ years experience, prior agency experience, proven record, media instincts, ability to win over reporters, love of media relations, ability to learn complex businesses, strong client counsel, exceptional writing/editing, ability to move among accounts, experience coaching, curious proactive approach, champion AI tools, ability to travel. That's a mix of qualifications and skills. Could put under Requirements.
- Benefits: benefits list.
- Pay: salary range.
- Location: not in allowed headings list but we could still include as a heading? 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? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. Location not listed, but we could incorporate location into About the role or Pay? Probably better to include location in About the role paragraph. We'll embed location there.
Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay.
We must not repeat job title as heading. The job title is "Media Relations Strategist, Account Director". We'll not use that.
We need to preserve all substantive information, no boilerplate. Remove EEO etc. The posting includes some EEO-like statements about diversity etc. Those are boilerplate? They are about culture but also part of "Why Archetype". Might be considered boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The diversity statements could be considered EEO boilerplate. However they are part of "Why Archetype" describing culture. Might be okay to keep as part of Benefits? But they are more about culture. The "Why Archetype" section includes a lot of repetitive statements about diversity, B Corp, etc. Some of that may be considered boilerplate. However we need to preserve ALL substantive information; do not invent or summarize away detail. The diversity statements are substantive about company values. Not sure if they consider them boilerplate. The instruction says remove EEO/equal-opportunity boilerplate. Those statements are about diversity, equity, inclusion, which is EEO-related. Might be considered boilerplate. But they also include B Corp, flexible work, etc. Might be okay to keep some but we need to be safe. Perhaps we can keep a summarized version? But we cannot summarize away detail. We could keep the unique parts: "We’re now a Certified B Corporation in North America...", "We offer a unique working environment that encourages people to try new things without fear of failure. We work flexibly, we’re agile, and we’re not afraid to experiment". That's substantive. The repeated diversity statements could be trimmed? But we must not invent or summarize away detail. If we remove them, we are summarizing away detail. So better to keep them.
Thus "Why Archetype" could be part of Benefits? Actually benefits are compensation and perks. Culture is separate. But we don't have a heading for Culture. Could we put under Benefits? Might be okay to include culture in Benefits section as part of "Why Archetype". But the instruction says include a section ONLY when posting has real, specific content for it. So we could have a "Benefits" section that includes both tangible benefits and culture/values. That's acceptable.
Thus sections:
- About the role: includes intro about Archetype and the role description (The Role paragraph). Also location.
- Responsibilities: "What You Do" list.
- Requirements: "What You Offer" list (experience, skills, etc.)
- Benefits: includes compensation? Actually Pay separate. Benefits includes 401k, insurance, mental health, sabbatical, disability, parental leave, Archetype Academy, mentorship, culture, B Corp, flexible work, etc.
- Pay: salary range.
We must not include Schedule.
Now format: Use for each section heading. Then content: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. Location not listed, but we could incorporate location into About the role or Pay? Probably better to include location in About the role paragraph. We'll embed location there.
Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay.
We must not repeat job title as heading. The job title is "Media Relations Strategist, Account Director". We'll not use that.
We need to preserve all substantive information, no boilerplate. Remove EEO etc. The posting includes some EEO-like statements about diversity etc. Those are boilerplate? They are about culture but also part of "Why Archetype". Might be considered boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The diversity statements could be considered EEO boilerplate. However they are part of "Why Archetype" describing culture. Might be okay to keep as part of Benefits? But they are more about culture. The "Why Archetype" section includes a lot of repetitive statements about diversity, B Corp, etc. Some of that may be considered boilerplate. However we need to preserve ALL substantive information; do not invent or summarize away detail. The diversity statements are substantive about company values. Not sure if they consider them boilerplate. The instruction says remove EEO/equal-opportunity boilerplate. Those statements are about diversity, equity, inclusion, which is EEO-related. Might be considered boilerplate. But they also include B Corp, flexible work, etc. Might be okay to keep some but we need to be safe. Perhaps we can keep a summarized version? But we cannot summarize away detail. We could keep the unique parts: "We’re now a Certified B Corporation in North America...", "We offer a unique working environment that encourages people to try new things without fear of failure. We work flexibly, we’re agile, and we’re not afraid to experiment". That's substantive. The repeated diversity statements could be trimmed? But we must not invent or summarize away detail. If we remove them, we are summarizing away detail. So better to keep them.
Thus "Why Archetype" could be part of Benefits? Actually benefits are compensation and perks. Culture is separate. But we don't have a heading for Culture. Could we put under Benefits? Might be okay to include culture in Benefits section as part of "Why Archetype". But the instruction says include a section ONLY when posting has real, specific content for it. So we could have a "Benefits" section that includes both tangible benefits and culture/values. That's acceptable.
Thus sections:
- About the role: includes intro about Archetype and the role description (The Role paragraph). Also location.
- Responsibilities: "What You Do" list.
- Requirements: "What You Offer" list (experience, skills, etc.)
- Benefits: includes compensation? Actually Pay separate. Benefits includes 401k, insurance, mental health, sabbatical, disability, parental leave, Archetype Academy, mentorship, culture, B Corp, flexible work, etc.
- Pay: salary range.
We must not include Schedule.
Now format: Use for each section heading. Then content: use
for prose,
- for lists.
We need to preserve all substantive information. Let's extract.
About the role: combine the introductory paragraphs before "The Role". The text:
"Media Relations Strategist, Account Director We Are Archetype At Archetype, you help clients think bigger, go further, and achieve more. With years of experience and 21 offices worldwide, you join a team of 650+ creative individuals turning ambitions into success with the close culture and vibe of a smaller boutique agency. Our people are the heart of our achievements. Whether you're starting out or a seasoned pro, if you take pride in your work and have bold ambitions, Archetype might be the place for you. You are a creative thinker, problem solver, and storyteller. You thrive in a high-energy, high-standard environment, where curiosity is encouraged, ambition celebrated, and kindness valued. As a self-motivated storyteller, you break new ground with strategic, creative campaigns. Your unique ideas and perspectives help us do our best work and make a difference in the world. The Role We’re looking for a Media Relations Strategist at the Account Director level to join our North American team. This is a senior, hands-on specialist role for someone who loves the chase: finding the story, understanding how reporters think, pitching with purpose and turning strong ideas into meaningful coverage. Rather than owning day-to-day account management, you’ll work across a select portfolio of technology clients, quickly immersing yourself in their businesses and partnering with account teams to build and execute media strategies, strengthen media relationships and engage in outreach that deliver results. You’ll be called on when teams need sharp media counsel, a fresh angle, or experienced hands to unlock coverage. You’ll advise clients and teams on announcements, executive visibility, proactive storytelling, and fast-moving news moments while personally pitching and building momentum with media. You’ll also help raise the agency’s media craft by coaching colleagues, sharing market intelligence, and contributing to agency-wide media initiatives. This role is based in San Francisco (strongly preferred) or New York City."
We need to avoid repeating the job title as heading, but we can keep the introductory sentences that mention "We Are Archetype". The job title appears at start: "Media Relations Strategist, Account Director We Are Archetype". We should not repeat the job title as a heading, but we can keep it in the paragraph? The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid it in paragraph. So we can keep it.
Thus About the role paragraph will include all that up to location.
Now Responsibilities: "What You Do" bullet list (actually each line starts with a verb). We'll make
- each line. List items: - Lead earned media strategy and execution across a portfolio of technology clients, flexing between accounts and priorities as needs emerge - Quickly get up to speed on new clients, industries, products, and competitive landscapes to identify the stories that will resonate with media - Develop creative, differentiated pitch angles that connect client stories to broader business, technology, and cultural conversations - Personally pitch reporters, editors, and other influential voices, bringing persistence, strong judgment, and a willingness to keep pushing when the first approach doesn’t land - Drive consistent, high-quality media coverage and results across business, technology, and relevant industry trade outlets - Advise account teams and clients on media strategy, newsworthiness, timing, announcement approaches, and the current media landscape - Spot proactive, reactive, and rapid-response opportunities and move quickly to turn them into meaningful client moments - Counsel and prepare executives for interviews, translating complex subject matter into clear, compelling narratives - Draft and sharpen pitches, press releases, bylines, media plans, briefing materials, and other media-facing content - Partner with senior media trainers on executive preparation and build toward leading media trainings independently over time - Coach colleagues and junior staff on media strategy, pitching, reporter engagement, and storytelling to strengthen media relations skills across the agency - Lead or contribute to media brainstorms, reporter conversations, trainings, and other agency-wide initiatives that keep teams connected to the evolving media landscape - Support new business through media research, audits, creative ideation, targeting, and pitch strategy Now Requirements: "What You Offer" list. We need to capture each bullet. List: - 7–9+ years of preferred experience in public relations, communications, or media relations, with significant hands-on hands-on experience securing earned media coverage - Preferred prior agency experience, particularly supporting technology brands across areas such as AI, enterprise software, cybersecurity, infrastructure, start-up, hardware, SaaS, or other complex B2B categories - A proven record of consistently landing meaningful coverage in business, technology, and industry trade and top-tier media - Excellent media instincts and editorial judgment, with a strong understanding of what makes a story relevant, timely, differentiated, and worth a reporter’s attention - The ability to win over reporters you may not already know; an existing media network is valuable, but curiosity, creativity, and the ability to build new relationships are essential - A genuine love of media relations and the persistence to navigate rejection, change direction, and keep pursuing the story until you land interest - The ability to quickly learn complex businesses and technical subject matter without needing to become the deepest subject-matter expert on every account - Strong client counsel and executive presence, with confidence advising teams and senior stakeholders in real time - Exceptional writing, editing, storytelling, and verbal communication skills - The ability to move fluidly among multiple accounts and workstreams, prioritize effectively, and operate with a high degree of autonomy - Experience coaching or mentoring colleagues and a desire to help build stronger media relations capabilities across teams - A curious, proactive, solutions-oriented approach and an appetite