Key Responsibilities:

Platform ownership and governance
Own administration and architecture for the Atlassian estate: Jira, Jira Service Management, Confluence and associated applications and integrations.
Establish and enforce governance: project and space creation standards, workflow and screen scheme rationalisation, custom field discipline, and permission and access models.
Prevent the sprawl that makes Atlassian estates unusable at scale — consolidate where configurations have diverged without reason, and hold the line on current ones.
Own upgrade, migration and vendor release management, and maintain the licensing and cost position.

Service management enablement
Own the Jira Service Management configuration that underpins IT service management: request types, queues, service level agreements, approval flows and the service catalogue.
Build the reporting that gives IT leadership a real view of delivery throughput, service performance and backlog health.




Partner with the Helpdesk Lead and the wider support function as IT service management shifts to a Hyderabad-centred model.

Automation and integration
Build automation that removes manual administration — automation rules, scripted workflows and self-service patterns.
Own integrations between Atlassian and the Microsoft 365 and Teams estate, source control and CI/CD tooling, and monitoring and alerting platforms.
Enable the delivery teams to work in a consistent way across the SAP, commerce, data and infrastructure functions without imposing a process that does not fit their work.

Controls and leadership
Own access governance and audit evidence for the Atlassian estate, including SOX-relevant change and approval records.
Ensure Confluence is a functioning knowledge estate rather than a document graveyard — this platform is where the transitioning organisation's knowledge will land or be lost.

📌 Infrastructure Lead Hyderabad
🏢 BayOne Solutions
📍 Hyderabad