Technical Information Architect/ Confluence Content Specialist

Job Title: Technical Information Architect
Location: Fridley, MN

Project Overview:

The PGBASE program is an embedded software development architecture and framework . It includes workflows, tools, processes, architecture documentation, and training content - all of which were originally housed in an internal Wiki that served as the single source of truth for engineering teams. This content was later migrated to SharePoint, but that migration broke internal references, link structures, and navigation, making the material difficult to use and explore.

We are now seeking a skilled temporary resource to migrate, restructure, and rebuild the PGBASE information in Confluence, creating a logically organized, easily navigable, and user-friendly technical knowledge base that accurately reflects the structure and relationships within the PGBASE ecosystem. After restructuring, this person will also develop training and "How-To" materials and provide orientation sessions or demonstrations to help users quickly adopt and effectively use the new Confluence site.

Primary Responsibilities:

• Review and map existing PGBASE content currently stored in SharePoint to understand its structure, relationships, and navigation gaps.
• Plan and execute the migration of PGBASE documentation from SharePoint to Confluence, ensuring preservation of version history, metadata, and relationships where possible.
• Design and implement a new information architecture in Confluence that improves discoverability, logical flow, and consistency across topics.
• Rebuild cross-linking between related content and re-establish navigation paths and reference integrity.
• Collaborate closely with internal subject matter experts (SMEs) to validate structure, taxonomy, and content placement.
• Standardize formatting and templates for technical documentation to ensure consistency and readability.
• Recommend and apply Confluence best practices for navigation menus, macros, labeling/tagging, and hierarchy organization.
• Create user-friendly training and How-To guides to help internal users navigate, update, and maintain content in the new Confluence environment.
• Provide training sessions, demonstrations, or short onboarding workshops for internal stakeholders to ensure smooth adoption of the new documentation system.
• Optionally, assist in light content editing to improve clarity, context, or user comprehension where needed.

Core Skills:

• Proven experience with Confluence administration, space design, and content management.
• Experience with SharePoint content organization and migration projects.
• Strong understanding of information architecture and knowledge management principles.
• Familiarity with technical documentation workflows, ideally in an engineering or software development environment.
• Ability to translate complex technical systems (software tools, embedded frameworks, engineering processes) into organized, user-accessible structures.
• Experience designing or improving taxonomy, metadata, and linking structures in technical documentation.
• Experience developing training documentation, tutorials, or end-user guidance for technical platforms.

Technical/Domain Competence:

• General literacy in embedded software development concepts, such as architectures, workflows, or system interfaces.
• Comfort with technical terminology and engineering artifacts (requirements, specifications, test procedures).
• Working knowledge of software documentation tools and collaboration platforms (e.g., Confluence, SharePoint, Markdown, Git-based wikis).

Soft Skills and Attributes:

• Strong analytical thinking - able to quickly understand complex systems and how documentation fits together.
• Excellent attention to detail and consistency.
• Clear communicator, capable of explaining structures, workflows, and documentation approaches to varied audiences.
• Collaborative and communicative - able to work effectively with engineers, SMEs, and non-technical stakeholders.
• Organized, self-directed, and capable of driving a documentation structure project from start to finish.
• Practical approach - focused on building a usable, maintainable structure rather than overly complex design.