Senior Manager, Business Systems
Jobgether · United States · 1 mo ago
RemoteRemoteInformation Technology$160k–$177k/yrFull-time
We need to output HTML fragment with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting.
We need to extract sections: The posting includes description (overview), accountabilities (responsibilities), requirements, benefits, maybe pay (salary range), schedule (remote, travel). Also maybe qualifications? The posting includes "Requirements" list. There's no separate "Qualifications" distinct from requirements; but we could treat Requirements as qualifications. However we need to follow instruction: Use headings for those categories if content exists. We should not repeat job title as heading. Also not include Job ID etc.
We need to remove boilerplate: "This position is listed on behalf of a partner company..." etc. Also remove "How Jobgether Works", "Why Apply Through Jobgether?", data privacy notice, etc. Also remove application instructions.
We need to preserve all substantive information.
Let's identify substantive parts:
- Intro: "This position is listed on behalf of a partner company, who manages all applications and next steps. Our partner is looking for a Senior Manager, Business Systems based in United States. This is a hands-on technical leadership role focused on consolidating and evolving a complex Atlassian Cloud environment across multiple business units. You will own platform architecture, governance, compliance, licensing strategy, and the long-term business systems roadmap. The role combines strategic planning with practical technical leadership, requiring you to stay close to architecture, tooling, integrations, and platform operations. You will partner with executive stakeholders to redesign workflows and operating models while supporting business objectives through scalable technology. You will lead delivery across internal teams and external customer environments while coaching managers and strengthening in-house technical expertise. The position also offers an opportunity to establish an AI-first approach to platform design, support, automation, and team productivity. This fully remote US role includes limited travel of up to 5% for client engagements and team leadership activities."
That's overview; could be "About the role".
- Accountabilities (list of bullet points): Starting after "Accountabilities". They are sentences separated by periods but could be turned into list items.
List:
Own the architecture and governance strategy for a multi-instance Atlassian Cloud environment, including Jira, Jira Service Management, Confluence, and related AI capabilities.
Establish scalable standards for permissions, SCIM and identity provisioning, Jira architecture, integrations, and the balance between customization and platform simplification.
Lead the consolidation of Atlassian products and business systems across multiple business units following organizational changes and acquisitions.
Own the platform's HIPAA and BAA compliance posture, evaluating scope across products, Marketplace applications, integrations, and AI connectors.
Define platform strategy and provide technical judgment for licensing decisions, including demand forecasting, tier and seat modeling, true-ups, and renewal recommendations.
Partner with senior and executive stakeholders to redesign workflows, operating models, and technology strategies that support evolving business objectives.
Lead internal and external delivery tracks through their respective managers while overseeing shared platform architecture capabilities.
Build and strengthen internal technical expertise, reducing reliance on external consultants and establishing clear standards for platform ownership and delivery.
Coach people leaders, establish high performance expectations, improve organizational structure, and develop team members toward broader responsibilities.
Apply an AI-first approach to platform architecture, administration, support, automation, and team workflows.
Drive iterative delivery through incremental releases, experiments, measured risk-taking, and continuous roadmap refinement based on results and feedback.
Evaluate, debug, and improve administrative tooling and integrations built against the Atlassian REST API.
Maintain strong platform health while identifying opportunities for modernization, simplification, automation, and improved user experience.
That's responsibilities.
- Requirements list: Starting after "Requirements". Bullets:
Deep, current hands-on experience with Atlassian Cloud, particularly permissions, SCIM and identity provisioning, and Jira architecture at enterprise scale.
Strong ability to read, troubleshoot, evaluate, and improve administrative tooling built against the Atlassian REST API; Python experience is preferred.
Demonstrated experience leading platform consolidation, workflow redesign, or technology transformation across multiple business units or a post-M&A environment.
Proven experience owning an enterprise platform internally, with direct in-house platform leadership preferred over primarily consulting or staffing-based experience.
Experience operating technology platforms within regulated environments such as HIPAA, HITRUST, SOC 2, PCI, FedRAMP, or GxP.
Understanding of how regulatory requirements affect architecture, vendor selection, integrations, data access, and AI adoption.
Hands-on experience with enterprise software licensing and vendor management, including tier modeling, seat forecasting, true-ups, and renewal support; comparable enterprise platform experience may also be considered.
Proven ability to build, restructure, or turn around technical teams by establishing clear ownership, improving performance, and developing people into larger scopes of responsibility.
Strong understanding of iterative product and platform delivery, with experience replacing large multi-quarter initiatives with shorter delivery cycles that demonstrate value incrementally.
Demonstrated ability to assess measured technical risks, learn from unsuccessful experiments, and adapt delivery strategies accordingly.
An AI-first mindset with practical experience incorporating AI into day-to-day workflows, technical decision-making, platform operations, or team productivity.
Strong executive communication skills and the ability to translate complex technical strategies into clear business decisions.
Excellent collaboration, leadership, problem-solving, and organizational skills.
Ability to work effectively across multiple time zones in a remote environment and communicate with technical and non-technical stakeholders.
Ability to work for extended periods at a computer and accommodate occasional travel and business-related schedule requirements.
- Benefits list: Starting after "Benefits". Bullets:
Annual US base salary range of $160,000–$177,000.
Fully remote position within the United States.
Full-time, permanent employment.
Up to 5% travel for client engagements and team leadership activities.
Opportunity to lead enterprise-scale platform consolidation and business systems transformation.
Significant ownership over architecture, governance, compliance, licensing, and long-term platform strategy.
Opportunity to shape AI-first approaches to technology operations and team productivity.
Leadership and professional development opportunities through team building, strategic initiatives, and cross-functional collaboration.
Work within a complex, multi-business-unit technology environment with executive-level exposure.
Also note "Pay" and "Schedule" sections: The posting includes salary range (pay) and schedule (fully remote, full-time, travel up to 5%). We could create separate Pay and Schedule sections, but we need to avoid duplication. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine Pay and Benefits? But they said use headings for Benefits, Pay, Schedule separately if content exists. However we could include Pay as part of Benefits (salary range). But they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state salary range (pay) and schedule (remote, full-time, travel). So we could create separate sections for Pay and Schedule, but we might also keep Benefits section for other benefits. However we risk thin sections. Let's see: Pay: salary range. Schedule: remote, full-time, travel up to 5%. Benefits: other items (opportunity to lead, ownership, AI-first, leadership dev, etc.). That seems reasonable.
We need to ensure we don't include filler like "commensurate with experience". Not present.
We need to output only HTML fragment, no markdown fences.
Thus produce:
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting.
We need to extract sections: The posting includes description (overview), accountabilities (responsibilities), requirements, benefits, maybe pay (salary range), schedule (remote, travel). Also maybe qualifications? The posting includes "Requirements" list. There's no separate "Qualifications" distinct from requirements; but we could treat Requirements as qualifications. However we need to follow instruction: Use headings for those categories if content exists. We should not repeat job title as heading. Also not include Job ID etc.
We need to remove boilerplate: "This position is listed on behalf of a partner company..." etc. Also remove "How Jobgether Works", "Why Apply Through Jobgether?", data privacy notice, etc. Also remove application instructions.
We need to preserve all substantive information.
Let's identify substantive parts:
- Intro: "This position is listed on behalf of a partner company, who manages all applications and next steps. Our partner is looking for a Senior Manager, Business Systems based in United States. This is a hands-on technical leadership role focused on consolidating and evolving a complex Atlassian Cloud environment across multiple business units. You will own platform architecture, governance, compliance, licensing strategy, and the long-term business systems roadmap. The role combines strategic planning with practical technical leadership, requiring you to stay close to architecture, tooling, integrations, and platform operations. You will partner with executive stakeholders to redesign workflows and operating models while supporting business objectives through scalable technology. You will lead delivery across internal teams and external customer environments while coaching managers and strengthening in-house technical expertise. The position also offers an opportunity to establish an AI-first approach to platform design, support, automation, and team productivity. This fully remote US role includes limited travel of up to 5% for client engagements and team leadership activities."
That's overview; could be "About the role".
- Accountabilities (list of bullet points): Starting after "Accountabilities". They are sentences separated by periods but could be turned into list items.
List:
Own the architecture and governance strategy for a multi-instance Atlassian Cloud environment, including Jira, Jira Service Management, Confluence, and related AI capabilities.
Establish scalable standards for permissions, SCIM and identity provisioning, Jira architecture, integrations, and the balance between customization and platform simplification.
Lead the consolidation of Atlassian products and business systems across multiple business units following organizational changes and acquisitions.
Own the platform's HIPAA and BAA compliance posture, evaluating scope across products, Marketplace applications, integrations, and AI connectors.
Define platform strategy and provide technical judgment for licensing decisions, including demand forecasting, tier and seat modeling, true-ups, and renewal recommendations.
Partner with senior and executive stakeholders to redesign workflows, operating models, and technology strategies that support evolving business objectives.
Lead internal and external delivery tracks through their respective managers while overseeing shared platform architecture capabilities.
Build and strengthen internal technical expertise, reducing reliance on external consultants and establishing clear standards for platform ownership and delivery.
Coach people leaders, establish high performance expectations, improve organizational structure, and develop team members toward broader responsibilities.
Apply an AI-first approach to platform architecture, administration, support, automation, and team workflows.
Drive iterative delivery through incremental releases, experiments, measured risk-taking, and continuous roadmap refinement based on results and feedback.
Evaluate, debug, and improve administrative tooling and integrations built against the Atlassian REST API.
Maintain strong platform health while identifying opportunities for modernization, simplification, automation, and improved user experience.
That's responsibilities.
- Requirements list: Starting after "Requirements". Bullets:
Deep, current hands-on experience with Atlassian Cloud, particularly permissions, SCIM and identity provisioning, and Jira architecture at enterprise scale.
Strong ability to read, troubleshoot, evaluate, and improve administrative tooling built against the Atlassian REST API; Python experience is preferred.
Demonstrated experience leading platform consolidation, workflow redesign, or technology transformation across multiple business units or a post-M&A environment.
Proven experience owning an enterprise platform internally, with direct in-house platform leadership preferred over primarily consulting or staffing-based experience.
Experience operating technology platforms within regulated environments such as HIPAA, HITRUST, SOC 2, PCI, FedRAMP, or GxP.
Understanding of how regulatory requirements affect architecture, vendor selection, integrations, data access, and AI adoption.
Hands-on experience with enterprise software licensing and vendor management, including tier modeling, seat forecasting, true-ups, and renewal support; comparable enterprise platform experience may also be considered.
Proven ability to build, restructure, or turn around technical teams by establishing clear ownership, improving performance, and developing people into larger scopes of responsibility.
Strong understanding of iterative product and platform delivery, with experience replacing large multi-quarter initiatives with shorter delivery cycles that demonstrate value incrementally.
Demonstrated ability to assess measured technical risks, learn from unsuccessful experiments, and adapt delivery strategies accordingly.
An AI-first mindset with practical experience incorporating AI into day-to-day workflows, technical decision-making, platform operations, or team productivity.
Strong executive communication skills and the ability to translate complex technical strategies into clear business decisions.
Excellent collaboration, leadership, problem-solving, and organizational skills.
Ability to work effectively across multiple time zones in a remote environment and communicate with technical and non-technical stakeholders.
Ability to work for extended periods at a computer and accommodate occasional travel and business-related schedule requirements.
- Benefits list: Starting after "Benefits". Bullets:
Annual US base salary range of $160,000–$177,000.
Fully remote position within the United States.
Full-time, permanent employment.
Up to 5% travel for client engagements and team leadership activities.
Opportunity to lead enterprise-scale platform consolidation and business systems transformation.
Significant ownership over architecture, governance, compliance, licensing, and long-term platform strategy.
Opportunity to shape AI-first approaches to technology operations and team productivity.
Leadership and professional development opportunities through team building, strategic initiatives, and cross-functional collaboration.
Work within a complex, multi-business-unit technology environment with executive-level exposure.
Also note "Pay" and "Schedule" sections: The posting includes salary range (pay) and schedule (fully remote, full-time, travel up to 5%). We could create separate Pay and Schedule sections, but we need to avoid duplication. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine Pay and Benefits? But they said use headings for Benefits, Pay, Schedule separately if content exists. However we could include Pay as part of Benefits (salary range). But they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state salary range (pay) and schedule (remote, full-time, travel). So we could create separate sections for Pay and Schedule, but we might also keep Benefits section for other benefits. However we risk thin sections. Let's see: Pay: salary range. Schedule: remote, full-time, travel up to 5%. Benefits: other items (opportunity to lead, ownership, AI-first, leadership dev, etc.). That seems reasonable.
We need to ensure we don't include filler like "commensurate with experience". Not present.
We need to output only HTML fragment, no markdown fences.
Thus produce:
About the role
... (overview paragraph)
Responsibilities
- ... ...
Requirements
- ... ...
Pay
Annual US base salary range of $160,000–$177,000.
Schedule
Fully remote position within the United States. Full-time, permanent employment. Up to 5% travel for client engagements and team leadership activities.
Benefits
- Opportunity to lead enterprise-scale platform consolidation and business systems transformation.
- Significant ownership over architecture, governance, compliance, licensing, and long-term platform strategy.
- Opportunity to shape AI-first approaches to technology operations and team productivity.
- Leadership and professional development opportunities through team building, strategic initiatives, and cross-functional collaboration.
- Work within a complex, multi-business-unit technology environment with executive-level exposure.