Confluence
Atlassian's team wiki and documentation platform — the standard knowledge management tool for software and product teams, typically used alongside Jira.
Confluence is Atlassian's collaborative documentation and knowledge management platform, used by software engineering, product, and operations teams to maintain technical documentation, meeting notes, project specs, runbooks, and internal wikis. It integrates tightly with Jira — tickets link to specs, sprints link to planning docs — making it the natural documentation layer for organizations already using Jira for project tracking. Confluence is deployed at the majority of technology companies and large enterprises, and proficiency with it is a listed requirement or assumed baseline in most software engineering, product management, and technical writing roles.
Typical time to job-readiness: ~1 week.
Learning Confluence
Beginner
Learn Confluence navigation: spaces, pages, and the page hierarchy. Practice creating well-structured pages using the editor — headings, tables, page layouts, and macros like Table of Contents, Info/Warning panels, and Jira issue embeds. Understand the difference between personal spaces and team spaces.
Intermediate
Page templates for consistency (meeting notes, decision logs, incident reports, RFCs), space permissions and page restrictions, and using Confluence as a living spec: linking requirements to Jira epics and keeping documentation in sync with development. Learn Confluence macros — they dramatically expand what you can build.
Advanced
Confluence administration: managing spaces, user groups, and permissions at scale; setting up space templates for new teams; integrating with external tools via REST API; and governance strategies for keeping wikis from decaying into outdated content graveyards. Senior technical writers and staff engineers are often asked how they'd structure documentation for a large organization.
Key concepts
- Spaces: top-level organizational containers — typically one per team or product area
- Pages: the primary content unit; organized in a hierarchical tree within a space
- Macros: built-in content blocks that add tables of contents, Jira issue lists, status labels, and more
- Page templates: pre-formatted layouts for recurring document types (meeting notes, RFC, decision log)
- Inline comments and page-level comments: feedback without editing the document
- Jira integration: embed live issue counts, sprint boards, or individual tickets directly in Confluence pages
Common interview topics
- How do you structure a Confluence space for a software team
- How do you keep documentation from becoming outdated
- What is the difference between Confluence and Notion — when would you use each
- How do you use Confluence page templates
- How would you organize technical documentation for a new product launch