Manager, Social Media & Strategic Communications

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Castelion" then role description. We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we must only include sections when posting has real specific content. We have content about responsibilities (What You'll Do). Requirements/Qualifications (What We're Looking For, Nice to Have). Benefits: mention long-term stock incentives, comprehensive medical/vision/dental, four weeks PTO. Pay: not mentioned. Schedule: mentions full-time, on-site, travel 50%, extended hours. So we can include Schedule section with that info. Benefits section with those details. Pay: not mentioned, so omit. Skills: maybe we can extract from requirements? But we have separate sections: Requirements, Qualifications, Skills. The posting lumps experience and skills together. We could put Requirements as experience, Qualifications as education? Not given. Better to follow instruction: Use headings only when posting has real specific content. We have content for Responsibilities, Requirements (experience), Qualifications maybe not separate; Skills maybe not separate; Benefits yes; Schedule yes. Could combine Requirements and Qualifications into one? But instruction says prefer few substantive sections over many thin ones. Could make sections: Responsibilities, Requirements, Benefits, Schedule. Omit About the role? The page already shows job title, but we could still have About the role? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we could include About the role if we have content. The posting includes an introductory paragraph about Castelion and role summary. That could be About the role. So we can include About the role section with the introductory paragraphs (About Castelion, role summary). Then Responsibilities (What You'll Do). Then Requirements (What We're Looking For + Nice to Have maybe). Then Benefits (stock incentives, medical, PTO). Then Schedule (full-time, on-site, travel 50%, extended hours). No Pay. No Qualifications/Skills separate. We must not repeat job title as heading. Not include Job ID etc. Remove boilerplate: EEO, legal, etc. We have some EEO statement at end; we should remove. Also ITAR requirements is substantive? It's a requirement for eligibility; could be part of Requirements. It's about citizenship. We'll include that in Requirements. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like "4-7 years of experience", "Demonstrated experience managing brand, founder, executive, or organizational social channels, especially LinkedIn and X." etc. Also "Nice to Have" list. We need to format using

• for any list of duties/requirements/benefits. For prose use

  . So we need to decide what is list vs prose. The responsibilities are a list of bullet-like sentences; we can make each as

