Microsoft Communications Specialist
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from posting, but we can format them.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove duplicated lines like repeated Bachelor's degree etc. We need to deduplicate.
We need to keep all substantive info: responsibilities list, qualifications, skills, benefits, etc.
Let's extract.
First, About the role: The introductory paragraph: "Join Centric Consulting – A Culture You’ll Love At Centric Consulting, we've cultivated a unique approach to business. Our business is built on three fundamental principles: Enjoy the people you work with, have fun, and do great work. These principles define our consulting model and have crafted one of the most vibrant cultures in the consulting industry – celebrating individuals, collaboration, and lifelong friendships." Also maybe "In this role, you will:" but that's responsibilities. So About the role could be that culture description.
Also maybe include "Job Level: Specialist Job Location: Remote Travel Expectations: up top 25% Job Classification: Full-Time". That could be metadata; we could fold into About the role as a short p.
But rule: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include a short p with those details.
Now Responsibilities: Many bullet points. Let's list them uniquely.
From "In this role, you will:":
- Establish and operate a consistent Win Wire process that captures, drafts, approves, and distributes Microsoft-relevant wins in a timely and professional manner.
- Operate a consistent Win Wire process that captures, approves, and distributes Microsoft-relevant wins. (duplicate of first? Slightly different but similar)
- Increase Centric’s visibility with Microsoft sellers through concise, field-ready proof points and success stories.
- Build a reusable customer story pipeline for case studies, Microsoft-facing proof points, event content, and award submissions.
- Create practical internal enablement content that helps BU, sales, and delivery teams understand how to engage Microsoft, position CSP, and use funding programs.
- Partner with Marketing to ensure Microsoft communications are brand-aligned, polished, and reusable.
- Track content production, usage, feedback, and improvement opportunities.
Then "Key Responsibilities:" list:
- Own a repeatable Win Wire process that captures, approves, packages, and distributes Microsoft-relevant wins to internal stakeholders and Microsoft field teams.
- Build and maintain a pipeline of customer stories, proof points, case study inputs, and Partner of the Year-ready content tied to Microsoft priorities and measurable client outcomes.
- Partner with Channel Sales, Solution Sales, delivery teams, account teams, and Marketing to gather accurate story details and determine how each win or story should be used.
- Create concise internal communications and enablement assets that explain how Centric sells with and through Microsoft, including priority offerings, CSP, co-sell motions, Marketplace, and Microsoft funding programs.
- Maintain consistent messaging around Centric’s Microsoft partnership, prioritized managed partner status, solution designations, specializations, CSP capabilities, funding alignment, and co-sell readiness.
- Develop reusable content such as Teams posts, newsletters, quick-reference guides, FAQs, one-pagers, presentation content, seller updates, event recaps, and executive-ready briefs.
- Support and maintain a Microsoft content hub or index so teams can easily find current Win Wires, customer stories, enablement materials, funding guidance, contacts, and templates.
- Coordinate with Channel Sales, Solution Sales, BU leaders, delivery teams, CSP/licensing stakeholders, Marketing, and Microsoft Partnership leadership to gather input, manage reviews, and keep communications moving.
- Maintain a Microsoft communications calendar covering Win Wires, enablement, customer stories, seller updates, events, and campaigns.
- Track content volume, quality, usage, distribution, feedback, approval bottlenecks, and improvement opportunities.
- Use feedback and lessons learned to improve templates, intake processes, approval workflows, and reusable content formats.
- Document and launch a Win Wire intake, approval, distribution, and tracking process within the first 60 days.
- Produce at least 2 Microsoft-focused Win Wires per month, with approved content distributed within 10 business days of intake for complete submissions.
- Maintain a current customer story inventory with at least 10 qualified Microsoft-relevant stories by the end of the first 90 days.
- Create and publish at least 5 reusable enablement assets covering priority offerings, CSP licensing, co-sell engagement, Microsoft funding, and “how to engage” guidance within the first 120 days.
- Deliver a monthly Microsoft communications update or digest covering wins, stories, enablement assets, events, and priority partner updates.
- Maintain a Microsoft content hub or index with current Win Wires, customer stories, enablement assets, funding guidance, contacts, and templates, reviewed at least monthly for accuracy.
- Achieve positive stakeholder feedback from Microsoft Partnership leadership, Channel Sales, Solution Sales, Marketing, and BU stakeholders, with at least 80% of surveyed respondents rating content clarity and usefulness as effective or better.
We need to deduplicate similar items. For example, "Establish and operate a consistent Win Wire process..." vs "Own a repeatable Win Wire process..." similar but we can keep both? Might be considered duplicate. We should avoid duplicated lines. We'll combine similar responsibilities into one bullet maybe but must preserve ALL substantive information; we cannot lose detail. If we combine, we might lose nuance. Better to keep both but note they are similar but not identical. The rule says remove duplicated lines. If they are not exactly same, we keep.
We'll produce a
with each responsibility as - . Might be long but okay.
Now Requirements/Qualifications: "Who You Are:" includes:
- Bachelor’s degree in communications, marketing communications, business communication, English, public relations, or a related field preferred, or equivalent practical experience. (appears twice; we keep once)
- Excellent writer and editor who can turn complex business, technology, and partnership information into clear, concise content. (appears twice)
- 2 to 5 years of experience in communications, marketing communications, Microsoft partner marketing, sales enablement, content marketing, internal communications, or professional services marketing. (twice)
- Experience creating B2B content such as case studies, sales collateral, newsletters, one-pagers, executive summaries, internal announcements, or enablement materials. (twice)
- Strong storytelling, interviewing, and synthesis skills, with the ability to extract key details from SMEs, sellers, delivery leaders, account teams, meetings, CRM data, and sales notes. (twice)
- Organized, proactive, and comfortable managing drafts, deadlines, stakeholders, approvals, distribution channels, and content trackers. (twice)
- Experience collaborating with sales, marketing, alliances, partnerships, technology teams, or consulting teams. (twice)
- Curiosity about Microsoft, cloud technology, AI, licensing, partner programs, CSP, co-sell motions, and strategic alliances. (twice)
We'll deduplicate.
Now Skills: Could be extracted from the qualifications as skills: excellent writer/editor, storytelling, interviewing, synthesis, organized, proactive, managing drafts, deadlines, stakeholders, approvals, distribution channels, content trackers, collaborating, curiosity about Microsoft etc. We could put them in Skills section.
But we already have Qualifications section that includes degree and experience. Skills could be separate.
We need to decide sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have content for About, Responsibilities, Requirements (maybe degree?), Qualifications (experience?), Skills (specific abilities), Benefits, Schedule (full-time remote). Pay not present.
We must not create Pay section.
Now we need to avoid filler like "commensurate with experience". Not present.
Now produce HTML.
Structure:
About the role
Join Centric Consulting – A Culture You’ll Love. At Centric Consulting, we've cultivated a unique approach to business built on three fundamental principles: enjoy the people you work with, have fun, and do great work. These principles define our consulting model and have crafted one of the most vibrant cultures in the consulting industry – celebrating individuals, collaboration, and lifelong friendships. Job Level: Specialist. Job Location: Remote. Travel Expectations: up to 25%. Job Classification: Full-Time.
But we need to ensure we don't repeat "Job Level:" etc as separate headings; it's okay as part of p.
Now Responsibilities:
Responsibilities
- Establish and operate a consistent Win Wire process that captures, drafts, approves, and distributes Microsoft-relevant wins in a timely and professional manner.
- Operate a consistent Win Wire process that captures, approves, and distributes Microsoft-relevant wins.
- Increase Centric’s visibility with Microsoft sellers through concise, field-ready proof points and success stories.
- Build a reusable customer story pipeline for case studies, Microsoft-facing proof points, event content, and award submissions.
- Create practical internal enablement content that helps BU, sales, and delivery teams understand how to engage Microsoft, position CSP, and use funding programs.
- Partner with Marketing to ensure Microsoft communications are brand-aligned, polished, and reusable.
- Track content production, usage, feedback, and improvement opportunities.
- Own a repeatable Win Wire process that captures, approves, packages, and distributes Microsoft-relevant wins to internal stakeholders and Microsoft field teams.
- Build and maintain a pipeline of customer stories, proof points, case study inputs, and Partner of the Year-ready content tied to Microsoft priorities and measurable client outcomes.
- Partner with Channel Sales, Solution Sales, delivery teams, account teams, and Marketing to gather accurate story details and determine how each win or story should be used.
- Create concise internal communications and enablement assets that explain how Centric sells with and through Microsoft, including priority offerings, CSP, co-sell motions, Marketplace, and Microsoft funding programs.
for prose. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from posting, but we can format them. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove duplicated lines like repeated Bachelor's degree etc. We need to deduplicate. We need to keep all substantive info: responsibilities list, qualifications, skills, benefits, etc. Let's extract. First, About the role: The introductory paragraph: "Join Centric Consulting – A Culture You’ll Love At Centric Consulting, we've cultivated a unique approach to business. Our business is built on three fundamental principles: Enjoy the people you work with, have fun, and do great work. These principles define our consulting model and have crafted one of the most vibrant cultures in the consulting industry – celebrating individuals, collaboration, and lifelong friendships." Also maybe "In this role, you will:" but that's responsibilities. So About the role could be that culture description. Also maybe include "Job Level: Specialist Job Location: Remote Travel Expectations: up top 25% Job Classification: Full-Time". That could be metadata; we could fold into About the role as a short p. But rule: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include a short p with those details. Now Responsibilities: Many bullet points. Let's list them uniquely. From "In this role, you will:": - Establish and operate a consistent Win Wire process that captures, drafts, approves, and distributes Microsoft-relevant wins in a timely and professional manner. - Operate a consistent Win Wire process that captures, approves, and distributes Microsoft-relevant wins. (duplicate of first? Slightly different but similar) - Increase Centric’s visibility with Microsoft sellers through concise, field-ready proof points and success stories. - Build a reusable customer story pipeline for case studies, Microsoft-facing proof points, event content, and award submissions. - Create practical internal enablement content that helps BU, sales, and delivery teams understand how to engage Microsoft, position CSP, and use funding programs. - Partner with Marketing to ensure Microsoft communications are brand-aligned, polished, and reusable. - Track content production, usage, feedback, and improvement opportunities. Then "Key Responsibilities:" list: - Own a repeatable Win Wire process that captures, approves, packages, and distributes Microsoft-relevant wins to internal stakeholders and Microsoft field teams. - Build and maintain a pipeline of customer stories, proof points, case study inputs, and Partner of the Year-ready content tied to Microsoft priorities and measurable client outcomes. - Partner with Channel Sales, Solution Sales, delivery teams, account teams, and Marketing to gather accurate story details and determine how each win or story should be used. - Create concise internal communications and enablement assets that explain how Centric sells with and through Microsoft, including priority offerings, CSP, co-sell motions, Marketplace, and Microsoft funding programs. - Maintain consistent messaging around Centric’s Microsoft partnership, prioritized managed partner status, solution designations, specializations, CSP capabilities, funding alignment, and co-sell readiness. - Develop reusable content such as Teams posts, newsletters, quick-reference guides, FAQs, one-pagers, presentation content, seller updates, event recaps, and executive-ready briefs. - Support and maintain a Microsoft content hub or index so teams can easily find current Win Wires, customer stories, enablement materials, funding guidance, contacts, and templates. - Coordinate with Channel Sales, Solution Sales, BU leaders, delivery teams, CSP/licensing stakeholders, Marketing, and Microsoft Partnership leadership to gather input, manage reviews, and keep communications moving. - Maintain a Microsoft communications calendar covering Win Wires, enablement, customer stories, seller updates, events, and campaigns. - Track content volume, quality, usage, distribution, feedback, approval bottlenecks, and improvement opportunities. - Use feedback and lessons learned to improve templates, intake processes, approval workflows, and reusable content formats. - Document and launch a Win Wire intake, approval, distribution, and tracking process within the first 60 days. - Produce at least 2 Microsoft-focused Win Wires per month, with approved content distributed within 10 business days of intake for complete submissions. - Maintain a current customer story inventory with at least 10 qualified Microsoft-relevant stories by the end of the first 90 days. - Create and publish at least 5 reusable enablement assets covering priority offerings, CSP licensing, co-sell engagement, Microsoft funding, and “how to engage” guidance within the first 120 days. - Deliver a monthly Microsoft communications update or digest covering wins, stories, enablement assets, events, and priority partner updates. - Maintain a Microsoft content hub or index with current Win Wires, customer stories, enablement assets, funding guidance, contacts, and templates, reviewed at least monthly for accuracy. - Achieve positive stakeholder feedback from Microsoft Partnership leadership, Channel Sales, Solution Sales, Marketing, and BU stakeholders, with at least 80% of surveyed respondents rating content clarity and usefulness as effective or better. We need to deduplicate similar items. For example, "Establish and operate a consistent Win Wire process..." vs "Own a repeatable Win Wire process..." similar but we can keep both? Might be considered duplicate. We should avoid duplicated lines. We'll combine similar responsibilities into one bullet maybe but must preserve ALL substantive information; we cannot lose detail. If we combine, we might lose nuance. Better to keep both but note they are similar but not identical. The rule says remove duplicated lines. If they are not exactly same, we keep. We'll produce a
- with each responsibility as
- . Might be long but okay.
Now Requirements/Qualifications: "Who You Are:" includes:
- Bachelor’s degree in communications, marketing communications, business communication, English, public relations, or a related field preferred, or equivalent practical experience. (appears twice; we keep once)
- Excellent writer and editor who can turn complex business, technology, and partnership information into clear, concise content. (appears twice)
- 2 to 5 years of experience in communications, marketing communications, Microsoft partner marketing, sales enablement, content marketing, internal communications, or professional services marketing. (twice)
- Experience creating B2B content such as case studies, sales collateral, newsletters, one-pagers, executive summaries, internal announcements, or enablement materials. (twice)
- Strong storytelling, interviewing, and synthesis skills, with the ability to extract key details from SMEs, sellers, delivery leaders, account teams, meetings, CRM data, and sales notes. (twice)
- Organized, proactive, and comfortable managing drafts, deadlines, stakeholders, approvals, distribution channels, and content trackers. (twice)
- Experience collaborating with sales, marketing, alliances, partnerships, technology teams, or consulting teams. (twice)
- Curiosity about Microsoft, cloud technology, AI, licensing, partner programs, CSP, co-sell motions, and strategic alliances. (twice)
We'll deduplicate.
Now Skills: Could be extracted from the qualifications as skills: excellent writer/editor, storytelling, interviewing, synthesis, organized, proactive, managing drafts, deadlines, stakeholders, approvals, distribution channels, content trackers, collaborating, curiosity about Microsoft etc. We could put them in Skills section.
But we already have Qualifications section that includes degree and experience. Skills could be separate.
We need to decide sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have content for About, Responsibilities, Requirements (maybe degree?), Qualifications (experience?), Skills (specific abilities), Benefits, Schedule (full-time remote). Pay not present.
We must not create Pay section.
Now we need to avoid filler like "commensurate with experience". Not present.
Now produce HTML.
Structure:
About the role
Join Centric Consulting – A Culture You’ll Love. At Centric Consulting, we've cultivated a unique approach to business built on three fundamental principles: enjoy the people you work with, have fun, and do great work. These principles define our consulting model and have crafted one of the most vibrant cultures in the consulting industry – celebrating individuals, collaboration, and lifelong friendships. Job Level: Specialist. Job Location: Remote. Travel Expectations: up to 25%. Job Classification: Full-Time.
But we need to ensure we don't repeat "Job Level:" etc as separate headings; it's okay as part of p. Now Responsibilities:Responsibilities
- Establish and operate a consistent Win Wire process that captures, drafts, approves, and distributes Microsoft-relevant wins in a timely and professional manner.
- Operate a consistent Win Wire process that captures, approves, and distributes Microsoft-relevant wins.
- Increase Centric’s visibility with Microsoft sellers through concise, field-ready proof points and success stories.
- Build a reusable customer story pipeline for case studies, Microsoft-facing proof points, event content, and award submissions.
- Create practical internal enablement content that helps BU, sales, and delivery teams understand how to engage Microsoft, position CSP, and use funding programs.
- Partner with Marketing to ensure Microsoft communications are brand-aligned, polished, and reusable.
- Track content production, usage, feedback, and improvement opportunities.
- Own a repeatable Win Wire process that captures, approves, packages, and distributes Microsoft-relevant wins to internal stakeholders and Microsoft field teams.
- Build and maintain a pipeline of customer stories, proof points, case study inputs, and Partner of the Year-ready content tied to Microsoft priorities and measurable client outcomes.
- Partner with Channel Sales, Solution Sales, delivery teams, account teams, and Marketing to gather accurate story details and determine how each win or story should be used.
- Create concise internal communications and enablement assets that explain how Centric sells with and through Microsoft, including priority offerings, CSP, co-sell motions, Marketplace, and Microsoft funding programs.