Must Have Skills:
– Expert -level knowledge of Tempo
Structure: creating, configuring, and managing boards, columns, swimlanes,
and views

– Solid
working knowledge of Atlassian Jira Data Centre — project types, issue
hierarchies, custom fields, and how data is structured

– Ability
to quickly orient within an unfamiliar Jira DC configuration and identify
what is and isn't achievable for a given request

– Experience
building boards that support planning and management use cases (quarterly
planning, OKR tracking, capacity views, strategy boards)

– Nice to Have Skills:
Understanding of Agile Ways of
Working — particularly how teams plan, track, and report on delivery at a
portfolio or programme level

– Familiarity
with OKR frameworks and how they are commonly represented in Jira -based
tooling

– Awareness
of capacity management concepts and how resource allocation is typically
modelled in Atlassian environments

Detailed Job Description

Tempo Structure Board Delivery

– Rapidly
take ownership of incoming board requests, conducting lightweight discovery




to clarify scope and confirm requirements directly with requestors and senior
stakeholders

– Design,
build, and deliver Tempo Structure boards to support a range of management
use cases, including:

– Delivery
Flow Tracking — visibility of work -in -progress and throughput across teams

– Tactical
OKR / Objectives Tracking — linking work items to strategic objectives in a
digestible view

– Plan
on a Page — consolidated planning views that surface quarterly or annual
commitments and progress

– Tactical
Capacity Management — boards that expose resourcing and allocation across
teams or time periods

– Any
additional urgent structural views as they arise, based on emerging
leadership needs

Requirements & Stakeholder Engagement

– Engage
directly with senior leadership and management stakeholders to validate
requirements and confirm priorities before building

– Translate
high -level, often loosely defined management needs into clear, buildable
Tempo Structure configurations

– Communicate
delivery timelines, constraints, and trade -offs clearly — flagging when a
request cannot be fulfilled as described given the DC configuration or
available data

Platform Understanding & Configuration

– Rapidly
assess and understand the existing Atlassian DC configuration (project
structures, issue hierarchies, custom fields, workflows) to determine what is
possible for each board request

– Work
within the constraints of the current DC environment — solutions need not be
permanent or elegant, but must be reliable and fit for purpose for their
intended shelf life

– Maintain
awareness of the Cloud transition direction to avoid building DC
configurations that would complicate migration

Minimum Years of Experience
- 5+ Year of IT experience