Senior Strategist or Design Strategist; Program Manager
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to parse the posting.
Key sections:
- Who We Are: description of LINK. Could be "About the company" but not required heading? The instructions say use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include "About the role" maybe for description of opportunity. "Who We Are" could be considered "About the company" but not in list; but we can still include as a section heading? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. Probably we should stick to those headings if content matches. "Who We Are" could be considered "About the role"? Not exactly. Might be better to include a heading "About the company" but not in list; but they said use for section headings (e.g. About the role, Responsibilities...). It might be okay to use other headings as long as they are . However they said "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This implies those are the expected sections. We can include "About the role" for the opportunity description. "Who We Are" maybe could be omitted or placed under a short paragraph before sections. But we need to preserve ALL substantive information. So we need to include that info somewhere. Could put it in a
before any headings, as introductory text. That's allowed.
Then "Location: We are actively hiring in the Charleston, SC area." That's location metadata; could be a short
.
Then "About The Opportunity" paragraph describing role. That fits "About the role" heading.
Then "Qualifications" list: bullet points (though they are semicolon separated). We'll need to convert to
- . Also there is a line "Bachelor’s degree in Journalism, Communication, English, Business, or a related field10+ years of experience..." Actually it's weird formatting: "Bachelor’s degree in Journalism, Communication, English, Business, or a related field10+ years of experience in strategic communication, public affairs, program management, or strategy development7+ years program/project management experience including familiarity with Agile methodologies and project delivery best practicesCurrent TS/SCI clearance level required.Excellent organizational skills..." It seems missing punctuation. We need to parse each qualification. Likely each sentence separated by a period? Actually there is no period after field. Let's try to split:
- Bachelor’s degree in Journalism, Communication, English, Business, or a related field
- 10+ years of experience in strategic communication, public affairs, program management, or strategy development
- 7+ years program/project management experience including familiarity with Agile methodologies and project delivery best practices
- Current TS/SCI clearance level required.
- Excellent organizational skills with the ability to manage multiple projects simultaneously, maintaining a strong focus on accuracy and attention to detail
- Exceptional written and verbal communication skills, with the ability to communicate in a clear, approachable, and knowledgeable manner
- Government contracting experience
- PMP certification preferred
- Security clearance as required by contracts
- Experience with human-centered design and design thinking principles
- Demonstrated ability to manage multiple complex projects simultaneously
We'll treat each as
- .
Then "Responsibilities" section with many bullet-like sentences under headings: "Senior Strategist/Design Strategist responsibilities include:" then subheadings like "Client Partnership & Design Strategy Leadership", "Content Strategy, Storytelling & Execution", etc. Each subheading has multiple sentences. We could treat each subheading as a heading? But instruction says use
for section headings (e.g. About the role, Responsibilities...). So we likely should have a single Responsibilities
and then under it we can have - for each duty. However the responsibilities are grouped under subheadings; we could either keep subheadings as
but not allowed? They didn't forbid other headings, but they said use for section headings (e.g...). Might be okay to use for subheadings, but safer to keep everything under - and maybe include the subheading text as part of the
- content. However we need to preserve ALL substantive information; we can include the subheading as bold text inside
- but we cannot use markdown; we can use . That's allowed as HTML. So we can do
- Client Partnership & Design Strategy Leadership: ...
. That preserves.
Similarly for Program Manager Responsibilities Include: we could treat as part of Responsibilities as well, maybe separate subheading.
Thus we will have a single Responsibilities section with many - items, each possibly containing a subheading.
Then "Work Schedule" paragraph: "Hybrid onsite presence 3-5 days per week may be required for client meetings, presentations, or working sessions.Full time, 40 hours per weekSome travel required to attend relevant events and conferences, and participate in LINK team events". That's schedule info. So we should have a
Schedule
with containing that.
Then "Salary: We're committed to offering competitive compensation. While the salary range for this position is $112,000-$151,000, your final offer may be adjusted based on factors like experience and location." That's pay info. So
Pay
with .
Then Benefits: list of benefits. So
Benefits
with - .
We also need to include location maybe as a short
before sections.
We must not include EEO boilerplate etc. Remove that at end.
Also remove duplicated lines, application instructions.
Now construct HTML.
Start with maybe an introductory
for Who We Are and Location.
Let's draft:
LINK is a fast-growing Woman Owned Small Business (WOSB) that leverages human-centered design to support strategy, innovation, communication, change, and branding within the federal government and adjacent industry partners. At LINK, we partner with engineers, futurists, and thought leaders to untangle complexity, discover opportunity, and communicate clearly with visual stories. Let us be your partners in change.
Location: We are actively hiring in the Charleston, SC area.
Then About the role
with paragraph about opportunity.
LINK is actively seeking a Senior Design Strategist or Strategist; Program Manager to join our dynamic team, where we leverage strong partnerships and a robust portfolio of clients across diverse industries. You will be responsible for leading and executing innovative design strategies, collaborating with both internal teams and executive-level clients, and driving impactful visual storytelling to meet client objectives. This is an exciting opportunity for an experienced professional to bring a combination of creative and strategic expertise to elevate LINK’s business growth and deliver high-quality, human-centered design solutions. You will work closely with clients to understand their challenges, develop compelling narratives, and implement design strategies that align with their mission, goals, and brand identity. Ideal candidates will have a proven track record of designing impactful visual experiences, utilizing data-driven insights, and collaborating cross-functionally to deliver exceptional client results.
Then Qualifications
with - each qualification.
Then
Responsibilities
with - each duty.
We need to extract responsibilities from the text.
Let's list them:
Under Senior Strategist/Design Strategist responsibilities include:
- Client Partnership & Design Strategy Leadership
* Serves as a trusted advisor to clients by framing complex challenges, identifying opportunities, and applying human-centered design approaches to inform strategic decision-making.
* Partners directly with client stakeholders to understand organizational priorities, user needs, operational constraints, and desired outcomes.
* Leads the development of design strategy approaches that align stakeholder needs, business objectives, and mission requirements.
* Guides cross-functional teams through ambiguity, helping stakeholders build alignment and make informed decisions.
* Identifies opportunities to create tangible business value and support long-term client success.
* Provides guidance that helps clients make informed decisions and navigate organizational complexity.
- Content Strategy, Storytelling & Execution
* Translates complex ideas into compelling strategic narratives, executive-level presentations, communication strategies, and decision-support products.
* Develops messaging frameworks that align leadership vision, organizational priorities, and stakeholder needs.
* Define content structures, information hierarchies, and storytelling approaches that communicate complex concepts clearly and effectively.
* Collaborates with creative teams to develop high-quality visual products that support strategic objectives and audience understanding.
* Establishes quality standards for strategic deliverables and provides guidance to team members to ensure consistency and excellence.
* Leads development of executive-ready materials that support decision-making, alignment, and organizational action.
- Change Management & Organizational Transformation
* Develops and implements change management strategies, including stakeholder engagement plans, communications strategies, change impact assessments, and adoption roadmaps.
* Designs governance frameworks, operating models, and implementation approaches that support successful transformation efforts.
* Facilitates cross-functional working sessions that drive alignment, accelerate decision-making, and address organizational resistance.
* Establishes feedback mechanisms and performance measures that support continuous improvement and long-term success.
* Monitors progress, evaluates outcomes, and refines approaches based on stakeholder feedback and organizational needs.
- Research, Insight Development & Systems Thinking
* Leads mixed-method research efforts, including stakeholder interviews, contextual inquiry, observations, journey mapping, ecosystem analysis, and systems mapping activities.
* Synthesizes qualitative and quantitative findings into actionable insights, opportunity areas, strategic recommendations, and design directions.
* Applies systems thinking to identify patterns, dependencies, root causes, and opportunities across complex organizational environments.
* Translates technical, operational, and policy-focused challenges into human-centered insights and strategic considerations.
* Guides research activities that inform organizational transformation, service design, experience design, and strategic planning efforts.
- Workshop Facilitation & Stakeholder Alignment
* Designs and facilitates workshops, design sprints, stakeholder engagements, and co-creation activities that advance strategic objectives and drive organizational alignment.
* Develops facilitation approaches, agendas, exercises, and collaborative experiences that enable productive dialogue and structured problem-solving.
* Synthesizes workshop outputs into actionable findings, recommendations, and implementation considerations.
* Helps stakeholders navigate competing priorities, organizational complexity, and change initiatives through structured facilitation and engagement.
* Guides teams in applying human-centered design methods throughout project lifecycles.
- Team Development & Leadership
* Mentors teammates through coaching, knowledge sharing, and constructive feedback.
* Models LINK values and contributes to a collaborative,
for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting. Key sections: - Who We Are: description of LINK. Could be "About the company" but not required heading? The instructions say use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include "About the role" maybe for description of opportunity. "Who We Are" could be considered "About the company" but not in list; but we can still include as a section heading? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. Probably we should stick to those headings if content matches. "Who We Are" could be considered "About the role"? Not exactly. Might be better to include a heading "About the company" but not in list; but they said use for section headings (e.g. About the role, Responsibilities...). It might be okay to use other headings as long as they are . However they said "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This implies those are the expected sections. We can include "About the role" for the opportunity description. "Who We Are" maybe could be omitted or placed under a short paragraph before sections. But we need to preserve ALL substantive information. So we need to include that info somewhere. Could put it in a
for section headings (e.g. About the role, Responsibilities...). It might be okay to use other headings as long as they are . However they said "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This implies those are the expected sections. We can include "About the role" for the opportunity description. "Who We Are" maybe could be omitted or placed under a short paragraph before sections. But we need to preserve ALL substantive information. So we need to include that info somewhere. Could put it in a
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This implies those are the expected sections. We can include "About the role" for the opportunity description. "Who We Are" maybe could be omitted or placed under a short paragraph before sections. But we need to preserve ALL substantive information. So we need to include that info somewhere. Could put it in a
before any headings, as introductory text. That's allowed. Then "Location: We are actively hiring in the Charleston, SC area." That's location metadata; could be a short
. Then "About The Opportunity" paragraph describing role. That fits "About the role" heading. Then "Qualifications" list: bullet points (though they are semicolon separated). We'll need to convert to
- . Also there is a line "Bachelor’s degree in Journalism, Communication, English, Business, or a related field10+ years of experience..." Actually it's weird formatting: "Bachelor’s degree in Journalism, Communication, English, Business, or a related field10+ years of experience in strategic communication, public affairs, program management, or strategy development7+ years program/project management experience including familiarity with Agile methodologies and project delivery best practicesCurrent TS/SCI clearance level required.Excellent organizational skills..." It seems missing punctuation. We need to parse each qualification. Likely each sentence separated by a period? Actually there is no period after field. Let's try to split: - Bachelor’s degree in Journalism, Communication, English, Business, or a related field - 10+ years of experience in strategic communication, public affairs, program management, or strategy development - 7+ years program/project management experience including familiarity with Agile methodologies and project delivery best practices - Current TS/SCI clearance level required. - Excellent organizational skills with the ability to manage multiple projects simultaneously, maintaining a strong focus on accuracy and attention to detail - Exceptional written and verbal communication skills, with the ability to communicate in a clear, approachable, and knowledgeable manner - Government contracting experience - PMP certification preferred - Security clearance as required by contracts - Experience with human-centered design and design thinking principles - Demonstrated ability to manage multiple complex projects simultaneously We'll treat each as
- .
Then "Responsibilities" section with many bullet-like sentences under headings: "Senior Strategist/Design Strategist responsibilities include:" then subheadings like "Client Partnership & Design Strategy Leadership", "Content Strategy, Storytelling & Execution", etc. Each subheading has multiple sentences. We could treat each subheading as a heading? But instruction says use
for section headings (e.g. About the role, Responsibilities...). So we likely should have a single
Responsibilities
and then under it we can have- for each duty. However the responsibilities are grouped under subheadings; we could either keep subheadings as
but not allowed? They didn't forbid other headings, but they said use
for section headings (e.g...). Might be okay to use
for subheadings, but safer to keep everything under
- and maybe include the subheading text as part of the
- content. However we need to preserve ALL substantive information; we can include the subheading as bold text inside
- but we cannot use markdown; we can use . That's allowed as HTML. So we can do
- Client Partnership & Design Strategy Leadership: ...
. That preserves. Similarly for Program Manager Responsibilities Include: we could treat as part of Responsibilities as well, maybe separate subheading. Thus we will have a single Responsibilities section with many- items, each possibly containing a subheading. Then "Work Schedule" paragraph: "Hybrid onsite presence 3-5 days per week may be required for client meetings, presentations, or working sessions.Full time, 40 hours per weekSome travel required to attend relevant events and conferences, and participate in LINK team events". That's schedule info. So we should have a
Schedule
withcontaining that. Then "Salary: We're committed to offering competitive compensation. While the salary range for this position is $112,000-$151,000, your final offer may be adjusted based on factors like experience and location." That's pay info. So
Pay
with. Then Benefits: list of benefits. So
Benefits
with- .
We also need to include location maybe as a short
before sections. We must not include EEO boilerplate etc. Remove that at end. Also remove duplicated lines, application instructions. Now construct HTML. Start with maybe an introductory
for Who We Are and Location. Let's draft:
LINK is a fast-growing Woman Owned Small Business (WOSB) that leverages human-centered design to support strategy, innovation, communication, change, and branding within the federal government and adjacent industry partners. At LINK, we partner with engineers, futurists, and thought leaders to untangle complexity, discover opportunity, and communicate clearly with visual stories. Let us be your partners in change.
Location: We are actively hiring in the Charleston, SC area.
ThenAbout the role
with paragraph about opportunity.LINK is actively seeking a Senior Design Strategist or Strategist; Program Manager to join our dynamic team, where we leverage strong partnerships and a robust portfolio of clients across diverse industries. You will be responsible for leading and executing innovative design strategies, collaborating with both internal teams and executive-level clients, and driving impactful visual storytelling to meet client objectives. This is an exciting opportunity for an experienced professional to bring a combination of creative and strategic expertise to elevate LINK’s business growth and deliver high-quality, human-centered design solutions. You will work closely with clients to understand their challenges, develop compelling narratives, and implement design strategies that align with their mission, goals, and brand identity. Ideal candidates will have a proven track record of designing impactful visual experiences, utilizing data-driven insights, and collaborating cross-functionally to deliver exceptional client results.
ThenQualifications
with- each qualification.
Then
Responsibilities
with- each duty. We need to extract responsibilities from the text. Let's list them: Under Senior Strategist/Design Strategist responsibilities include: - Client Partnership & Design Strategy Leadership * Serves as a trusted advisor to clients by framing complex challenges, identifying opportunities, and applying human-centered design approaches to inform strategic decision-making. * Partners directly with client stakeholders to understand organizational priorities, user needs, operational constraints, and desired outcomes. * Leads the development of design strategy approaches that align stakeholder needs, business objectives, and mission requirements. * Guides cross-functional teams through ambiguity, helping stakeholders build alignment and make informed decisions. * Identifies opportunities to create tangible business value and support long-term client success. * Provides guidance that helps clients make informed decisions and navigate organizational complexity. - Content Strategy, Storytelling & Execution * Translates complex ideas into compelling strategic narratives, executive-level presentations, communication strategies, and decision-support products. * Develops messaging frameworks that align leadership vision, organizational priorities, and stakeholder needs. * Define content structures, information hierarchies, and storytelling approaches that communicate complex concepts clearly and effectively. * Collaborates with creative teams to develop high-quality visual products that support strategic objectives and audience understanding. * Establishes quality standards for strategic deliverables and provides guidance to team members to ensure consistency and excellence. * Leads development of executive-ready materials that support decision-making, alignment, and organizational action. - Change Management & Organizational Transformation * Develops and implements change management strategies, including stakeholder engagement plans, communications strategies, change impact assessments, and adoption roadmaps. * Designs governance frameworks, operating models, and implementation approaches that support successful transformation efforts. * Facilitates cross-functional working sessions that drive alignment, accelerate decision-making, and address organizational resistance. * Establishes feedback mechanisms and performance measures that support continuous improvement and long-term success. * Monitors progress, evaluates outcomes, and refines approaches based on stakeholder feedback and organizational needs. - Research, Insight Development & Systems Thinking * Leads mixed-method research efforts, including stakeholder interviews, contextual inquiry, observations, journey mapping, ecosystem analysis, and systems mapping activities. * Synthesizes qualitative and quantitative findings into actionable insights, opportunity areas, strategic recommendations, and design directions. * Applies systems thinking to identify patterns, dependencies, root causes, and opportunities across complex organizational environments. * Translates technical, operational, and policy-focused challenges into human-centered insights and strategic considerations. * Guides research activities that inform organizational transformation, service design, experience design, and strategic planning efforts. - Workshop Facilitation & Stakeholder Alignment * Designs and facilitates workshops, design sprints, stakeholder engagements, and co-creation activities that advance strategic objectives and drive organizational alignment. * Develops facilitation approaches, agendas, exercises, and collaborative experiences that enable productive dialogue and structured problem-solving. * Synthesizes workshop outputs into actionable findings, recommendations, and implementation considerations. * Helps stakeholders navigate competing priorities, organizational complexity, and change initiatives through structured facilitation and engagement. * Guides teams in applying human-centered design methods throughout project lifecycles. - Team Development & Leadership * Mentors teammates through coaching, knowledge sharing, and constructive feedback. * Models LINK values and contributes to a collaborative,
- each qualification.
Then
- for each duty. However the responsibilities are grouped under subheadings; we could either keep subheadings as