About Alyve The problems are complex. The clients are senior. The team is small enough that your thinking is visible in everything we produce.

We work with organisations facing difficult technology and transformation challenges. We bring clear thinking, practical expertise and the willingness to tell clients what they need to hear.

If you want to do the best work of your career, this is a reasonable place to try.

The Role

This is a hands-on platform leadership role supporting an established enterprise Jira and Confluence environment.

The platform has recently expanded to support portfolio visibility, capacity planning, delivery management and testing. Tempo Structure, Tempo Capacity Planner and Xray now sit alongside the core Atlassian platform.

The foundations are in place. Your role is to take ownership of what comes next: strengthening the configuration, improving adoption and making the platform a reliable part of how work is planned, managed and delivered.

You will work with technology teams, the PMO, delivery leaders, testing functions and business stakeholders. Some conversations will begin with a clear platform requirement. Others will begin with a delivery problem that needs to be understood before anything is configured.

You will need to know the difference.

This is not a service-desk role or a position focused on processing configuration requests. You will be trusted to understand how the organisation works, challenge weak requirements and design solutions that remain useful as the environment grows.

What You Will Do

Own and improve the platform

You will take responsibility for the health, reliability and ongoing evolution of Jira and Confluence.

That includes projects, workflows, issue types, screens, fields, schemes, permissions, notifications and automation. You will manage configuration changes carefully, resolve issues and maintain the standards required to keep the environment scalable.

Make complex delivery visible

You will maintain portfolio structures and reporting across initiatives, streams, projects, epics and delivery work.

The objective is practical visibility. Priorities, milestones, dependencies, critical paths, delivery status, risks and capacity should be clearer because of the platform.

Get more from the applications already in place

You will own and improve the use of Tempo Structure,



Tempo Capacity Planner and Xray.

That means supporting portfolio planning, resource forecasting, capacity management and test management while ensuring the applications work coherently with the underlying Jira configuration.

Translate operational needs into maintainable solutions

Stakeholders will rarely describe their needs in perfect Jira terminology.

You will work with them to understand the actual problem, design fit-for-purpose solutions and avoid unnecessary complexity. Where planning and reporting still happen through spreadsheets or disconnected tools, you will assess what should move into Jira and lead the transition.

Build capability around the platform A strong configuration is only useful when people understand and trust it.

You will maintain documentation and operating procedures, provide practical guidance and training, and improve adoption without creating unnecessary administration for delivery teams.

Shape Alyve’s Atlassian capability

You will work closely with Alyve’s leadership and consultants, bringing a specialist platform perspective to wider delivery and transformation problems.

You will contribute to solution design, proposals, platform standards and the development of a stronger Atlassian capability across the firm.

You Are Someone Who

- Understands Jira deeply enough to know when to configure, simplify or challenge a request
- Can move comfortably between technical platform detail and the delivery problem behind it
- Thinks structurally about hierarchies, workflows, permissions, data and reporting
- Works well with technical teams, delivery leaders, PMO functions and senior stakeholders
- Diagnoses problems methodically and communicates solutions clearly
- Values maintainability and consistency without imposing control for its own sake
- Enjoys remaining technically close to the platform while influencing how it supports the organisation

Minimum Requirements





- Five or more years of hands-on Jira administration and configuration experience
- Strong experience administering Jira Cloud and Confluence in a complex organisation
- Advanced knowledge of workflows, schemes, permissions, custom fields, automation and Jira data structures
- Experience designing or supporting programme and portfolio-level Jira configurations
- Experience implementing or supporting Tempo Structure, Tempo Capacity Planner, Xray or comparable marketplace applications
- A working understanding of project, programme, portfolio and Agile delivery practices
- Experience translating stakeholder requirements into scalable platform solutions
- Strong documentation, troubleshooting, communication and user-training capability
- Australian working rights
- Melbourne-based and available to work hybrid

Experience with Atlassian APIs, integrations, migrations, application upgrades or Atlassian certifications will be highly regarded.

Why Alyve

- Work that matters: Platforms that directly shape how major organisations plan and deliver change
- Visible expertise: Your judgement will influence both the technical environment and the wider delivery model
- Real ownership: You will be trusted to lead the platform, challenge assumptions and make decisions
- Diverse perspective: You will work across technology, delivery, portfolio management and testing
- Human culture: Warmth, directness and genuine investment in each other
- Growth: You will help shape Alyve’s Atlassian capability as the firm grows

Application A senior delivery leader asks you to introduce a new mandatory workflow, twelve custom fields and a project-specific reporting structure. They believe this will solve inconsistent status reporting across their portfolio.

When you inspect the environment, you find several existing workflows addressing similar needs, inconsistent data across projects and limited adoption of the current portfolio structure. The leader wants the new configuration released within two weeks.

What is the actual problem, and what do you do first?

Maximum 300 words. We are not looking for a list of Jira features. We are looking for your platform judgement, how you approach the stakeholder and how you determine the right solution.

Shortlisted candidates will complete a practical platform-design exercise as part of the interview process.

📌 Atlassian Platform Lead - Jira & Confluence (Melbourne)
🏢 Alyve
📍 Melbourne