Senior Account Executive, PR
for 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 as heading. Must not include Job ID etc. Remove boilerplate.
We need to parse the posting.
Content:
- About Us: description of company. Probably not needed as a section? Could be "About Us" but not listed as allowed headings. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to these.
We have "About You" which is requirements/qualifications/skills. "About This Role" is description of role. Then "What You’ll Be Doing" is responsibilities. Then "Compensation" with salary range. Then "Codeword Benefits" list. Then "A Few More Things You Should Know About Codeword" maybe not needed; could be omitted as boilerplate? It's more culture but maybe could be considered "About the role"? But we already have About This Role. The extra culture could be omitted as not required.
We must not create sections with filler. So we need sections: About the role (from About This Role), Responsibilities (What You’ll Be Doing), Requirements (maybe from About You), Qualifications (maybe overlapping), Skills (maybe from About You), Benefits (list), Pay (salary range). Schedule not present, so omit.
We must not repeat job title as heading. No Job ID.
We must preserve all substantive information. So we need to include details from About Us? Not required headings; maybe we could include as a paragraph under About the role? But About the role should be about the role, not company. However we could include About Us as a paragraph before sections? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use h3 for section headings (e.g those). Likely we should only use those headings. Could we include a paragraph about company before sections? Possibly but not required. The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." It didn't say we cannot have other elements like
for prose. So we could include a brief intro paragraph about company as
before sections. That would preserve info. But we must not invent or summarize away detail. We can keep About Us as a paragraph. Similarly, "A Few More Things You Should Know About Codeword" could be a paragraph under maybe "About the role"? But it's more culture; we could include as a paragraph after Benefits maybe as a generic
but not under a heading. That's okay. We must not include EEO boilerplate etc. The posting includes Equal Opportunity and Diversity and Inclusion statements at the end. Those are boilerplate; we should remove them. Also remove "A Few More Things You Should Know About Codeword" maybe not boilerplate but could be kept as culture. It's not duplicated lines. It's substantive? It's about culture; we could keep as a paragraph. Now let's extract content. About Us paragraph: "Codeword is a communication agency that helps brands create breakthrough comms, content, and community experiences. We’re a fast-moving team of writers, editors, designers, strategists, videographers, PR mavens, and even a few traditional marketers. Our incredible roster of global brands trust us to launch their startups, run multi-channel campaigns, grow their user bases, and lead comprehensive PR and marketing initiatives. We're storytellers and brand engineers, and we love big ideas that serve a real purpose. Codeword is a remote-first agency, with physical offices in NYC and SF that we won’t make you visit." That's substantive. About You (requirements/qualifications/skills): - 3+ years of experience in tech (B2B and/or consumer) - You have your ear to the ground on the latest in media, are an avid trendspotter, and bring creative thinking to storytelling. - You are comfortable servicing a broad range of clients, from nimble startups to large enterprises and publicly traded companies, matching the tone to reinforce client confidence. - You thrive in a high-context, low-control environment, taking ownership of deliverables (e.g. first-drafts of pitches and story-angles) without waiting for step-by-step direction. - You treat media relationships with deep respect, avoiding “spray and pray” tactics to build long-term trust with reporters, influencers and analysts. That's requirements/qualifications/skills. About This Role (role description): "The Senior Account Executive is a key day-to-day client contact and seasoned executional hand on accounts (maximum of 6). You are in the business of providing long-term value to clients and executing bespoke, high-impact earned attention strategies aligned directly with their business outcomes. This is one of the heaviest media relations roles on the PR team with an expectation that you’ll be proactively developing hard-hitting story angles that regularly turn into results for clients. You’re growing your own industry reputation and Rolodex, and love meeting with journalists, influencers, and industry experts. You’ll operate with outcome-oriented autonomy, using AI tools to eliminate process bloat and low-value tasks so you can focus on high-impact strategic work. Previous experience in the tech (B2B or B2C) world is critical, as well as a deep understanding of the shifting earned media landscape and how to measure the value of a PR win in the context of a client’s business goals. You’ll thrive if you’re an energetic, nimble self-starter who pushes for continuous evolution, shoots their shot with bold creative ideas, and acts as a trusted advisor to clients and executives." What You’ll Be Doing (responsibilities): - Lead day-to-day program execution across up to 6 accounts, deploying tailored earned attention strategies alongside a dedicated resource from our Strategy team, day-to-day account leads and a S/VP. - Build enduring, first-name-basis relationships with journalists, creators, and analysts. - Craft tailored, high-value pitches (no "spray and pray") that turn complex tech into compelling stories. - Score earned attention for your clients across all media verticals and mediums. - Take ownership of clients’ speaking and awards programs, identifying best-fit opportunities, crafting submissions, and managing stage appearances. - Attend trade shows, conferences, and other events as a representative of Codeword. - Support with building industry-leading reports on PR program ROI with our Insights & Analytics team. - Leverage AI tools smartly and precisely to streamline workflow and automate administrative tasks, maintaining a high bar of human-in-the-loop quality. - Lead by example by securing impactful media wins and guiding junior talent on client-facing work and narrative building. - Support your account teams in building lasting relationships with clients. - Bring creative ideas to your clients outside of traditional PR, utilizing Codeword’s full service capabilities. Compensation: "The base annual salary range for this role, applicable across all U.S. locations, is outlined below. The actual salary may vary based on several factors such as business requirements, job responsibilities, skills, experience, and geographical location. Salary Range: $70,000 USD - $79,500 USD" Benefits list: - Flexible work hours - Minimum 20 days paid vacation annually - 401k + financial wellness support - Health Insurance (medical, dental, life, pet, mental health services) - Home office allowance - Bi-annual Wellness Credits - Monthly Technology Credit (to offset internet / phone costs) - Comprehensive Parental Leave Policy Culture paragraph (A Few More Things You Should Know About Codeword) we can keep as a
maybe after benefits. Now we need to decide sections. We have About the role: we could combine About This Role description. Could also include About Us? But About the role likely refers to role description. We'll put About This Role content under
About the role
. Responsibilities:Responsibilities
with- list.
Requirements: maybe from About You (experience, trendspotter, etc). We'll put under
Requirements
as- .
Qualifications: maybe overlapping; but we could split: Requirements = experience, Qualifications = skills/trendspotter etc. However we risk duplication. The instruction: prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one section? But we have to use headings only when posting has real specific content for it. We have content for both; we could make two sections but they'd be thin. Better to combine into one section maybe "Requirements and Qualifications". But allowed headings list includes Requirements and Qualifications separately. We could still use both but risk thin. The instruction: "Prefer a few substantive sections over many thin ones." So we should avoid creating many thin sections. So we could have one section "Requirements" that includes both experience and skills. Or we could have "Requirements" and "Skills". But Skills is also allowed heading. We could put skills under Skills heading. That would be three sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay. That's many but each may be substantive enough.
Let's see content:
Requirements (experience): 3+ years of experience in tech (B2B and/or consumer). Also previous experience in tech critical (mentioned in About This Role). Could combine.
Skills: creative thinking to storytelling, trendspotter, servicing broad range clients, high-context low-control ownership, media relationship respect, avoiding spray and pray, energetic nimble self-starter, pushes for continuous evolution, bold creative ideas, trusted advisor, etc. Also understanding of earned media landscape, measuring PR win value, using AI tools, etc.
We could split.
Benefits: list.
Pay: salary range.
We'll omit Schedule.
Now we need to ensure we don't include boilerplate like Equal Opportunity etc. We'll remove.
Now produce HTML.
Structure:
About Us paragraph
About the role
... role description ...
Responsibilities
- ... ...
Requirements
- 3+ years of experience in tech (B2B and/or consumer)
- Previous experience in the tech (B2B or B2C) world is critical
Skills
- Avid trendspotter with ear to the ground on latest media
- Creative thinking applied to storytelling
- Comfortable servicing a broad range of clients, from startups to large enterprises and publicly traded companies, matching tone to reinforce client confidence
- Thrives in high‑context, low‑control environment, taking ownership of deliverables (e.g., first‑drafts of pitches and story angles) without waiting for step‑by‑step direction
- Treats media relationships with deep respect, avoiding “spray and pray” tactics to build long‑term trust with reporters, influencers, and analysts
- Energetic, nimble self‑starter who pushes for continuous evolution and shoots their shot with bold creative ideas
- Acts as a trusted advisor to clients and executives
- Deep understanding of the shifting earned media landscape and how to measure the value of a PR win in the context of a client’s business goals
- Proficient leveraging AI tools to eliminate process bloat and focus on high‑impact strategic work
- .
Benefits
- Flexible work hours
- Minimum 20 days paid vacation annually
- 401k + financial wellness support
- Health Insurance
- .
Qualifications: maybe overlapping; but we could split: Requirements = experience, Qualifications = skills/trendspotter etc. However we risk duplication. The instruction: prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one section? But we have to use headings only when posting has real specific content for it. We have content for both; we could make two sections but they'd be thin. Better to combine into one section maybe "Requirements and Qualifications". But allowed headings list includes Requirements and Qualifications separately. We could still use both but risk thin. The instruction: "Prefer a few substantive sections over many thin ones." So we should avoid creating many thin sections. So we could have one section "Requirements" that includes both experience and skills. Or we could have "Requirements" and "Skills". But Skills is also allowed heading. We could put skills under Skills heading. That would be three sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay. That's many but each may be substantive enough.
Let's see content:
Requirements (experience): 3+ years of experience in tech (B2B and/or consumer). Also previous experience in tech critical (mentioned in About This Role). Could combine.
Skills: creative thinking to storytelling, trendspotter, servicing broad range clients, high-context low-control ownership, media relationship respect, avoiding spray and pray, energetic nimble self-starter, pushes for continuous evolution, bold creative ideas, trusted advisor, etc. Also understanding of earned media landscape, measuring PR win value, using AI tools, etc.
We could split.
Benefits: list.
Pay: salary range.
We'll omit Schedule.
Now we need to ensure we don't include boilerplate like Equal Opportunity etc. We'll remove.
Now produce HTML.
Structure: