Atlassian Cloud Administrator / Jira Implementation Specialist

We are hiring a remote Atlassian Cloud Administrator / Jira Implementation Specialist to design and implement a clean, scalable Atlassian environment across Jira Software, Jira Service Management, and Confluence.

The Role

This is a hands-on role.

We currently use both Jira and Wrike. Your primary project will be to standardize our processes in Jira, recreate the useful workflows currently managed in Wrike, simplify where possible, introduce automation and governance, and prepare the organization to retire Wrike. We are not looking to replicate Wrike. We want someone who can understand our existing processes and redesign them using Jira best practices.

What You'll Do

• Configure and administer Jira Software, Jira Service Management, and Confluence Cloud.
• Create and standardize Jira spaces/projects, issue types, workflows, statuses, screens, and schemes.
• Design and manage custom fields while preventing unnecessary field proliferation.
• Configure roles, groups, permissions, and governance standards.
• Build Jira Automation rules to eliminate repetitive manual work.
• Create engineering and management dashboards, filters, reports, and JQL queries.
• Configure structured intake/request forms for Engineering, Product, Client Success, and other teams.
• Configure JSM request types, queues, workflows, SLAs, and approval processes where appropriate.
• Review approximately five existing Wrike spaces and identify the processes that should be recreated in Jira.
• Redesign and standardize those processes rather than performing a direct data migration.
• Work with engineering teams to configure integrations with GitHub, Azure DevOps, Microsoft Teams/Slack, and other systems.
• Partner with a full-stack developer where custom integration work is required.
• Establish Jira administration standards and change-control processes.
• Create clear administrator and user documentation.
• Train internal Engineering, Technical Program Management, and DevOps team members so they can maintain the platform after the engagement.

Key Deliverables

• A clean and standardized Jira Cloud environment.
• Jira Software, Jira Service Management, and Confluence configured appropriately.
• Existing Wrike processes redesigned and recreated in Jira.
• Standard workflows and issue structures across teams.
• Engineering and business intake processes.
• Jira automation for common workflows and repetitive activities.
• Executive and engineering delivery dashboards.
• Clear roles, permissions, and governance.
• Integration with key engineering tools.
• Documentation covering configuration, standards, and ongoing administration.
• Knowledge transfer to internal administrators.
• A clear path to retiring Wrike.

What We're Looking For

• Strong hands-on experience administering Jira Cloud.
• Experience with Jira Software, Jira Service Management, and Confluence.
• Strong experience configuring workflows, issue types, screens, custom fields, schemes, permissions, and roles.
• Strong Jira Automation and JQL skills.
• Experience designing Jira environments for software engineering organizations.
• Experience configuring JSM portals, request types, queues, SLAs, and workflows.
• Experience creating dashboards and management reporting.
• Strong understanding of Jira governance and configuration best practices.
• Ability to understand existing business processes and translate them into simpler Jira workflows.
• Strong documentation and knowledge-transfer skills.
• Ability to work independently and make pragmatic configuration recommendations.
• Fluent professional English.

Nice to Have

• Experience with Wrike.
• Previous Wrike-to-Jira transition experience.
• Experience integrating Jira with GitHub or Azure DevOps.
• Experience with REST APIs, webhooks, or Atlassian integrations.
• Experience with SaaS engineering organizations.
• Experience supporting Agile engineering teams.
• Atlassian certifications.

Practical experience is more important than certification. The role requires someone who will challenge unnecessary complexity.

If an existing process contains 15 statuses, 20 custom fields, and several manual handoffs, the goal is not to simply recreate all of them in Jira. The goal is to identify the simplest Jira configuration that supports the process, provides the required controls and visibility, and remains maintainable after the engagement.

Success will be measured not by how much Jira configuration is created, but by how simple, automated, governed, documented, and maintainable the resulting environment is.