Domain
Version Control & Collaboration
Skill Profile
InnerSource, contribution guidelines, discoverability, cross-team collaboration
Roles
3
where this skill appears
Levels
5
structured growth path
Mandatory requirements
6
the other 7 optional
Version Control & Collaboration
Collaboration Tools
3/17/2026
Choose your current level and compare expectations. The items below show what to cover to advance to the next level.
The table shows how skill depth grows from Junior to Principal. Click a row to see details.
| Role | Required | Description |
|---|---|---|
| Technical Writer | Understands the InnerSource concept: applying open-source practices within a company. Knows the role of documentation in InnerSource: README, CONTRIBUTING, CODE_OF_CONDUCT. Can create basic documentation for internal projects. |
| Role | Required | Description |
|---|---|---|
| Engineering Manager | Applies InnerSource practices in team management: encourages cross-team contributions, establishes contribution guidelines, and tracks InnerSource participation metrics. Facilitates team collaboration on shared internal projects and documentation. | |
| Technical Lead | Applies InnerSource practices in technical leadership: establishes code contribution standards, reviews cross-team pull requests, and maintains shared library documentation. Facilitates technical knowledge sharing through InnerSource project governance. | |
| Technical Writer | Creates comprehensive InnerSource documentation: contribution guides, architecture overviews, getting started, API references. Helps projects become discoverability-friendly through quality documentation. Adapts open-source documentation best practices. |
| Role | Required | Description |
|---|---|---|
| Engineering Manager | Required | Designs InnerSource program for engineering organization: defines Trusted Committer roles, contribution workflows, and incentive structures. Implements metrics for measuring cross-team collaboration effectiveness and knowledge transfer impact. |
| Technical Lead | Required | Designs InnerSource technical practices: shared codebase architecture, API-first internal platforms, and cross-team code review standards. Implements automated contribution quality gates and documentation-as-code for shared components. |
| Technical Writer | Designs documentation framework for the company's InnerSource program: standards, templates, quality requirements. Creates internal developer portal for InnerSource project discoverability. Trains teams on writing quality documentation. |
| Role | Required | Description |
|---|---|---|
| Engineering Manager | Required | Defines InnerSource strategy at product/department level: establishes governance models, community management practices, and success measurement frameworks. Coordinates InnerSource adoption across multiple teams with stakeholder alignment. |
| Technical Lead | Required | Defines InnerSource technical strategy: shared platform architecture, reusable component libraries, and cross-team development standards. Establishes technical governance for internal open-source projects with release management and versioning policies. |
| Technical Writer | Defines documentation strategy for InnerSource at the organizational level. Coordinates documentation for cross-team projects. Builds a culture of documentation through InnerSource practices, training, and incentives. |
| Role | Required | Description |
|---|---|---|
| Engineering Manager | Required | Defines enterprise InnerSource strategy and cultural transformation roadmap. Shapes organizational structure for maximum cross-team collaboration. Mentors engineering leaders on InnerSource adoption patterns and community building. |
| Technical Lead | Required | Defines enterprise InnerSource technical architecture and platform strategy. Shapes organization-wide engineering practices for internal code sharing, API governance, and developer experience. Mentors leads on building sustainable InnerSource ecosystems. |
| Technical Writer | Shapes corporate InnerSource documentation and knowledge sharing strategy. Determines investments in documentation infrastructure. Builds connections between InnerSource docs, developer portal, and architecture knowledge base. |