Senior Communications & PR Manager

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must not repeat job title. Must not include Job ID etc. Remove boilerplate. We need to parse the job description. Content: Intro paragraph: "We’re making security suck less for developers..." up to "Join an all-star team. Take real ownership. Push boundaries. Build things that matter." That's about the role/company. Could be "About the role" or maybe "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put an

About the role

with that intro paragraph. Then "We’re hiring our first dedicated in-house Senior Communications & PR Manager to help shape, build, and execute on Aikido’s communications strategy; growing Aikido’s presence among developers, security teams, and top-tier media. We’re looking for someone who understands how the media works, has strong relationships with journalists, and knows how to turn product updates, research, and industry insight into stories people actually want to cover." This could be part of About the role or maybe Responsibilities. But we have a separate Responsibilities section later. Responsibilities bullet list: - Independently identify industry news and trends where Aikido’s perspective is relevant, and work with internal experts to develop timely commentary - Turn product launches, research, and marketing initiatives into PR opportunities - Work closely with product, marketing, and content to maintain a clear and consistent narrative - Build relationships with analysts, creators, influencers, podcasts, and other voices in the developer and security ecosystem - Partner with the events team to build in-person relationships with media - Track and report on the performance of communications and PR activity Job Requirements bullet list: - 5+ years of experience in PR, communications, or journalism - Strong network of media contacts across relevant trade and top-tier publications - Ability to understand complex products and translate them into clear stories for the media - Comfortable working independently and taking initiative - Background in journalism or strong writing skills Nice to have bullet list: - Experience working with developers or cybersecurity audiences - Experience working in a fast-paced startup environment - Experience working with industry analysts What you can expect bullet list: - Short decision lines. Big ownership. Shape the projects that matter and ship fast. - Grow as fast as we do. Take on more, own more, and carve out your own path. - Top-tier tech pay and equity. - High trust, strong values, zero corporate BS. - Flexibility in working hours. - A company that sticks to its values in an open and informal atmosphere. - We hire for talent, drive, and potential. Everything else is noise. We need to map these to sections: Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Requirements (the "Job Requirements") – that's clear. We have Nice to have – could be Qualifications or Skills. Usually "Nice to have" could be Skills or Qualifications. We'll decide: maybe put under Skills. We have "What you can expect" – includes benefits like Top-tier tech pay and equity, Flexibility in working hours, etc. That could be Benefits and Pay. Pay: "Top-tier tech pay and equity." That's pay info. Benefits: other items like flexibility, high trust, etc. Schedule: maybe "Flexibility in working hours" could be schedule. But we should only create sections if there is real specific content. We have pay info: "Top-tier tech pay and equity." That's specific enough for Pay section. Benefits: we have multiple items: Short decision lines, big ownership, etc. Those are more cultural expectations; but they could be Benefits. However the instruction says: Prefer a few substantive sections over many thin ones. So maybe combine Benefits and Pay into one Benefits section? But we have separate headings allowed. We need to decide. We have schedule info: "Flexibility in working hours." That's schedule. Could be Schedule section. We have also "Short decision lines. Big ownership..." etc. That's more about culture/ownership, maybe not benefits. Could be omitted? But we must preserve ALL substantive information; we cannot drop it. So we need to include it somewhere. Could be under Benefits (as cultural benefits) or under a separate section like "What you can expect". But we only allowed headings list; we could create a Benefits section and put all those items there, including pay and schedule? But then we would have duplicate headings? Better to follow the allowed headings: Benefits, Pay, Schedule. We'll allocate: - Benefits: items like Short decision lines, Big ownership, Grow as fast as we do, Take on more, own more, carve out your own path, High trust, strong values, zero corporate BS, A company that sticks to its values in an open and informal atmosphere, We hire for talent, drive, and potential. Everything else is noise. - Pay: Top-tier tech pay and equity. - Schedule: Flexibility in working hours. But note that "Short decision lines. Big ownership..." is more about work style; still could be considered benefit. We'll include. Now we also have "About the role" intro. We also have maybe "Qualifications" section? Could we put Nice to have under Qualifications? Or Skills? The instruction says we can use Qualifications, Skills. We have Nice to have items: Experience working with developers or cybersecurity audiences, Experience working in a fast-paced startup environment, Experience working with industry analysts. Those could be Skills. Or Qualifications. Let's put them under Skills. We have Requirements already. We might also have a Qualifications section for education? Not present. So we skip Qualifications if no content. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. We must not emit empty sections. Now format: Use

for each section heading. Then content: For prose, use

. For lists, use

