Business Analyst

Atlassian Platform Depth (core requirement)

• Deep, hands-on knowledge of Jira, Jira Service Management and Confluence at expert power-user level — enough to know what the platform can and cannot do. Experience as an Atlassian administrator is not required.
• Jira: fluent in projects, issue types, custom fields, screens, workflows, permission and notification schemes, reporting and dashboards — and able to reason about how a given requirement maps onto these objects.
• Jira Service Management: fluent in request types and forms, portals, queues, SLAs, approvals, automation rules and agent/customer permissions.
• Confluence: spaces and permissions, page structuring, templates, and linking documentation to Jira/JSM projects.
• Understands the configuration model well enough to anticipate consequences: shared vs. dedicated schemes, global vs. project-level settings, licence and permission implications, and where a requested change would create long-term maintenance debt.
• Able to hold a substantive technical discussion with the Atlassian administrators — challenge a proposed solution, weigh alternatives, and understand why something is difficult — without performing the configuration themselves.

Integrations & Connected Systems

• Understanding of how Atlassian sits in a wider system landscape: examples: SSO / Active Directory and user provisioning, asset and CMDB data, and downstream reporting.
• Comfortable with APIs and integration concepts at analyst level (REST, webhooks, data and field mapping between systems) — able to specify an integration and discuss it with admins
• Able to analyse cross-system automation and to judge what should be solved inside Atlassian versus in a connected system.

Translating Requirements into Functionality

• Works independently: takes a vaguely stated business need, runs the analysis, and produces a solution proposal expressed in platform terms (objects, workflows, request types, automation) rather than a generic list of requirements.
• Produces user stories, process flows, acceptance criteria and functional designs specific enough to be built directly.
• Confident enough to push back or propose a simpler alternative when a requirement would harm the platform or the user experience.

International / Cross-Functional Experience

• Demonstrated experience working in an international, multi-country organization.
• Comfortable facilitating workshops and interviews with stakeholders from different countries and business functions.
• Able to shift register between technical detail (administrators, developers) and business framing (Tribe leads, board).

Analytical & Soft Skills

• Strong analytical and requirements-elicitation skills (process mapping, workflow design).
• Excellent stakeholder management, facilitation and written/verbal communication skills.
• Structured, detail-oriented way of working; comfortable producing clear documentation.
• Technically curious — explores the tools hands-on in a test environment rather than relying on others to explain how they work.