• . Similarly requirements and nice to have can be lists. Benefits list. We need to ensure we don't lose any detail. Let's extract sections. About Castelion/intro: "About Castelion Castelion is bringing a new approach to defense development and production: short, iterative design cycles, rapid testing, and modern commercial manufacturing strategies built for scale. We're designing, building, and testing next generation long range strike weapons systems to give America and its Allies a definitive edge and deter future conflicts. The brand studio you will help build is how the world comes to understand that mission. Manager, Social Media & Strategic Communications Castelion is building next-generation strike systems to restore credible deterrence and expand the industrial base for national security. We are looking for a Manager, Social Media & Strategic Communications to lead Castelion's presence across social and owned channels while supporting broader media, executive communications, and strategic storytelling. This role is responsible for turning Castelion's mission, technology, milestones, leadership perspective, and culture into clear, credible, high-impact content for defense, aerospace, policy, technology, investor, and talent audiences. The right candidate understands how to build momentum on LinkedIn, X, YouTube, and emerging platforms while maintaining the judgment required to communicate in a national-security environment. You will work closely with company leadership, engineering, business development, recruiting, legal, security, and communications to shape social-first narratives around hypersonic systems, advanced effects, missile defense, defense manufacturing, and emerging national-security technologies. This is a hands-on role for a sharp writer, fast operator, and high-judgment communicator who can move from strategy to execution quickly." We can keep that as prose paragraphs. Responsibilities (What You'll Do) list: - Develop and execute Castelion's social media and owned-channel strategy across social channels, including X, LinkedIn, YouTube, and other priority platforms. - Own the editorial calendar for company channels, including announcements, milestones, recruiting content, executive perspective, industry commentary, event coverage, and evergreen brand storytelling. - Draft, edit, schedule, and publish social content that is technically accurate, visually compelling, and appropriate for defense, policy, customer, investor, and talent audiences. - Build social-first campaigns around major company announcements, product milestones, test activity, launch activity, executive appearances, industry events, and recruiting priorities. - Partner with creative, design, video, engineering, and recruiting teams to develop visual assets, short-form video concepts, carousels, explainers, and behind-the-scenes content. - Support executive social presence, including drafting posts, shaping point of view, identifying timely moments, and translating leadership perspective into credible public commentary. - Monitor defense, aerospace, technology, policy, competitor, and geopolitical conversations to identify relevant moments for Castelion to engage or avoid. - Produce a concise daily executive media and social brief summarizing relevant coverage, industry developments, competitor activity, social conversation, geopolitical events, and emerging narratives. - Track channel performance, audience growth, engagement, sentiment, and campaign results, then use those insights to improve content strategy. - Manage community engagement, comment monitoring, inbound message routing, and escalation workflows. - Support media strategy for announcements and high-visibility moments, including drafting press materials, talking points, briefing notes, media pitches, and social amplification plans. - Help identify high-quality podcasts, interviews, conferences, speaking opportunities, and other visibility moments for company leadership. - Support rapid-response communications and issue management with discretion, accuracy, and sound judgment. - Maintain consistency of Castelion's external voice, messaging, terminology, and narrative across social, press, web, recruiting, and executive channels. - Coordinate with legal, security, engineering, and business stakeholders to ensure communications meet OPSEC, export-control, customer-sensitivity, and technical-accuracy standards. Requirements (What We're Looking For) list: - 4-7 years of experience in social media, strategic communications, public affairs, journalism, defense communications, technology communications, or a related field. - Demonstrated experience managing brand, founder, executive, or organizational social channels, especially LinkedIn and X. - Exceptional writing and editing skills, with the ability to craft concise, compelling content under tight deadlines. - Strong understanding of social media strategy, content calendars, audience development, platform best practices, social listening, and performance analytics. - Ability to translate technical or complex subject matter into clear, accurate, engaging messaging. - Strong judgment, discretion, and calm under pressure, especially in sensitive or high-visibility communications environments. - Ability to work directly with senior executives, engineers, military leaders, reporters, policymakers, and external partners with professionalism and confidence. - Strong organizational skills and ability to manage multiple fast-moving priorities simultaneously. - Interest in U.S. national security, defense innovation, aerospace, manufacturing, and emerging technologies. - Willingness to travel as needed for events, media opportunities, launches, tests, and industry conferences. - ITAR Requirements: To conform to U.S. Government export regulations, applicant must be a (i) U.S. citizen or national, (ii) U.S. lawful, permanent resident (aka green card holder), (iii) Refugee under 8 U.S.C.1157, or (iv) Asylee under 8 U.S.C.1158, or be eligible to obtain the required authorizations from the U.S. Department of State. Nice to Have list: - Experience in defense, aerospace, government, Capitol Hill, journalism, public affairs, venture-backed technology, or dual-use technology. - Experience building or managing executive social media programs. - Experience using social listening, analytics, scheduling, or reporting tools. - Experience supporting product launches, test campaigns, major announcements, conferences, or recruiting campaigns. - Familiarity with defense acquisition, Pentagon structure, national-security policy, venture-backed technology environments, or dual-use technology sectors. - Relationships with defense, aerospace, technology, policy, business, podcast, or creator-media communities. - Experience with crisis communications, rapid response, or sensitive issue management. - Comfort working with creative teams on photography, video, motion graphics, and visual storytelling. - Familiarity with OPSEC, export-control considerations, classification boundaries, or communications review processes in defense or aerospace environments. Benefits: - All employees are granted long-term stock incentives as part of their employment as Castelion. - All employees receive access to comprehensive medical, vision, and dental insurance. - The company offers four weeks of paid time off per year. Schedule: - This is a full-time, on-site role based at our Torrance or Washington, DC facility. - Some of the most important production moments, including field shoots at test and manufacturing sites, happen in dynamic and physically demanding environments. - You should be comfortable working extended hours when production demands it. - You should expect to travel approximately 50 percent of the time. We must not include Pay section. Now produce HTML fragment with

  headings and

  for prose sections (About the role maybe prose). For lists use

  • . We need to ensure we don't include any markdown fences. Just raw HTML. Let's craft. We'll start with

    About the role

    then

    ... maybe split into two paragraphs: first about Castelion, second about role. Could combine but okay. Then

    Responsibilities

    with each responsibility as
    • . Then

      Requirements

      with each requirement. Then

      Nice to Have

      maybe but instruction only lists certain headings; Nice to Have not in list. Could we omit? It's substantive but not a prescribed heading. Could we incorporate Nice to Have into Requirements? Might be better to keep as Requirements and include nice to have as part of Requirements? But we already have Requirements section; we could add a subheading? Not allowed. Perhaps we can treat Nice to Have as part of Requirements (since they are still requirements/qualifications). But we risk losing detail if we just merge; but we can keep them as separate list items under Requirements, labeling them as "Nice to have:"? Might be okay. Alternatively we could create a section "Qualifications" and put both Requirements and Nice to Have there. But Qualifications is in allowed headings. We could put Requirements under Qualifications? Hmm. The instruction: "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not strict list; we can use those headings. It says "include a section ONLY when the posting has real, specific content for it". So we can choose which headings to use. We have content for Responsibilities, Requirements (experience), Qualifications (maybe education? none), Skills (maybe we could treat the skill bullets as Skills), Benefits, Schedule. We could map: - About the role: intro. - Responsibilities: What You'll Do. - Requirements: What We're Looking For (experience). - Skills: Ability to translate technical, writing, judgment, etc. Could be separate. - Benefits: stock, medical, PTO. - Schedule: full-time, on-site, travel,