• . We need to preserve all substantive information. Ensure we don't lose any bullet. Let's craft. About the role: combine the introductory paragraphs before Responsibilities. The text: "We’re making security suck less for developers. Security tools haven’t kept up with how software is built today. They interrupt teams, slow releases, and turn security into a bottleneck instead of a capability. We built Aikido to change that. Aikido builds developer-first security products that reduce real risk without getting in the way of shipping software. We focus on what actually matters and automate the rest. We’re taking on legacy security tools teams have been stuck with, and we’re winning. If you want to help us take market share and build products developers actually enjoy using, you’re in the right place. Founded in 2022 by third-time founders, Aikido has $85M in the bank, a long runway ahead, and unicorn status. We’re building toward self-securing software. Join an all-star team. Take real ownership. Push boundaries. Build things that matter. We’re hiring our first dedicated in-house Senior Communications & PR Manager to help shape, build, and execute on Aikido’s communications strategy; growing Aikido’s presence among developers, security teams, and top-tier media. We’re looking for someone who understands how the media works, has strong relationships with journalists, and knows how to turn product updates, research, and industry insight into stories people actually want to cover." We'll put that as

  maybe multiple paragraphs? Could be one

  with line breaks? We'll keep as one

  . Now Responsibilities: list as

  • each bullet. Requirements: list. Skills: list of nice to have. Benefits: list of what you can expect items except pay and schedule? We'll separate pay and schedule. But we need to ensure we don't duplicate. Let's extract "What you can expect" bullets: - Short decision lines. Big ownership. Shape the projects that matter and ship fast. - Grow as fast as we do. Take on more, own more, and carve out your own path. - Top-tier tech pay and equity. - High trust, strong values, zero corporate BS. - Flexibility in working hours. - A company that sticks to its values in an open and informal atmosphere. - We hire for talent, drive, and potential. Everything else is noise. We will assign: Pay: "Top-tier tech pay and equity." Schedule: "Flexibility in working hours." Benefits: the rest: - Short decision lines. Big ownership. Shape the projects that matter and ship fast. - Grow as fast as we do. Take on more, own more, and carve out your own path. - High trust, strong values, zero corporate BS. - A company that sticks to its values in an open and informal atmosphere. - We hire for talent, drive, and potential. Everything else is noise. Now we need to ensure we didn't miss any other info like "Founded in 2022..." etc already in About the role. Now output HTML. We'll produce:

    About the role

    ...

    Responsibilities

    • ...
    ...

    Requirements

    ...

    Skills

    ...

    Benefits

    ...

    Pay

    Top-tier tech pay and equity.

    Schedule

    Flexibility in working hours.

    Check that we didn't include any boilerplate like cookie/navigation etc. Good. Now ensure we didn't repeat job title. Not present. Now output only HTML fragment. Let's craft the About the role paragraph exactly as given, preserving punctuation. We'll copy the text: We’re making security suck less for developers. Security tools haven’t kept up with how software is built today. They interrupt teams, slow releases, and turn security into a bottleneck instead of a capability. We built Aikido to change that. Aikido builds developer-first security products that reduce real risk without getting in the way of shipping software. We focus on what actually matters and automate the rest. We’re taking on legacy security tools teams have been stuck with, and we’re winning. If you want to help us take market share and build products developers actually enjoy using, you’re in the right place. Founded in 2022 by third-time founders, Aikido has $85M in the bank, a long runway ahead, and unicorn status. We’re building toward self-securing software. Join an all-star team. Take real ownership. Push boundaries. Build things that matter. We’re hiring our first dedicated in-house Senior Communications & PR Manager to help shape, build, and execute on Aikido’s communications strategy; growing Aikido’s presence among developers, security teams, and top-tier media. We’re looking for someone who understands how the media works, has strong relationships with journalists, and knows how to turn product updates, research, and industry insight into stories people actually want to cover. Now Responsibilities bullets: - Independently identify industry news and trends where Aikido’s perspective is relevant, and work with internal experts to develop timely commentary - Turn product launches, research, and marketing initiatives into PR opportunities - Work closely with product, marketing, and content to maintain a clear and consistent narrative - Build relationships with analysts, creators, influencers, podcasts, and other voices in the developer and security ecosystem - Partner with the events team to build in-person relationships with media - Track and report on the performance of communications and PR activity Requirements bullets: - 5+ years of experience in PR, communications, or journalism - Strong network of media contacts across relevant trade and top-tier publications - Ability to understand complex products and translate them into clear stories for the media - Comfortable working independently and taking initiative - Background in journalism or strong writing skills Skills bullets (nice to have): - Experience working with