JIRA/Confluence consultant needed for standardization and cleanup project

We're a small lab tech company (~60 people) building laboratory automation systems. We use JIRA and Confluence as our core project management and knowledge sharing tools, but we've accumulated significant technical debt in how they're set up and used.

The problem:

We operate as a matrix organization. Our functional teams (R&D, Mechatronics/Hardware Engineering, Infrastructure/SysOps, Software Application Development, AI/MLOps, and Wet lab Research) are led by Functional Team Leads (FTLs). We also have Instrument Teams that pull resources from across these functions, led by Instrument Team Leads (ITLs). Each team has evolved their own way of using JIRA over time, and there's no consistency across epics, initiatives, labels, fix versions, or how work is visualized. Neither ITLs nor FTLs are aligned in their usage. It mostly works when work stays within a single functional team, but when initiatives span multiple instruments or requires deep cross-functional coordination with dependencies, it really falls apart. We also have stale tickets that just add noise.

What we're looking for:

A one-time engagement to audit what we have, recommend a standardized structure, and help us implement it. This includes:

• Standardizing JIRA workflows, ticket types, epics, initiatives, labels, and fix versions across all teams
• Establishing a Definition of Ready and minimum ticket attributes
• Cleaning out stale/obsolete tickets
• Restructuring Confluence spaces so teams can navigate and find information consistently
• Building dashboards and reports so team leads can pull status updates without manual reformatting
• Documenting standards and policies so we can maintain everything going forward
• Training rollouts and adherence monitoring/ feedback

Must haves:

• Experience working with cross-functional hardware + software organizations
• Familiarity with PI-based planning (SAFe-adjacent, not strict SAFe)
• Experience with matrix organizations where shared resources work across multiple teams/projects
• Experience with JIRA automation rules

Nice to haves:

• Experience with requirements management within the Atlassian ecosystem
• Working Spanish proficiency

Details:

• Remote, async-friendly
• Available to start immediately
• Competitive compensation - est. 80-120 hour commitment over 60 days
• Cloud instance (not Data Center/Server)

If you're interested, DM me with a brief overview of similar engagements you've done, particularly with cross-functional or matrix organizations. Bonus points if you can share examples of before/after standardization work or client references.