VP, International Communications

We need to output HTML fragment with sections: headings

for each section present. Need to extract content: About the role? Actually the posting includes "Who We Are", "What We Do", "The Opportunity", "To be Successful in this role", "You ideally have:", "Bonus points:". We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections correspond. We have description of role: responsibilities likely under "To be Successful in this role" bullet list. Also "What We Do" maybe about the team? Could be "About the role"? Actually "Who We Are" is about organization, not role. Could be omitted? The instruction: do NOT repeat job title as heading; we can include sections only if posting has real specific content. We can include "About the role" maybe summarizing the opportunity? But we must not invent placeholder. We have content: "The Opportunity" describing role. That could be "About the role". Also "To be Successful in this role" is responsibilities. "You ideally have:" is qualifications/requirements. "Bonus points:" could be additional qualifications or skills. We must not include sections like Benefits, Pay, Schedule if not present. There's no mention of benefits, pay, schedule. So omit those. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve all substantive information, not invent or summarize away detail. So we need to keep the bullet points exactly as given? We can keep them as list items. We need to remove boilerplate: cookie/navigation/legal/EEO etc. Not present. We need to output only HTML fragment. Let's structure:

  About the role

  The Opportunity ...

  maybe include the paragraph describing opportunity. Then responsibilities:

  Responsibilities

  • Define and maintain a global narrative...
  etc. Then qualifications:

  Qualifications

  • Roughly 10 to 15 years in communications...
  etc. Then skills? Could be "Bonus points:" as

  Additional Qualifications

  but allowed headings list includes Skills. We could use Skills for bonus points. Or we could treat bonus points as Skills. Use

  Skills

  for bonus points. We must not create headings with filler. Ensure each heading has content. Let's extract exact text. From posting: "The Opportunity The people forming a view of Solana now include payments executives, asset managers, central bank staff, congressional offices and consumer press - audiences with no patience for jargon and a long memory for the network's early reliability problems. At the same time, the original audience of developers, validators and the extremely online will punish anything that reads as corporate. Holding both at once is the craft this role is hired for. We are looking for a VP, Communications to own the global narrative and the reputation of the network end to end. You will set the handful of things Solana should be understood for, build the tier-one relationships that carry them, and own incidents and issues responses when the news cycle turns. This is a hands-on role with a function to build behind it: you will write the statement, make the call, and design the system that lets a small team operate at the scale of a much larger one. One thing to be clear about before you apply. The Foundation does not own the Solana network. We cannot direct the validator operators, the client engineering teams, the infrastructure providers or the loudest voices in the ecosystem, and we cannot issue a statement on anyone's behalf. The work is not message control. It is building the conditions in which an accurate story travels faster than an inaccurate one and enough trust across the ecosystem that independent parties choose to coordinate with you in the first hour of a bad day rather than the fourth." That's the opportunity paragraph. Responsibilities bullet list under "To be Successful in this role You will:" then list: - Define and maintain a global narrative for Solana built around a handful of defensible claims, with the discipline to eliminate competing messages that dilute the story. - Build and personally maintain tier-one media relationships across U.S. business, financial, technology, and crypto-native press. - Own reputation and issues management across network incidents, client bugs, application-layer exploits, validator disputes, and other high-stakes moments, establishing severity tiers, named decision-makers, rehearsed processes, and pre-drafted response language. - Provide executive positioning and communications counsel to Foundation leadership, including candid pushback when needed. - Build a bench of credible external technical voices who can independently explain and advocate for Solana, recognizing that the most persuasive validation often comes from outside the Foundation. - Provide communications support to ecosystem teams, including launch support, founder media training, and shared narrative infrastructure that smaller companies could not build independently. - Translate protocol and governance changes for a wide range of audiences, from stake-weighted voters and technical participants to readers with no prior understanding of validators or blockchain infrastructure. - Coordinate with Policy and Legal on regulatory and legislative moments, including work alongside the Solana Policy Institute. - Develop a measurement framework focused on narrative accuracy and reputation outcomes, including how accurately Solana is described in independently generated coverage and how quickly misinformation is corrected—not simply clip counts. Then "You ideally have:" bullet list: - Roughly 10 to 15 years in communications, with meaningful time in a high-scrutiny environment: a regulated industry, a platform under sustained press attention, a political or advocacy context, or a company that had a genuinely bad year and came through it - Personal experience running a situation where the facts were unclear, the clock was running, and the wrong sentence would have made it worse - Direct relationships with tier-one business, financial and technology journalists, and a view on which four are worth real investment - The ability to hold a technical conversation with engineers and come out with something true, accurate and repeatable by someone who does not understand it - Experience earning coverage on a hard story with no news hook, using patience and proof rather than access - A track record of operating with influence rather than authority: coalitions, consortia, federated organizations or open-source projects - Comfort as a hands-on practitioner who would rather draft the statement than brief someone else to draft it - Composure on the worst day, which is the single most predictive trait in this role - Fluency with AI tooling as part of your working practice — for monitoring, research, drafting, message testing and adversarial review Then "Bonus points:" bullet list: - Experience communicating a decentralized or multi-stakeholder system you did not control - You have told a principal no, given your reasoning, and kept the relationship - Experience building a comms function rather than inheriting one - You have opinions about what makes crypto communications mostly bad, and a view on how to do it better We need to preserve all substantive information. So include these bullet points exactly. We need to wrap each bullet in
  • . Use
    • ... etc. We need to ensure no extra headings like About the role if we don't have content? We have opportunity paragraph, we can put under About the role. We also have "Who We Are" and "What We Do" which are about organization; maybe we could include as "About the role"? But that's not exactly role. However we could include a section "About the organization" but not allowed heading. Allowed headings list does not include About the organization. So we might omit those paragraphs because they are not role-specific? The instruction: "include a section ONLY when the posting has real, specific content for it". The allowed headings are limited; we can only use those headings. If we have content that doesn't fit any allowed heading, we might need to omit it? But we must preserve ALL substantive information. However we cannot invent headings not allowed. Perhaps we can incorporate "Who We Are" and "What We Do" into a

      under About the role? But that would be mixing organization info with role. The instruction says "do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid adding other content under a heading. So we could put the organization description under About the role as introductory paragraph. That seems acceptable. Thus About the role section will contain: combine "Who We Are", "What We Do", and "The Opportunity". That's a lot of prose; we can put as

      maybe multiple paragraphs. We must not invent placeholder. So we will include all that text. Let's craft HTML:

      About the role

      The Solana Foundation is a non-profit based in Zug, Switzerland, dedicated to the adoption, decentralization, and security of the Solana network. Solana is a high performance blockchain that can deliver a fast and friendly user experience, without sacrificing security. The Solana Foundation is working to realize a world where individuals own their data, use permissionless networks, and transfer information and value freely around the world. We are looking for talented people who are willing to jump right in and use their expertise to help the ecosystem build.

      The Solana Foundation's marketing and communications team tells the story of what is being built on Solana. We work across developers and founders, traders and crypto-native users, institutions and capital-market participants, payments companies and merchants, enterprises and consumer platforms, and the policymakers and media who shape how all of it is understood. We are deliberately lean, fast, and close to the work.

      The people forming a view of Solana now include payments executives, asset managers, central bank staff, congressional offices and consumer press - audiences with no patience for jargon and a long memory for the network's early reliability problems. At the same time, the original audience of developers, validators and the extremely online will punish anything that reads as corporate. Holding both at once is the craft this role is hired for. We are looking for a VP, Communications to own the global narrative and the reputation of the network end to end. You will set the handful of things Solana should be understood for, build the tier-one relationships that carry them, and own incidents and issues responses when the news cycle turns. This is a hands-on role with a function to build behind it: you will write the statement, make the call, and design the system that lets a small team operate at the scale of a much larger one. One thing to be clear about before you apply. The Foundation does not own the Solana network. We cannot direct the validator operators, the client engineering teams, the infrastructure providers or the loudest voices in the ecosystem, and we cannot issue a statement on anyone's behalf. The work is not message control. It is building the conditions in which an accurate story travels faster than an inaccurate one and enough trust across the ecosystem that independent parties choose to coordinate with you in the first hour of a bad day rather than the fourth.

      Then responsibilities:

      Responsibilities

      • Define and maintain a global narrative for Solana built around a handful of defensible claims, with the discipline to eliminate competing messages that dilute the story.
      • Build and personally maintain tier-one media relationships across U.S. business, financial, technology, and crypto-native press.
      • Own reputation and issues management across network incidents, client bugs, application-layer exploits, validator disputes, and other high-stakes moments, establishing severity tiers, named decision-makers, rehearsed processes, and pre-drafted response language.
      • Provide executive positioning and communications counsel to Foundation leadership, including candid pushback when needed.
      • Build a bench of credible external technical voices who can independently explain and advocate for Solana, recognizing that the most persuasive validation often comes from outside the Foundation.
      • Provide communications support to ecosystem teams, including launch support, founder media training, and shared narrative infrastructure that smaller companies could not build independently.
      • Translate protocol and governance changes for a wide range of audiences, from stake-weighted voters and technical participants to readers with no prior understanding of validators or blockchain infrastructure.
      • Coordinate with Policy and Legal on regulatory and