Technical Writer

Determining compensation for this role (and others) at Vaco/Highspring depends upon a wide array of factors including but not limited to the individual’s skill sets, experience and training, licensure and certifications, office location and other geographic considerations, as well as other business and organizational needs. With that said, as required by local law in geographies that require salary range disclosure, Vaco/Highspring notes the salary range for the role is noted in this job posting. The individual may also be eligible for discretionary bonuses, and can participate in medical, dental, and vision benefits as well as the company’s 401(k) retirement plan.


Core Technical Writing Skills

• Excellent written communication: Ability to clearly and concisely explain complex technical concepts to both technical and non-technical audiences.
• Information architecture: Skilled in organizing and structuring documentation for usability and scalability.
• Attention to detail: Precision in documenting field-level mappings, data flows, and UI elements.

Technical Knowledge & Tools

• Understanding of data integration concepts: Familiarity with APIs, payload structures (e.g., JSON, XML), and data mapping between systems.
• Experience with platform architecture documentation: Ability to trace data lineage, identify field sources, and document system interactions.
• Proficiency with documentation tools: Such as Confluence, Markdown, DITA, or other content management systems.
• Basic querying and data inspection: Ability to use tools like SQL, or browser dev tools to inspect payloads and field values.

Collaboration & Process

• Cross-functional collaboration: Experience working with developers, product managers, and business analysts to gather and validate technical information.
• Agile documentation practices: Comfortable working in iterative environments and updating documentation alongside development cycles.
• Version control familiarity: Understanding of Git or similar tools for managing documentation changes.

 Here's a quick list: 

• Clear and concise technical writing
• Understanding of data integration (e.g., APIs, payloads)
• Experience with PowerSchool and/or Salesforce
• Documentation of platform architecture and data mappings
• Familiarity with JSON, XML, and data payloads
• Use of tools like Confluence, Markdown, or DITA
• Ability to trace data sources and field origins
• Collaboration with devs, PMs, and analysts
• Visual documentation (e.g., diagrams, flowcharts)
• Agile documentation practices
• Basic querying (e.g., SQL, Postman)
• Version control knowledge (e.g., Git)

 
Measurable Outcomes

• Fields for all custom PS tables documented
• Documentation to include:
• Source: Payload from salesforce, etc.
• Mapping to UI Element
• Field level descriptions
• Any cross-field considerations documented

• Documentation of fields associated with critical workflows
• Documentation to include:
• Flow Diagram
• Mapping to UI Element
• Critical Field descriptions