Senior Platform Jira Administrator

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 must not repeat job title. Must preserve all substantive info, no boilerplate. We need to extract content: - About the role: description of role, team, mission, location, etc. The posting includes: "At RTX, the world's largest aerospace and defense company..." and "We are looking for a driven and talented individual contributor to become a part of our DevSecOps Team... as a Jira Administrator." Also description of Department's mission, software teams, location (full-time on-site in Marlborough Massachusetts or Tewksbury Massachusetts). So we can put that under About the role. - Responsibilities: list of duties under "What You’ll Do". That includes bullet points: User Management, Consistency Across Jira Projects, System Maintenance, Troubleshooting and Support, Workflow Customization, Upgrade Support, Tool Integration, Customizations and Enhancements, Data Management and Reporting, Documentation, System Monitoring, Scripting, Refactoring. So we need

• for each. - Requirements: includes security clearance, US citizenship, ability to obtain interim secret clearance prior to start date. Also maybe "U.S. Citizen, U.S. Person, or Immigration Status Requirements:" but we need to keep substantive. So we can list: Active and transferable U.S. government issued security clearance required prior to start date; U.S. citizenship required; Ability to obtain interim U.S. government issued security clearance required prior to start date; DoD Clearance: Secret; etc. We'll put as list. - Qualifications: "You Must Have" list: degree in STEM and min 5 years experience; Experience as Jira Administrator; Experience in Jira automation features and scripting languages such as Groovy or JavaScript; Experience with SDLC processes; Experience with Jira dashboards and Structure plugin; Experience with configuration management tools (Git, GitLab); Experience with Agile and Scrum principles; Ability to obtain and maintain US Gov Interim Secret security clearance prior to start date; U.S. citizenship required. We'll list. - Qualifications We Prefer: list of preferred qualifications. Could be under Qualifications or separate? The instruction says use headings for Qualifications (maybe combine both must have and preferred?). But we have separate sections: Qualifications (must have) and maybe "Preferred Qualifications". However the allowed headings list includes Qualifications only. We could put both must have and preferred under Qualifications heading, but we need to preserve all info. Could separate into two sub-sections? Not allowed headings besides those. Could combine into one Qualifications section with two lists: "Must Have" and "Preferred". That's acceptable. - Skills: The posting includes "Skills to create and manage custom scripts..." etc under "Qualifications We Prefer". Actually those are skills. We could extract skills list: Strong analytical thinking, Knowledge of CI/CD pipelines, Experience managing multiple Jira instances, Understanding of project management principles, Strong grasp of Agile/Scrum, Skills to create and manage custom scripts, Experience integrating Jira with other tools, Familiarity with APIs, Ability to quickly assess situations, Strong written and verbal communication, Capability to translate complex technical concepts, Willingness to collaborate. That's a skills section. - Benefits: The posting includes "What We Offer" includes values, relocation eligible, benefits list: medical, dental, vision, life insurance, short-term disability, long-term disability, 401(k) match, flexible spending accounts, flexible work schedules, employee assistance program, Employee Scholar Program, parental leave, paid time off, holidays. Also annual short-term/long-term incentive compensation programs. So we can include Benefits section. - Pay: The posting includes salary range: 86,800 USD - 165,200 USD. So we include Pay. - Schedule: The posting mentions full-time on-site. Could be schedule: full-time, onsite. So we can include Schedule: Full-time, Onsite (Marlborough MA or Tewksbury MA). That's specific. We must not include boilerplate like EEO, legal, application instructions, etc. We must not include headings with filler text. Ensure each heading has substantive content. We must output only HTML fragment, no or . Use

  for each section heading. Use

  for prose. Use

  • for lists. We need to avoid repeating job title. Not include "Date Posted", "Country", etc unless they are substantive? Those are metadata but not required; we can drop minor metadata. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it." So we can drop date posted, country, location maybe? But location is substantive for schedule? We already have schedule includes location. Could include location in About the role or Schedule. We'll keep location in About the role or Schedule. We need to preserve all substantive information. So we should keep location info (Marlborough Massachusetts or Tewksbury Massachusetts) somewhere. We'll put in About the role: "This position is full-time on-site in Marlborough Massachusetts or Tewksbury Massachusetts." Now craft HTML. Structure:

    About the role

    At RTX, the world's largest aerospace and defense company ... We are looking for a driven and talented individual contributor to become a part of our DevSecOps Team, an essential component of our software development and delivery framework, as a Jira Administrator. In this role, you will collaborate closely with the Radar Digital Product Line (RDPL) programs to develop and implement solutions across multiple Jira servers, working together with the Platform Engineering team to identify and establish solutions that function effectively within a shared server environment used by programs across one of the largest Information System (IS) in the Northeast. The Department’s mission is to provide world class Radar Software to be used in military systems deployed at sea and on land. Our software teams employ an Agile Scrum process to rapidly design, code, integrate and test capabilities on a continuous basis into a mature solution for our customers. This position is full-time on-site in Marlborough Massachusetts or Tewksbury Massachusetts.

    Responsibilities

    • Oversee user accounts and permissions, including onboarding and offboarding to EIM/AD groups.
    • Ensure alignment and standardization across all Jira projects (both unclassified and IS), including maintaining and updating synchronization automation for configurations and issues.
    • Perform regular system maintenance to ensure optimal performance and reliability.
    • Provide direct user support, resolve issues, answer questions, and offer training as needed.
    • Design, implement, and maintain workflows, permissions, and project structures tailored to program-specific needs.
    • Assist with system upgrades to ensure smooth transitions and minimal disruptions.
    • Manage integrations with other tools like Confluence, GitLab, and other DevOps platforms.
    • Implement customizations and address enhancement requests to improve system functionality, including leveraging plugins such as Structure, Project Configurator, ScriptRunner, and JSU Automation.
    • Develop and maintain dashboards, reports, and queries to meet reporting needs and provide actionable insights.
    • Create and maintain comprehensive documentation for system configurations, processes, and user guides.
    • Monitor system performance to proactively address potential issues.
    • Develop and maintain scripts to automate processes or enhance functionality.
    • Refactor existing implementations to align with software development best practices, as approved.

    Requirements

    • Active and transferable U.S. government issued security clearance required prior to start date.
    • U.S. citizenship required (only U.S. citizens are eligible for a security clearance).
    • Ability to obtain interim U.S. government issued security clearance required prior to start date.
    • DoD Clearance: Secret.

    Qualifications

    Must Have

    • Typically requires a degree in Science, Technology, Engineering or Mathematics (STEM) and a minimum of 5 years of prior relevant experience unless prohibited by local laws/regulations.
    • Experience as a Jira Administrator, including configuring workflows, permissions, and issue types to meet project requirements.
    • Experience with Jira automation features and scripting languages such as Groovy (for ScriptRunner) or JavaScript.
    • Experience with Software Development Lifecycle (SDLC) processes, especially related to scripting languages.
    • Experience with Jira dashboards and the Structure plugin.
    • Experience with configuration management tools (e.g., Git, GitLab).
    • Experience with Agile and Scrum principles for supporting workflows and team processes within Jira.
    • Ability to obtain and maintain a U.S. Government issued Interim Secret security clearance prior to the start date.
    • U.S. citizenship is required as only U.S. citizens are eligible for a security clearance.

    Preferred

    • Strong analytical thinking for troubleshooting and resolving Jira configuration or integration issues.
    • Knowledge of CI/CD pipelines and tools such as Jenkins or GitLab CI/CD.
    • Experience managing multiple Jira instances in complex environments.
    • Understanding of project management principles to align Jira configurations with organizational goals.
    • Strong grasp of Agile/Scrum principles to configure Jira for iterative development (e.g., sprints, Kanban boards, backlog grooming).
    • Skills to create and manage custom scripts and automation rules for enhanced Jira functionality.
    • Experience with integrating Jira with other tools (e.g., Confluence, Bitbucket, Jenkins, GitLab, or other DevOps tools).
    • Familiarity with APIs to create custom integrations.
    • Ability to quickly assess situations and deliver results, even under pressure.
    • Strong written and verbal communication skills to effectively interact with both technical and non-technical stakeholders.
    • Capability to translate complex technical concepts into clear, user‑friendly language.
    • Willingness to collaborate closely with cross‑functional teams.
    We could also have a Skills section separate, but we already included skills under Preferred. However the instruction allows Skills heading. Might be better to separate Skills from Qualifications. But we already have a lot of content under Qualifications. Could we move the "Skills to create and manage custom scripts..." etc to Skills section? The Preferred list includes many skill-like items. We could create a Skills heading and put those skill items there. But we must not duplicate. Let's think: The posting has a section "Qualifications We Prefer" which includes both qualifications and skills. The instruction says we can have Skills heading. So we could split: Qualifications (must have) and Skills (preferred). But we also have "Qualifications We Prefer" includes items like strong analytical thinking, knowledge of CI/CD, etc. Those are more skills/experience. We'll treat them as Skills. Thus:

    Qualifications

    Must Have

    (list of must have items)

    Skills

    (list of preferred skill items)
    Then Benefits, Pay, Schedule. Let's extract must have items precisely: - Typically requires a degree in Science,Technology, Engineering or Mathematics (STEM) and a minimum of 5 years of prior relevant experience unless prohibited by local laws/regulations. - Experience as a Jira Administrator, including configuring workflows, permissions, and issue types to meet project requirements. - Experience in Jira automation features and scripting languages such as Groovy (for ScriptRunner) or JavaScript. - Experience with Software Development Lifecycle (SDLC) processes, especially