Knowledgebase Content Specialist
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must include sections only when posting has real specific content. So we need sections: About SoftWriters (maybe "About the company"? but heading must be from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The instruction says: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It seems they expect those specific headings. But we can also use other headings? The examples are given but not exclusive? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they want us to use those headings when applicable. We need to map content to those sections.
We have: About SoftWriters (company overview) could be "About the role"? Actually "About the role" is about the job, not company. But we could use "About the role" to describe the opportunity. The posting includes "The Opportunity" and "About SoftWriters". Could combine into "About the role". However we also have "What You'll Do" which is responsibilities. "What We're Looking For" includes requirements, qualifications, skills. "Why You'll Love Working Here" includes benefits, work environment, values. So we can map:
- About the role: combine The Opportunity and About SoftWriters? Might be okay.
- Responsibilities: What You'll Do (list of duties).
- Requirements: Required qualifications (Bachelor's degree, proven experience, etc.) Could be under Requirements.
- Qualifications: Preferred qualifications (4-7 years, AI, Agile, healthcare, etc.) Could be under Qualifications.
- Skills: maybe combine some skill statements? Could be under Skills.
- Benefits: Why You'll Love Working Here includes benefits and work environment.
- Pay: Not specified (they mention Competitive salary but no specifics). According to rule: never create Pay/Schedule/Benefits sections unless posting actually states them. They say "Competitive salary" but not specific number. Is that enough? It's vague but still states competitive salary. However they said never create Pay/Schedule/Benefits sections unless posting actually states them. "Competitive salary" is a statement about pay, albeit not specific. Might be considered stating pay. But they also said never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "Competitive salary" is similar to filler? It's vague but not exactly those. Might be considered filler. Safer to omit Pay section.
- Schedule: They mention Hybrid - Pittsburgh, PA (Core office days: Tuesday, Wednesday, Thursday). That's schedule info. So we can include Schedule section.
- Benefits: We have benefits listed: Modern Work Environment, Recognized Top Workplace, Work-Life Balance Hybrid work policy with flexible hours, Remote-Work Bank, Paid parking, PTO day on your birthday, Floating holidays, Comprehensive Benefits: Competitive salary, 100% paid parental leave, 401(k) with company match, Comprehensive medical, dental, vision, Life and disability insurance, Growth-Focused Culture, Continuous learning, etc. So we can include Benefits section.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills?, Benefits, Schedule.
We need to decide if we need Skills section. Could extract skill statements: Exceptional writing, editing, proofreading, communication skills; Experience developing user-friendly documentation; Proficiency with CMS, documentation tools, knowledge management platforms; Experience with platforms such as Microsoft SharePoint, Aha! Knowledge, or comparable; Strong project management and organizational skills; Ability to collaborate effectively across cross-functional teams and translate complex information into clear, actionable documentation. Those could be skills. We could put them under Skills.
But we must not repeat content. We'll need to ensure we preserve all substantive information. We'll need to parse the posting and include all details.
Let's extract content:
About SoftWriters: "SoftWriters develops innovative IT solutions that empower long-term care (LTC) pharmacies to deliver life-saving medications more efficiently and accurately. As a voted top workplace in Pittsburgh, we combine meaningful work with a collaborative culture where your contributions directly impact patient care."
The Opportunity: "We're seeking a Knowledgebase Content Specialist to join our growing team and help shape the future of healthcare technology. In this role, you'll create and maintain the critical documentation that empowers employees, customers, and partners to successfully leverage SoftWriters' solutions, while driving clarity, consistency, and continuous improvement across our knowledge ecosystem."
Location: Hybrid - Pittsburgh, PA (Core office days: Tuesday, Wednesday, Thursday)
Reports to: Product Release Manager
What You'll Do (Responsibilities):
- Develop, maintain, and enhance high-quality internal documentation including Standard Operating Procedures (SOPs), process documentation, and training materials.
- Create and update customer-facing content such as User Guides, Help Guides, FAQs, release documentation, and knowledge base articles that support exceptional user experiences.
- Manage the full documentation lifecycle, including content planning, drafting, editing, stakeholder review, publishing, and ongoing maintenance.
- Maintain a well-organized and accessible knowledge base, ensuring information remains accurate, relevant, and aligned with evolving products and business processes.
- Leverage AI-powered tools and modern content management practices to improve documentation quality, efficiency, engagement, and usability.
- Conduct knowledge audits and root cause analysis to identify documentation gaps, outdated content, process inefficiencies, and opportunities for improvement.
- Coordinate documentation deliverables across multiple projects and product releases, balancing competing priorities while meeting deadlines and quality expectations.
- Partner closely with Subject Matter Experts, Product Management, Support, Operations, and other stakeholders to gather information, validate content, and drive knowledge-sharing initiatives.
What We're Looking For (Required):
- Bachelor's degree in English, Communications, Technical Writing, or a related field.
- Proven experience as a Knowledgebase Content Specialist, Technical Writer, Content Manager, or similar documentation-focused role.
- Exceptional writing, editing, proofreading, and communication skills with strong attention to detail.
- Experience developing user-friendly documentation for both technical and non-technical audiences.
- Proficiency with content management systems (CMS), documentation tools, and knowledge management platforms.
- Experience with platforms such as Microsoft SharePoint, Aha! Knowledge, or comparable knowledge management solutions.
- Strong project management and organizational skills with the ability to manage multiple initiatives, coordinate stakeholder reviews, and consistently meet deadlines.
- Demonstrated ability to collaborate effectively across cross-functional teams and translate complex information into clear, actionable documentation.
Preferred:
- 4-7 years of technical writing, knowledge management, or content development experience within a software or technology environment.
- Experience utilizing AI technologies and automation tools to improve content creation, maintenance, and user engagement.
- Familiarity with Agile methodologies, software development lifecycles, and product release processes.
- Healthcare technology, long-term care pharmacy, or healthcare software experience.
- Experience conducting knowledge audits, performing root cause analysis, and recommending process improvements.
- Experience planning and executing large-scale documentation initiatives across multiple teams and stakeholders.
- Familiarity with project management and collaboration tools such as Jira, Azure DevOps, Aha!, Monday.com, or similar platforms.
- Strong ability to create intuitive, user-centric documentation that improves adoption and reduces support burden.
Why You'll Love Working Here:
- Meaningful Work: Your contributions will help pharmacies, healthcare organizations, and internal teams access critical information that supports patient care and operational excellence.
- Modern Work Environment: Brand new, high-tech office with stunning Pittsburgh city views, located directly on the North Shore waterfront.
- Recognized Top Workplace: Consistently voted one of the best places to work in Pittsburgh.
- Work-Life Balance: Hybrid work policy with flexible hours, Remote-Work Bank for additional flexibility, Paid parking provided, PTO day on your birthday, Floating holidays.
- Comprehensive Benefits: Competitive salary, 100% paid parental leave, 401(k) with company match, Comprehensive medical, dental, and vision coverage, Life and disability insurance.
- Growth-Focused Culture: Continuous learning and development opportunities, Cross-functional collaboration, Clear career advancement paths, Opportunities to work with emerging AI-driven content and knowledge management technologies.
- Our Values in Action: Innovators, Thought Leaders, Teachers: We invest in your growth and encourage knowledge sharing. Accountability and Ownership: Take initiative, own outcomes, celebrate wins. Customer-Centric: Direct connection to the pharmacies and patients we serve. Unyielding Integrity: Ethical decision-making in everything we do. One Team, Family Spirit: Collaborative environment where everyone's success matters.
Note about visa: "Note: This position does not sponsor work visas and requires ability to work hybrid from our Pittsburgh office. Relocation assistance is not provided." This is minor metadata; we can fold into a short p or drop. Probably include as a short p under maybe About the role or separate? But we should not create extra headings for minor metadata. We'll include a short p after sections maybe.
Now we need to output HTML fragment with headings and appropriate
or
- .
We must not repeat job title as heading. We'll not include any heading for job title.
We'll produce sections:
About the role
SoftWriters develops innovative IT solutions that empower long-term care (LTC) pharmacies to deliver life-saving medications more efficiently and accurately. As a voted top workplace in Pittsburgh, we combine meaningful work with a collaborative culture where your contributions directly impact patient care. We're seeking a Knowledgebase Content Specialist to join our growing team and help shape the future of healthcare technology. In this role, you'll create and maintain the critical documentation that empowers employees, customers, and partners to successfully leverage SoftWriters' solutions, while driving clarity, consistency, and continuous improvement across our knowledge ecosystem.
Optionally include location and reports to? Could be in same p.
Responsibilities
- Develop, maintain, and enhance high-quality internal documentation including Standard Operating Procedures (SOPs), process documentation, and training materials.
- Create and update customer-facing content such as User Guides, Help Guides, FAQs, release documentation, and knowledge base articles that support exceptional user experiences.
- Manage the full documentation lifecycle, including content planning, drafting, editing, stakeholder review, publishing, and ongoing maintenance.
- Maintain a well-organized and accessible knowledge base, ensuring information remains accurate, relevant, and aligned with evolving products and business processes.
- Leverage AI-powered tools and modern content management practices to improve documentation quality, efficiency, engagement, and usability.
- Conduct knowledge audits and root cause analysis to identify documentation gaps, outdated content, process inefficiencies, and opportunities for improvement.
- Coordinate documentation deliverables across multiple projects and product releases, balancing competing priorities while meeting deadlines and quality expectations.
- Partner closely with Subject Matter Experts, Product Management, Support, Operations, and other stakeholders to gather information, validate content, and drive knowledge-sharing initiatives.
Requirements
- Bachelor's degree in English, Communications, Technical Writing, or a related field.
- Proven experience as a Knowledgebase Content Specialist, Technical Writer, Content Manager, or similar documentation-focused role.
- Exceptional writing, editing, proofreading, and communication skills with strong attention to detail.
- Experience developing user-friendly documentation
for prose. We must include sections only when posting has real specific content. So we need sections: About SoftWriters (maybe "About the company"? but heading must be from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The instruction says: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It seems they expect those specific headings. But we can also use other headings? The examples are given but not exclusive? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they want us to use those headings when applicable. We need to map content to those sections.
We have: About SoftWriters (company overview) could be "About the role"? Actually "About the role" is about the job, not company. But we could use "About the role" to describe the opportunity. The posting includes "The Opportunity" and "About SoftWriters". Could combine into "About the role". However we also have "What You'll Do" which is responsibilities. "What We're Looking For" includes requirements, qualifications, skills. "Why You'll Love Working Here" includes benefits, work environment, values. So we can map:
- About the role: combine The Opportunity and About SoftWriters? Might be okay.
- Responsibilities: What You'll Do (list of duties).
- Requirements: Required qualifications (Bachelor's degree, proven experience, etc.) Could be under Requirements.
- Qualifications: Preferred qualifications (4-7 years, AI, Agile, healthcare, etc.) Could be under Qualifications.
- Skills: maybe combine some skill statements? Could be under Skills.
- Benefits: Why You'll Love Working Here includes benefits and work environment.
- Pay: Not specified (they mention Competitive salary but no specifics). According to rule: never create Pay/Schedule/Benefits sections unless posting actually states them. They say "Competitive salary" but not specific number. Is that enough? It's vague but still states competitive salary. However they said never create Pay/Schedule/Benefits sections unless posting actually states them. "Competitive salary" is a statement about pay, albeit not specific. Might be considered stating pay. But they also said never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "Competitive salary" is similar to filler? It's vague but not exactly those. Might be considered filler. Safer to omit Pay section.
- Schedule: They mention Hybrid - Pittsburgh, PA (Core office days: Tuesday, Wednesday, Thursday). That's schedule info. So we can include Schedule section.
- Benefits: We have benefits listed: Modern Work Environment, Recognized Top Workplace, Work-Life Balance Hybrid work policy with flexible hours, Remote-Work Bank, Paid parking, PTO day on your birthday, Floating holidays, Comprehensive Benefits: Competitive salary, 100% paid parental leave, 401(k) with company match, Comprehensive medical, dental, vision, Life and disability insurance, Growth-Focused Culture, Continuous learning, etc. So we can include Benefits section.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills?, Benefits, Schedule.
We need to decide if we need Skills section. Could extract skill statements: Exceptional writing, editing, proofreading, communication skills; Experience developing user-friendly documentation; Proficiency with CMS, documentation tools, knowledge management platforms; Experience with platforms such as Microsoft SharePoint, Aha! Knowledge, or comparable; Strong project management and organizational skills; Ability to collaborate effectively across cross-functional teams and translate complex information into clear, actionable documentation. Those could be skills. We could put them under Skills.
But we must not repeat content. We'll need to ensure we preserve all substantive information. We'll need to parse the posting and include all details.
Let's extract content:
About SoftWriters: "SoftWriters develops innovative IT solutions that empower long-term care (LTC) pharmacies to deliver life-saving medications more efficiently and accurately. As a voted top workplace in Pittsburgh, we combine meaningful work with a collaborative culture where your contributions directly impact patient care."
The Opportunity: "We're seeking a Knowledgebase Content Specialist to join our growing team and help shape the future of healthcare technology. In this role, you'll create and maintain the critical documentation that empowers employees, customers, and partners to successfully leverage SoftWriters' solutions, while driving clarity, consistency, and continuous improvement across our knowledge ecosystem."
Location: Hybrid - Pittsburgh, PA (Core office days: Tuesday, Wednesday, Thursday)
Reports to: Product Release Manager
What You'll Do (Responsibilities):
- Develop, maintain, and enhance high-quality internal documentation including Standard Operating Procedures (SOPs), process documentation, and training materials.
- Create and update customer-facing content such as User Guides, Help Guides, FAQs, release documentation, and knowledge base articles that support exceptional user experiences.
- Manage the full documentation lifecycle, including content planning, drafting, editing, stakeholder review, publishing, and ongoing maintenance.
- Maintain a well-organized and accessible knowledge base, ensuring information remains accurate, relevant, and aligned with evolving products and business processes.
- Leverage AI-powered tools and modern content management practices to improve documentation quality, efficiency, engagement, and usability.
- Conduct knowledge audits and root cause analysis to identify documentation gaps, outdated content, process inefficiencies, and opportunities for improvement.
- Coordinate documentation deliverables across multiple projects and product releases, balancing competing priorities while meeting deadlines and quality expectations.
- Partner closely with Subject Matter Experts, Product Management, Support, Operations, and other stakeholders to gather information, validate content, and drive knowledge-sharing initiatives.
What We're Looking For (Required):
- Bachelor's degree in English, Communications, Technical Writing, or a related field.
- Proven experience as a Knowledgebase Content Specialist, Technical Writer, Content Manager, or similar documentation-focused role.
- Exceptional writing, editing, proofreading, and communication skills with strong attention to detail.
- Experience developing user-friendly documentation for both technical and non-technical audiences.
- Proficiency with content management systems (CMS), documentation tools, and knowledge management platforms.
- Experience with platforms such as Microsoft SharePoint, Aha! Knowledge, or comparable knowledge management solutions.
- Strong project management and organizational skills with the ability to manage multiple initiatives, coordinate stakeholder reviews, and consistently meet deadlines.
- Demonstrated ability to collaborate effectively across cross-functional teams and translate complex information into clear, actionable documentation.
Preferred:
- 4-7 years of technical writing, knowledge management, or content development experience within a software or technology environment.
- Experience utilizing AI technologies and automation tools to improve content creation, maintenance, and user engagement.
- Familiarity with Agile methodologies, software development lifecycles, and product release processes.
- Healthcare technology, long-term care pharmacy, or healthcare software experience.
- Experience conducting knowledge audits, performing root cause analysis, and recommending process improvements.
- Experience planning and executing large-scale documentation initiatives across multiple teams and stakeholders.
- Familiarity with project management and collaboration tools such as Jira, Azure DevOps, Aha!, Monday.com, or similar platforms.
- Strong ability to create intuitive, user-centric documentation that improves adoption and reduces support burden.
Why You'll Love Working Here:
- Meaningful Work: Your contributions will help pharmacies, healthcare organizations, and internal teams access critical information that supports patient care and operational excellence.
- Modern Work Environment: Brand new, high-tech office with stunning Pittsburgh city views, located directly on the North Shore waterfront.
- Recognized Top Workplace: Consistently voted one of the best places to work in Pittsburgh.
- Work-Life Balance: Hybrid work policy with flexible hours, Remote-Work Bank for additional flexibility, Paid parking provided, PTO day on your birthday, Floating holidays.
- Comprehensive Benefits: Competitive salary, 100% paid parental leave, 401(k) with company match, Comprehensive medical, dental, and vision coverage, Life and disability insurance.
- Growth-Focused Culture: Continuous learning and development opportunities, Cross-functional collaboration, Clear career advancement paths, Opportunities to work with emerging AI-driven content and knowledge management technologies.
- Our Values in Action: Innovators, Thought Leaders, Teachers: We invest in your growth and encourage knowledge sharing. Accountability and Ownership: Take initiative, own outcomes, celebrate wins. Customer-Centric: Direct connection to the pharmacies and patients we serve. Unyielding Integrity: Ethical decision-making in everything we do. One Team, Family Spirit: Collaborative environment where everyone's success matters.
Note about visa: "Note: This position does not sponsor work visas and requires ability to work hybrid from our Pittsburgh office. Relocation assistance is not provided." This is minor metadata; we can fold into a short p or drop. Probably include as a short p under maybe About the role or separate? But we should not create extra headings for minor metadata. We'll include a short p after sections maybe.
Now we need to output HTML fragment with headings and appropriate
headings and appropriate
or
- .
We must not repeat job title as heading. We'll not include any heading for job title.
We'll produce sections:
About the role
SoftWriters develops innovative IT solutions that empower long-term care (LTC) pharmacies to deliver life-saving medications more efficiently and accurately. As a voted top workplace in Pittsburgh, we combine meaningful work with a collaborative culture where your contributions directly impact patient care. We're seeking a Knowledgebase Content Specialist to join our growing team and help shape the future of healthcare technology. In this role, you'll create and maintain the critical documentation that empowers employees, customers, and partners to successfully leverage SoftWriters' solutions, while driving clarity, consistency, and continuous improvement across our knowledge ecosystem.
Optionally include location and reports to? Could be in same p.Responsibilities
- Develop, maintain, and enhance high-quality internal documentation including Standard Operating Procedures (SOPs), process documentation, and training materials.
- Create and update customer-facing content such as User Guides, Help Guides, FAQs, release documentation, and knowledge base articles that support exceptional user experiences.
- Manage the full documentation lifecycle, including content planning, drafting, editing, stakeholder review, publishing, and ongoing maintenance.
- Maintain a well-organized and accessible knowledge base, ensuring information remains accurate, relevant, and aligned with evolving products and business processes.
- Leverage AI-powered tools and modern content management practices to improve documentation quality, efficiency, engagement, and usability.
- Conduct knowledge audits and root cause analysis to identify documentation gaps, outdated content, process inefficiencies, and opportunities for improvement.
- Coordinate documentation deliverables across multiple projects and product releases, balancing competing priorities while meeting deadlines and quality expectations.
- Partner closely with Subject Matter Experts, Product Management, Support, Operations, and other stakeholders to gather information, validate content, and drive knowledge-sharing initiatives.
Requirements
- Bachelor's degree in English, Communications, Technical Writing, or a related field.
- Proven experience as a Knowledgebase Content Specialist, Technical Writer, Content Manager, or similar documentation-focused role.
- Exceptional writing, editing, proofreading, and communication skills with strong attention to detail.
- Experience developing user-friendly documentation